We had a short outage of media delivery yesterday, May 25th (for about 40 minutes just after noon, eastern time).  It looks to have been a denial of service attack targeting a few key machines in the network.  We acted quickly to switch to a hot backup we had in place for just this kind of scenario, and took appropriate actions to block the offending ip(s).

Ok everyone, we have scheduled the system maintenance (spoken of in the previous post) for this friday, may 26th.  We will begin around 10pm EST and expect to work through the night.  Most of it will be transparent to you all, but we do expect a short period of down-time for the main libsyn site, blog pages, and RSS feeds (media delivery will continue unfettered) some time after midnight. 

Please let us know if you have any questions or concerns.  Thanks!

UPDATE:

The move has been delayed some as our techs at the datacenter double and triple check wiring, configurations, and routing for all of our equipment.  We will make a new post here with at least 24 hours notice of when the actual upgrade is going to take place.

--

Our primary datacenter is upgrading and expanding (partially to meet our growing demands). We have been working through a series of updates and are a reaching a point where there will been some physical hardware shifted around this coming week. Through careful planning and our redundancy in multiple datacenters, we intend to keep mission critical functions, like serving media to your audience, up and functioning at all times. There will however be a short period on Tuesday, May 16th where you will be unable to upload new media, login to post shows or check stats for up to an hour.

We will be dialing in the exact times as this stage of the process grows closer, and will post an update with  the latest news. This estimate is the worst-case scenario, and our technical team will be in constant  communication with the folks "on the ground," ready to react to any issues that should arise during the transition.

As always, we want you all to have complete clarity and understanding of what we are doing and that we are focused on ensuring the least inconvenience and downtime possible. Thanks

We have repaired a service which has caused a brief outage we experienced tonight. Everything is back to 100% and we are making the necessary steps right now to ensure this particular issue does not arise again. We learned tonight, yet another, thing that can go wrong. Luckily we had the hands in the right places to react and bring things back to normal

LibSyn blog engine 2.7 is online today.  We'll be updating the wiki w/ better documentation on what the new engine can do.  It's incremental changes as we work towards a grand rewrite of how the blog page functions.

If things are starting to not work right on your page, please contact support@libsyn right away.

It looks like that some physical damage has affected two our our high level connections. We are told that there are crews on site from Level 3 and Cogent. Our data center is working on a reroute, and we should now be back online for many of you.

We are about 1/2 way to having full redundancy on the libsyn network and expect to be fully redundant across multiple datacenters / geographic locations early this summer. We apologize for the inconvenience