29
Aug. 1 Level3 Communications backbone issue
Filed Under (Website Monitoring) by admin on 29-11-2011
<img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/f4629_imagebutton.gif?url=http%3A%2F%2Fwww.dotcom-monitor.com%2Fblog%2Findex.php%2F2011%2F08%2Faug-1-level3-communications-backbone-issue%2F&source=dotcommonitor&style=normal” height=”61″ width=”50″ />
Some Dotcom-Monitor clients may have experienced alerts due to a Level3 connectivity issue. For details see the statement below from Level3 explaining the event and the resolution.
“Much of the internet connectivity in and to the Continental United States was degraded by an outage within the Level3 Communications backbone that began at approximately 17:22 1 August 2011 UTC. The impact of this event was felt not only on the Level3 backbone but also on other carriers as providers shifted large amounts of traffic that would have normally transited the Level3 network onto alternate network paths, causing increased latency and congestion and packet loss.
Many providers who utilize Level3 Communications for transport services, both telephone and IP, were also impacted as these transport services utilize the same converged backbone as the Level3 transit product.
The Level3 Communications master case number is 40976066.
The Level3 Communications official statements regarding the unscheduled network event are:
8/1/11 7:12:56 PM GMT The IP NOC reports that the network equipment self restored, resolving the routing issue and restoring services at approximately 17:55 GMT. The IP NOC states that they will continue to work with Level 3 OPS Engineers and the equipment vendor to isolate the root cause of the service interruption. The Level 3 TSC has confirmed that all customer services have been restored and the IP NOC will continue to monitor for stability.
8/1/11 6:29:26 PM GMT The IP NOC reports that a routing issue failure between Dallas, TX and Los Angeles, CA is impacting IP services in multiple markets. The IP NOC has engaged the equipment vendor, as well as Level 3 OPS Engineers and continues to investigate to isolate the issue at this time.”
<img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/fd67c_delicious.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to Del.icio.us” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to Del.icio.us” /><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/b47b6_digg.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to digg” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to digg” /><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/b47b6_reddit.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to reddit” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to reddit” /><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/66ace_stumbleupon.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to Stumble Upon” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to Stumble Upon” /><a href="http://www.google.com/bookmarks/mark?op=edit&output=popup&bkmk=http://www.dotcom-monitor.com/blog/index.php/2011/08/aug-1-level3-communications-backbone-issue/&title=Aug.+1+Level3+Communications+backbone+issue” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to google Bookmarks”><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/c24bd_google.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to google Bookmarks” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to google Bookmarks” /><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/c24bd_slashdot.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to SlashDot” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to SlashDot” /><a href="http://www.<a href="http://www.website-monitoring.com/blog/2010/03/17/facebook-facts-and-figures-history-statistics/”>facebook.com/share.php?u=http://www.dotcom-monitor.com/blog/index.php/2011/08/aug-1-level3-communications-backbone-issue/&t=Aug.+1+Level3+Communications+backbone+issue” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to <a href="http://www.website-monitoring.com/blog/2010/03/17/facebook-facts-and-figures-history-statistics/”>facebook“><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/728b6_<a href="http://www.website-monitoring.com/blog/2010/03/17/facebook-facts-and-figures-history-statistics/”>facebook.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to <a href="http://www.website-monitoring.com/blog/2010/03/17/facebook-facts-and-figures-history-statistics/”>facebook” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to <a href="http://www.website-monitoring.com/blog/2010/03/17/facebook-facts-and-figures-history-statistics/”>facebook” /><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/1e94d_blogsvine.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to Blogsvine” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to Blogsvine” /><a href="http://<a href="http://www.website-monitoring.com/blog/2010/05/04/twitter-facts-and-figures-history-statistics/”>twitter.com/home?status=http://www.dotcom-monitor.com/blog/index.php/2011/08/aug-1-level3-communications-backbone-issue/” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to <a href="http://www.website-monitoring.com/blog/2010/05/04/twitter-facts-and-figures-history-statistics/”>twitter“><img src="http://www.website-monitoring.eu/wp-content/plugins/wp-o-matic/cache/1e94d_<a href="http://www.website-monitoring.com/blog/2010/05/04/twitter-facts-and-figures-history-statistics/”>twitter.png” title=”Add ‘Aug. 1 Level3 Communications backbone issue’ to <a href="http://www.website-monitoring.com/blog/2010/05/04/twitter-facts-and-figures-history-statistics/”>twitter” alt=”Add ‘Aug. 1 Level3 Communications backbone issue’ to <a href="http://www.website-monitoring.com/blog/2010/05/04/twitter-facts-and-figures-history-statistics/”>twitter” />
