October 2010 - Outages - Outages Lists

llnw/dtag suboptimal routing
by Robin Pimentel 29 Oct '10

29 Oct '10

Just as I was about to send this, things seemed to have normalized. Throughout most of this morning: Some domestic Limelight routes, normally routed through local peers, seemed to only be available through DTAG (causing them to be routed to Europe). A minority of routes were affected: * i68.142.72.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i68.142.76.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i68.142.80.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i68.142.84.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i68.142.100.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i68.142.118.0/23 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i68.142.120.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i69.28.128.0/20 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i69.28.141.0/24 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i69.28.144.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i69.28.148.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i69.28.152.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i69.28.156.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i69.28.160.0/21 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i69.28.176.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i69.28.180.0/22 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i69.28.187.0/24 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i * i 67.17.64.89 50 199 0 3320 22822 i *>i 67.17.64.89 50 199 0 3320 22822 i The majority of routes seemed to be unaffected.

1 0

[ADMIN] OUTAGES.ORG Survey: Your Participation Requested.
by virendra rode 29 Oct '10

29 Oct '10

<Apologies for duplicate emails. If you have already participated, thank you very much. And for you who have not, please consider doing so.> We encourage all organizations across global operational community on the operational aspects of public-facing networks to participate in the survey so we can establish a comprehensive view of what's working and how we can improve going forward in the area of critical infrastructure outages notification. The survey is composed of 36 questions and can be completed in about 15 minutes. Also, NO personally (or organizationally) identifiable information will be shared in any manner. Please take a few moments to complete the survey located at: https://spreadsheets.google.com/viewform?formkey=dGpvQXgtQjk1eEllcDJJVk94MV… We're grateful for your insight and participation, and welcome your feedback and comments. Grateful Thanks! regards, /virendra

2 1

Any oddities with Yipes?
by Dawson, Robert 29 Oct '10

29 Oct '10

I am seeing what appear the be potential peering issues with Yipes for one of my customers, websites unreachable from some ISPs, not others. Can't really divulge any specifics, just wondering if anyone has seen anything generally. Thanks, Rob

1 0

Re: [outages] NSF.gov Unavailable
by Chris Boyd 27 Oct '10

27 Oct '10

> -----Original Message----- > From: Ernie Rubi [mailto:ernesto@cs.fiu.edu] > Sent: Wednesday, October 27, 2010 3:46 PM > To: nanog(a)nanog.org > Subject: NSF.gov Unavailable > > Um, down for everyone reports it as down for everyone. > > Any news as to what may be causing it? > > Ernesto M. Rubi > Sr. Network Engineer > AMPATH/CIARA > Florida International Univ, Miami > Reply-to: ernesto(a)cs.fiu.edu > Cell: 786-282-6783 On Oct 27, 2010, at 2:58 PM, Samuel Petreski wrote: > I think they had a fire in the building. > > --Samuel > > -- > Samuel Petreski > Sr. Security Analyst > Georgetown University Lightning strike, apparently http://www.arlnow.com/2010/10/27/nsf-building-evacuated-in-ballston-after-a… Seems it took out the nameservers as well. --Chris

2 1

ADMIN: Outages List FAQ/Monthly Post.
by virendra rode 25 Oct '10

25 Oct '10

