Our upstream provider started re-announcing our prefixes to Qwest this morning and we had no issues. I assume Qwest resolved it over the weekend. Our upstream provider never got a response from Qwest on the trouble ticket because they said that AS5056 wasn't a customer of theirs. So they had to open up another ticket with Qwest to address that mistake (they've had this issue with Qwest before, apparently). Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of David Ramirez Sent: Friday, July 29, 2011 6:43 PM To: outages@outages.org Subject: Re: [outages] Several IPv6 sites down? Yes, there's definitely some issues with our IPv6 transit traffic through Qwest. We've filtered off announcements to/from Qwest. Hurricane Electric was still using Qwest though, with Qwest (attempting to) use Internap to get to us. So, we've had tofilter off Internap as well. This definitely points to an issue within Qwest's network, so we've opened a ticket with them to get this resolved. David Ramirez Network Engineer Rackspace Hosting On Jul 29, 2011, at 5:20 PM, Frank Bulk wrote:
Someone else shared with me offlist that HE tunnels from Ashburn see the Qwest brokenness when tracing to me or Rackspace...
Frank
-----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Friday, July 29, 2011 3:53 PM To: outages@outages.org Subject: Re: [outages] Several IPv6 sites down?
Our upstream provider withdrew our prefixes from Qwest and connectivity is good again. We're waiting for Qwest's QControl to investigate.
Frank
-----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Frank Bulk Sent: Friday, July 29, 2011 9:58 AM To: outages@outages.org Subject: [outages] Several IPv6 sites down?
Just a few minutes ago three of the 20+ IPv6 sites I monitor became inaccessible:
ipv6.cnn.com (IPv6-only) HOST: nagios Loss% Snt Last Avg Best Wrst StDev 1. 2607:fe28:0:1003::2 0.0% 10 1.4 1.3 1.1 2.4 0.4 2. router-core.mtcnet.net 0.0% 10 1.0 1.1 0.9 1.8 0.3 3. sxct.sxcy.mtcnet.net 0.0% 10 0.9 1.0 0.9 1.1 0.1 4. v6-siouxcenter.sxcy.137.neti 0.0% 10 2.7 3.5 2.7 4.6 0.7 5. v6-ins-db1-et-11-8-204.desm. 0.0% 10 13.1 11.0 8.3 16.6 3.6 6. v6-ins-dc1-et-8-2.desm.netin 0.0% 10 8.5 8.6 8.5 8.9 0.1 7. 2001:428:3801:210:0:1:0:1 0.0% 10 20.7 27.5 20.7 56.8 14.2 8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 9. vl-60.car2.Dallas1.Level3.ne 0.0% 10 116.7 49.0 41.1 116.7 23.8 10. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
www.charter.com (IPv4 is fine, just not IPv6) HOST: nagios Loss% Snt Last Avg Best Wrst StDev 1. 2607:fe28:0:1003::2 0.0% 10 1.1 1.1 1.1 1.2 0.0 2. router-core.mtcnet.net 0.0% 10 1.0 1.0 0.9 1.4 0.1 3. sxct.sxcy.mtcnet.net 0.0% 10 0.9 0.9 0.9 1.0 0.0 4. v6-siouxcenter.sxcy.137.neti 0.0% 10 3.4 3.8 2.8 4.7 0.6 5. v6-ins-db1-et-11-8-204.desm. 0.0% 10 8.3 8.3 8.3 8.5 0.1 6. v6-ins-dc1-et-8-2.desm.netin 0.0% 10 8.5 24.0 8.5 161.5 48.3 7. 2001:428:3801:210:0:1:0:1 0.0% 10 20.8 24.8 20.7 45.5 8.8 8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
ipv6.weather.yahoo.com (there's three AAAA records, just 2a00:1288:f006:1fe::1000 is not working) HOST: nagios Loss% Snt Last Avg Best Wrst StDev 1. 2607:fe28:0:1003::2 0.0% 10 1.2 6.5 1.1 54.3 16.8 2. router-core.mtcnet.net 0.0% 10 1.1 1.1 0.9 1.7 0.2 3. sxct.sxcy.mtcnet.net 0.0% 10 0.9 0.9 0.9 1.1 0.1 4. v6-siouxcenter.sxcy.137.neti 0.0% 10 2.7 3.9 2.7 6.3 1.1 5. v6-ins-db1-et-11-8-204.desm. 0.0% 10 13.6 9.4 8.2 13.9 2.3 6. v6-ins-dc1-et-8-2.desm.netin 0.0% 10 8.6 12.6 8.5 40.8 10.2 7. 2001:428:3801:210:0:1:0:1 0.0% 10 20.6 30.0 20.6 112.9 29.1 8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 9. vl-90.car1.Dallas1.Level3.ne 0.0% 10 41.5 41.3 41.1 41.5 0.1 10. vl-4042.car1.NewYork1.Level3 0.0% 10 58.0 58.6 57.7 63.8 1.9 11. vl-4086.edge3.London1.Level3 0.0% 10 127.2 126.9 126.5 127.3 0.3 12. vl-52.car3.London1.Level3.ne 0.0% 10 127.0 130.4 126.1 166.7 12.7 13. YAHOO-INC.car3.London1.Level 0.0% 10 126.3 126.3 126.0 127.1 0.3 14. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
Can anyone else confirm? It's like our /32 stopped propagating to some networks.
Frank
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
This email may include confidential information. If you received it in error, please delete it. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages