Fri, 28 March 2008 To you straight from the mouths of our datacenter team: "I will try to explain it as easy as possible. at 18:45EST 3-27-2008; The PFC3B line card in the Primary Supervisor of Core1 went into a LOOP; This caused an issue that did not allow Core1 to process Layer3 traffic across the MSFC3. Layer2 however was not affected in this matter which allowed Core2 to continue running normally and pass Layer2 traffic Across the Core1 Layer2 Back-bone. HSRP which is used as a counter-measure; still showed Core1 as functional even though it was experiencing a Loop. at 19:00EST; a CISCO SMART-NET Tech has been dispatched with additional hardware (SUP, MSFC3, PFC3) in case a defective board was found. At 19:35EST, Core1 was taken off-line in preparation for Cisco's Arrival. Upon arrival at about 20:45EST; a debug was generated and CISCO has re-certified the Module. We are waiting on Final Explanation from CISCO as to what caused the PFC3 daughter board to act in the way that it has. We have taken numerous Physical counter-measures to make sure that this will not happen again. Some of these counter-measures include modification to the HSRP algorythm as well as physical scripting. Lastly; This incident only affected clients that the HSRP was Active on the Device. We have placed more sophisticated HSRP counter-measures." Laymen's explanation: there was a hardware failure. Our side of the blame line is not having enough replication of our DNS records in another datacenter. That is being fixed today. Sorry again for the downtime. Category: general -- posted at: 10:51 AM Comments[0] |
Thu, 20 March 2008 As you may have already heard (and as reported in this article), two major network carriers (Cogent and Telia) have "stopped talking to each other." While Libsyn.com does push a decent amount of traffic through Cogent (which could mean problems for users on the Telia network requesting that content), we are connected to the net through multiple large providers. The word from our main data center is that most, if not all, of the requests for libsyn content from users on the Telia network should get sent through alternate (non-cogent) channels. If you or someone you know is having problems getting content from libsyn, please find out the IP address of the affected user (try http://whatismyip.com) and send it to Libsyn suport letting them know you're having issues. Thanks! Category: general -- posted at: 4:08 PM Comments[0] |
Tue, 11 March 2008 We launched v.1.6 of the libsyn stats service yesterday. Here's a 7 minute demonstration video to see what they are all about. Please excuse the fact that I have a cold.. and am not, in fact, the EVP of Stats.
Comments[1] |
Fri, 7 March 2008  Issues addressed in this release:
There are currently 2 partitions which contain many popular users and therefore taking longer to re-process that last 9 months worth of data. We've held off an extra couple weeks from releasing this version while we waited for all users to catch up. Our feelings now are why make the 90% suffer for the 10% that are behind. If you are unlucky enough to be in that 10%, please be patient while your data catches up. For the most recent issues some users have been experiencing this week regarding slow or no updates, those engines are working to catch up. You should see v.1.5.2 numbers updating over the weekend. Category: Stats -- posted at: 3:09 AM Comments[0] |
|
Libsyn Support Blog Weblog of the status of the Liberated Syndication System.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