Please take 5 minutes to read it before you post [again]. General Information =================== About Outages & Mission statement: http://wiki.outages.org/index.php/Main_Page Credits: Credit goes to the Debian / NANOG mailing list for FAQ, which served as a model for the OUTAGES FAQ. Outages lists and AUP: ========================================== Mailing List Charter The OUTAGES mailing list is established to provide a forum for the exchange of major outages discussion of Critical Internet infrastructure, such as IXPs, DNS root servers, major carrier failures, major data center, carrier hotel, COs, etc., that require cooperation among network service providers, carriers and network operators around the globe. In order to continue to provide a useful forum for discussion of relevant outages issues, the list is governed by the following guidelines: Acceptable Use Policy (Code of Conduct) Outages is entirely volunteer-run non-profit organisation. We collaborate freely on a volunteer basis for everyone's benefit. This code of conduct covers your behaviour as a member of the Outages Community, in any outages mailing list, wiki, web site, IRC channel, public meeting or private correspondence. 1. Discussion will focus on Internet / backbone related outages and technical issues surrounding it as described in the charter of OUTAGES. 2. Postings of issues inconsistent with the charter are prohibited. 3. Cross posting is prohibited. 4. Do not quote messages that were sent to you by other people in private mail, unless agreed beforehand. 5. Postings that include foul language, character assassination, and lack of respect for other participants are prohibited. 6. Product marketing is prohibited. 7. Postings of political, philosophical, religious and legal nature are prohibited. 8. Using list as source for private marketing initiatives is prohibited. 9. Autoresponders sending "out of office" or "vacation" mail either to the list or to the poster are prohibited. 10. Try not to flame; it is not polite. 11. Never send your messages in HTML; use plain text instead. 12. Do not send "test" messages to determine whether your mail client is working. Individuals who violate these guidelines will be contacted and asked to adhere to the guidelines. If groups of individuals persist in introducing topics that are outside the charter of OUTAGES, the moderator committee will send a request to the entire mailing list requesting adherence to the guidelines. OUTAGES List FAQ: =================================================== FAQ contributions are welcome -- please send email to admins(a)outages.org About OUTAGES and the List The primary goal of outages mailing list is for outages-reporting that would apply to failures of major communications infrastructure components having significant traffic-carrying capacity. See the main OUTAGES web page at: http://www.outages.org The OUTAGES Volunteer Committee is made up of network operator community members. You can reach the committee at admins(a)outages.org A. Is the list moderated? No, the outages mailing list is not moderated. B. I am not getting any mail anymore from the list! Is it down or what? * If for any reason your email address is unavailable, after some retries you will be automatically unsubscribed. * You may get unsubscribed because MTAs relaying traffic to you get bounces for some reason. * There are no major outages to report :-) C. How do I report outages regarding outages mailing list? You could report problem(s) by reaching us at, admin(a)outages.org D. Subscribe / Unsubscribe to OUTAGES Mailing List For more information, see the subscription web page at: http://wiki.outages.org/index.php/Main_Page#Mailing_Lists E. Disclaimer for the OUTAGES mailing lists http://wiki.outages.org/index.php/Wiki:General_disclaimer To contact the list's admins: admins(a)outages.org Posting Policy ============== * The basic rule is to avoid asking questions that have been asked before, or that are irrelevant to other list users, or that are off topic. Please use your good sense. * Network operational related topics / issues are not appropriate for this forum. * Please read the FAQ and AUP (code of conduct) policy before posting for more details. The following are specifically discouraged: * Is a certain site down? Please do your technical diligence before posting, use http://downforeveryoneorjustme.com/ or check http://wiki.outages.org/index.php/Dashboard for public dashboard prior to querying the list. Please also avoid ============= * Sending posts to the list relevant to only one or two people on this list, such as tests or traceroute(s) in response to another post for comparison to those originally posted. * Jokes, Puns, amusing observations, spelling corrections. * Network operations, and other non-outages related issues should be discussed in the appropriate forums elsewhere. Other OUTAGES related lists ==================== * outages-discussion - Post outages related discussion, including troubleshooting, analysis, post-mortem pertaining to ongoing and /or post outages. https://puck.nether.net/mailman/listinfo/outages-discussion * outages-announce - Change management, future updates regarding the list. https://puck.nether.net/mailman/listinfo/outages-announce Please send your feedback, comments and /or recommendations on how we can improve outages services further at admin(a)outages.org

1 0

Facebook ??
by Collin Rose 22 Oct '10

22 Oct '10

http://www.downforeveryoneorjustme.com/www.facebook.com

9 8

Not really an outage, but...
by Larry Sheldon 22 Oct '10

22 Oct '10

....Cox east MTA'a and some other stuff this morniong and early afternoon Central seems really really slow. (PING to my default router address at Cox seems normal and I have not looked further.)

1 0

Netflix Outage
by Josh Luthman 21 Oct '10

21 Oct '10

http://downforeveryoneorjustme.com/netflix.com Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

3 2

Re: [outages] Road Runner - Kansas City Metro - Correction to ticket number
by Michienne Dixon 21 Oct '10

21 Oct '10

Confirmation Ticket number 446-3840 Additional info - This outage is affecting the Liberty, MO portion of the Kansas City metro. A technician has been assigned. - Michienne Dixon Network Administrator liNKCity 312 Armour Rd. North Kansas City, MO 64116 www.linkcity.org <http://www.linkcity.org/> (816) 412-7990 ________________________________ From: outages-bounces(a)outages.org [mailto:outages-bounces@outages.org] On Behalf Of Michienne Dixon Sent: Thursday, October 21, 2010 3:00 PM To: outages(a)outages.org Subject: [outages] Road Runner - Kansas City Metro Looks like there is an unplanned outage for the a portion of the Kansas City metro. Confirmation Ticket number 446-384 No ETA given / No additional details provided. - Michienne Dixon Network Administrator liNKCity 312 Armour Rd. North Kansas City, MO 64116 www.linkcity.org <http://www.linkcity.org/> (816) 412-7990

1 0

Road Runner - Kansas City Metro
by Michienne Dixon 21 Oct '10

21 Oct '10

Looks like there is an unplanned outage for the a portion of the Kansas City metro. Confirmation Ticket number 446-384 No ETA given / No additional details provided. - Michienne Dixon Network Administrator liNKCity 312 Armour Rd. North Kansas City, MO 64116 www.linkcity.org <http://www.linkcity.org/> (816) 412-7990

1 0