Hello, We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to: - Abovenet (Zayo) - Telia I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything. Is anyone able to corroborate?
Yeah. I'm seeing peering problems between XO and Global Crossing in San Jose. -Joel -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Ravi Pina Sent: Thursday, July 19, 2012 10:46 AM To: outages@outages.org Subject: [outages] SF Bay Area Hello, We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to: - Abovenet (Zayo) - Telia I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything. Is anyone able to corroborate? _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
traceroutes please On Thu, Jul 19, 2012 at 1:46 PM, Ravi Pina <ravi@cow.org> wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Only one I have so far: Host Loss% Last Avg Best Wrst StDev 1. 208.77.4.21 0.0% 0.5 1.3 0.4 7.6 1.6 2. 216.55.30.57 0.0% 1.2 5.1 1.1 69.5 11.2 3. ae1d0.mcr1.fremont-ca.us.xo.net 0.0% 1.8 2.9 1.3 26.6 4.4 4. vb1500.rar3.sanjose-ca.us.xo.net 0.0% 11.0 8.1 1.4 13.5 3.7 5. 207.88.14.226.ptr.us.xo.net 0.0% 1.8 3.3 1.7 33.1 5.3 6. te4-2-10G.ar2.sjc2.gblx.net 36.8% 902.1 321.5 1.9 1102. 426.1 7. ??? -Joel -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Ren Provo Sent: Thursday, July 19, 2012 10:57 AM To: Ravi Pina Cc: outages@outages.org Subject: Re: [outages] SF Bay Area traceroutes please On Thu, Jul 19, 2012 at 1:46 PM, Ravi Pina <ravi@cow.org> wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
_______________________________________________ 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
The known carrier issues are from emails and phone calls confirming. My Comcast datapoint is: traceroute to boris.mozilla.com (63.245.208.5), 64 hops max, 52 byte packets 1 10.217.24.1 (10.217.24.1) 1.431 ms 1.114 ms 1.498 ms 2 c-24-4-56-1.hsd1.ca.comcast.net (24.4.56.1) 31.688 ms 31.309 ms 9.457 ms 3 te-8-1-ur01.sfmission.ca.sfba.comcast.net (68.87.197.81) 11.608 ms 11.338 ms 9.336 ms 4 te-1-12-0-0-ar01.sfsutro.ca.sfba.comcast.net (68.85.154.138) 13.478 ms 12.279 ms 11.254 ms 5 he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.157) 22.151 ms 23.670 ms 23.831 ms 6 pos-0-5-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.87.162) 18.122 ms 35.022 ms 15.952 ms 7 * * * On Thu, Jul 19, 2012 at 01:57:10PM -0400, Ren Provo wrote:
traceroutes please
On Thu, Jul 19, 2012 at 1:46 PM, Ravi Pina <ravi@cow.org> wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
We're still seeing issues on connectivity into the SF and Sacramento area via GLX as well. Has anyone been able to isolate this down to specifically a GLX issue, or if there is something more widespread across multiple carriers? So far we do not seem to have the same issue via the legacy Level3 network. -- Jason Nesheim Manager, Network Architecture TelePacific Communications Office: 702-405-3571 Mobile: 702-885-0815 Fax: 702-724-2110 On 7/19/12 1:03 PM, "Ravi Pina" <ravi@cow.org> wrote:
The known carrier issues are from emails and phone calls confirming.
My Comcast datapoint is:
traceroute to boris.mozilla.com (63.245.208.5), 64 hops max, 52 byte packets 1 10.217.24.1 (10.217.24.1) 1.431 ms 1.114 ms 1.498 ms 2 c-24-4-56-1.hsd1.ca.comcast.net (24.4.56.1) 31.688 ms 31.309 ms 9.457 ms 3 te-8-1-ur01.sfmission.ca.sfba.comcast.net (68.87.197.81) 11.608 ms 11.338 ms 9.336 ms 4 te-1-12-0-0-ar01.sfsutro.ca.sfba.comcast.net (68.85.154.138) 13.478 ms 12.279 ms 11.254 ms 5 he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.157) 22.151 ms 23.670 ms 23.831 ms 6 pos-0-5-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.87.162) 18.122 ms 35.022 ms 15.952 ms 7 * * *
On Thu, Jul 19, 2012 at 01:57:10PM -0400, Ren Provo wrote:
traceroutes please
On Thu, Jul 19, 2012 at 1:46 PM, Ravi Pina <ravi@cow.org> wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
_______________________________________________ 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
On 7/19/12 11:29 AM, Jason Nesheim wrote:
We're still seeing issues on connectivity into the SF and Sacramento area via GLX as well. Has anyone been able to isolate this down to specifically a GLX issue, or if there is something more widespread across multiple carriers? So far we do not seem to have the same issue via the legacy Level3 network.
Just for fun I called Global Crossing regarding my circuit and I'm still in the initial pick up hold loop after 20 minutes. So I'm guessing they're busy. Their online tool for reading master tickets just returns "Error trying to retrieve Cases". I've kicked the BGP prefs on my circuit with them to a minimum and things are better for me. ~Seth
On 7/19/12 11:36 AM, Seth Mattinen wrote:
On 7/19/12 11:29 AM, Jason Nesheim wrote:
We're still seeing issues on connectivity into the SF and Sacramento area via GLX as well. Has anyone been able to isolate this down to specifically a GLX issue, or if there is something more widespread across multiple carriers? So far we do not seem to have the same issue via the legacy Level3 network.
Just for fun I called Global Crossing regarding my circuit and I'm still in the initial pick up hold loop after 20 minutes. So I'm guessing they're busy. Their online tool for reading master tickets just returns "Error trying to retrieve Cases".
Ah, it finally loaded. San Jose, CA an automated tool made unexpected config changes that inadvertently impacted IP Services. ~Seth
On 7/19/12 10:46 AM, Ravi Pina wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
Hi Ravi - We are seeing plenty of issues too, some things dying in GLBX or twtelecom between our office in the North bay and Sacramento. Also regular trouble getting to Yahoo!, some google, gotomeetin/citrix. Our network provider is Telepacific.net Some traceroutes in case they help someone. I can ssh to a data center in SFO, and then get to our provider in Sac (herakles) - so there are things afoot somewhere in between the other route between novato <-> sac. thx Scott trace route from office to Sac -- traceroute to ahmes.infocentricity.com (65.74.143.195), 30 hops max, 38 byte packets 1 chapman (192.168.11.1) 1.231 ms 1.454 ms 0.948 ms 2 71-6-66-65.static-ip.telepacific.net (71.6.66.65) 1.695 ms 1.573 ms 1.987 ms 3 68-233-217-81.static-ip.telepacific.net (68.233.217.81) 6.000 ms 5.584 ms 5.978 ms 4 vl1.sw5.snrfca.telepacific.net (216.31.224.193) 6.033 ms 5.563 ms 5.959 ms 5 gi21.cr1.snrfca.telepacific.net (216.31.224.241) 6.021 ms 5.560 ms 5.987 ms 6 pos10.cr2.snjsca.telepacific.net (66.7.224.89) 8.026 ms 6.546 ms 7.986 ms 7 208.178.247.173 (208.178.247.173) 8.023 ms 8.606 ms 8.928 ms 8 te2-1-10G.ar2.SJC2.gblx.net (67.16.162.69) 548.837 ms po2-20G.ar2.SJC2.gblx.net (67.17.105.6) 801.942 ms te2-1-10G.ar2.SJC2.gblx.net (67.16.162.69) 351.050 ms 9 TWTC.TenGigabitEthernet9-1.ar2.SJC2.gblx.net (64.212.32.234) 19.534 ms 17.610 ms 18.982 ms 10 oak1-ar3-ge-1-0-0-0.us.twtelecom.net (66.192.247.122) 19.998 ms oak1-ar3-ge-1-1-0-0.us.twtelecom.net (206.222.120.210) 20.441 ms 19.422 ms 11 * * * 12 * * * trace route from Sacramento to office -- traceroute to corporate.infocentricity.com (71.6.66.66), 64 hops max, 40 byte packets 1 50.157.74.65.static.heraklesdata.net (65.74.157.50) 1.50 ms 1.219 ms 0.734 ms 2 ge010-crt1-sacca.heraklesdata.net (65.74.128.22) 1.101 ms 1.226 ms 0.735 ms 3 216.55.46.13 (216.55.46.13) 1.601 ms 1.352 ms 1.609 ms 4 ae1d0.mcr1.roseville-ca.us.xo.net (216.156.1.77) 1.726 ms 1.600 ms 1.609 ms 5 vb1510.rar3.sanjose-ca.us.xo.net (216.156.0.153) 8.224 ms 7.97 ms 14.852 ms 6 207.88.14.226.ptr.us.xo.net (207.88.14.226) 5.352 ms 5.349 ms 5.231 ms 7 te4-2-10G.ar2.sjc2.gblx.net (64.208.110.113) 7.973 ms 15.716 ms 4.982 ms 8 * * * 9 * * * -------------------------------------------------------------------------------- Scott Nelson Windels - Director of Operations InfoCentricity - http://www.infocentricity.com 415-493-2090 x213 --------------------------------------------------------------------------------
We are seeing issues with Comcast customers not being able to reach us Sent from my iPhone On Jul 19, 2012, at 10:46, Ravi Pina <ravi@cow.org> wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
what does 'us' mean? source and destination please. On Thu, Jul 19, 2012 at 2:01 PM, Tony <pasq77@gmail.com> wrote:
We are seeing issues with Comcast customers not being able to reach us
Sent from my iPhone
On Jul 19, 2012, at 10:46, Ravi Pina <ravi@cow.org> wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
_______________________________________________ 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
We're getting a few reports of a customers, one we've confirmed is located in Palo Alto, unable to reach our Chicago-hosted service, while all of our monitoring reports our services are up from here. Nothing concrete, but seems like it might be related to the issues you're talking about. Paul Hinze Developer Braintree Payments On Thursday, July 19, 2012 at 12:46 PM, Ravi Pina wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
_______________________________________________ Outages mailing list Outages@outages.org (mailto:Outages@outages.org) https://puck.nether.net/mailman/listinfo/outages
On 7/19/12 10:46 AM, Ravi Pina wrote:
Hello,
We're seeing issues with many providers in the SF Bay Area which include, but apear to not be limited to:
- Abovenet (Zayo) - Telia
I'm also seeing what appears to be peering issues with Comcast but that is more gut than anything.
Is anyone able to corroborate?
I was getting random grief with traffic going via my Global Crossing circuit that terminates in Sunnyvale (couldn't resolve Yahoo DNS for one). Rerouting via Sprint mitigated most of it for me. ~Seth
participants (8)
-
Jason Nesheim -
Joel Stalder -
Paul Hinze -
Ravi Pina -
Ren Provo -
Scott Nelson Windels -
Seth Mattinen -
Tony