Re: [outages] Any known problems with Comcast in Houston area?
Vinny, Thanks -- got the screenshot. Short version is: 69.39.160.194 --> 74.95.232.29 8. 68.85.245.150 0.0% 1735 45.0 48.9 44.9 175.1 16.2 (Bearcreek) 9. 68.85.245.154 76.5% 1735 55.5 57.9 50.3 164.3 14.3 (Royalton) 10. 68.85.245.206 77.0% 1735 55.0 59.0 51.5 170.2 16.3 (Bisbee) ...and similar loss all the way to destination... 74.95.232.29 --> 69.39.160.194 5. 68.85.245.205 0.0% (Royalton) 6. 68.85.245.153 0.0% (Bearcreek) 7. 68.84.94.137 0.0% (Dallas) 8. * * * 100.0% 9. 173.167.56.182 0.0% (per ARIN, Comcast Business netblock) 10. * * * 100.0% 11. * * * 100.0% ...where the destination is eventually reachable but there is very high packet loss throughout all subsequent hops... Agreed: to me this looks like something happened within the Comcast network within Texas. It may have been as simple as circuit issues or a router rebooting or experiencing issues "briefly". If this is business-class service, you might be able to reach out to whoever your sales/support rep is and try to get an answer. Alternately, the only choices I see are to ask on either the Comcast HSI (publicly viewable) or Comcast Direct (customer-to-Comcast only) forums over on DSLR/BBR, respectively: http://www.dslreports.com/forum/comcast https://secure.dslreports.com/forum/comcastdirect Ren Provo might have some ideas or insights, if she's lurking... :-) -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Fri, Jul 06, 2012 at 06:23:05PM +0000, Vinny_Abello@Dell.com wrote:
I do, unfortunately it's a screenshot and I'm unsure if I can post to the list. I'm attaching it anyway. Hopefully it makes it through. It should to you at least, Jeremy. Look at my last post to the list as well for the updated mtr where the issue is resolved.
The problem is now cleared up and the path from the mtr initiated from my end looks to be 3 hops shorter now. It looks like they cut out the pay through Bearscreek, Royalton and Bisbee. It now goes direct from Greenspoint to Baytown. I was watching the routes change on Comcast's network. We aren't seeing an issue anymore. I was just wondering if anyone knew the cause. I'm suspecting maybe a large pipe was lost between Greenspoint and Baystown and the new path couldn't support the traffic load, but I'm just speculating. I wish I had an mtr from Comcast back to us, but alas I'm working with end users second hand on Windows when I asked for the information.
-Vinny
-----Original Message----- From: Jeremy Chadwick [mailto:outages@jdc.parodius.com] Sent: Friday, July 06, 2012 2:17 PM To: Abello, Vinny Cc: outages@outages.org Subject: Re: [outages] Any known problems with Comcast in Houston area?
Vinny,
Do you have return path traceroutes (e.g. Comcast -> Dellservices)?
When did the issue begin (include timezone)?
-- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
On Fri, Jul 06, 2012 at 06:07:28PM +0000, Vinny_Abello@Dell.com wrote:
Hello,
Is anyone aware of any issues with Comcast in the Houston area currently? We're seeing the following:
Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. vlan31.colo3.tdc.nwt.dellservices.net 0.0% 1711 7.5 5.6 0.5 201.2 27.0 2. ge1-6.core2.tdc.nwt.dellservices.net 0.0% 1711 0.5 0.5 0.4 12.1 0.5 3. ge1-9.core1.ccs.phl.dellservices.net 0.0% 1711 5.5 5.4 5.3 14.6 0.7 4. ge-5-2-pe01.philadelphia.pa.ibone.comcast.net 0.0% 1711 5.6 7.2 5.5 115.4 8.0 5. te-0-1-0-12-cr01.ashburn.va.ibone.comcast.net 0.1% 1710 19.4 15.4 9.7 28.0 3.5 6. 68.86.89.182 0.0% 1710 48.7 48.3 42.5 59.9 3.5 7. so-6-0-0-0-ar01.greenspoint.tx.houston.comcast.net 0.0% 1710 45.3 49.5 44.9 168.3 18.4 8. ae-0-0-ar04.bearcreek.tx.houston.comcast.net 0.0% 1710 45.0 49.0 44.9 175.1 16.3 9. ae-0-0-ar01.royalton.tx.houston.comcast.net 76.7% 1710 52.6 57.9 50.3 164.3 14.4 10. ae-0-0-ar01.bisbee.tx.houston.comcast.net 76.9% 1710 52.7 59.1 51.5 170.2 16.4 11. xe-0-3-0-0-sur01.baytown.tx.houston.comcast.net 72.3% 1710 56.6 56.4 51.6 108.9 4.3 12. te-4-4-ur02.baytown.tx.houston.comcast.net 78.8% 1710 56.5 57.8 51.5 98.8 4.7 13. ge-3-0-0-ten01.baytown.tx.houston.comcast.net 73.4% 1710 55.6 55.8 50.4 62.1 1.4 14. 74-95-232-29-Houston.hfc.comcastbusiness.net 69.9% 1710 62.8 64.3 57.8 85.8 3.5
Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 69.39.183.177 0.0% 1736 0.6 5.5 0.5 201.2 26.8 2. 66.97.0.13 0.0% 1736 0.5 0.5 0.4 12.1 0.5 3. 216.182.7.58 0.0% 1736 5.5 5.4 5.3 14.6 0.7 4. 173.167.56.205 0.0% 1736 5.6 7.1 5.5 115.4 7.9 5. 68.86.84.177 0.1% 1736 13.7 15.4 9.7 28.0 3.5 6. 68.86.89.182 0.0% 1735 49.2 48.3 42.5 59.9 3.5 7. 68.86.94.130 0.0% 1735 45.1 49.4 44.9 168.3 18.3 8. 68.85.245.150 0.0% 1735 45.0 48.9 44.9 175.1 16.2 9. 68.85.245.154 76.5% 1735 55.5 57.9 50.3 164.3 14.3 10. 68.85.245.206 77.0% 1735 55.0 59.0 51.5 170.2 16.3 11. 68.85.247.210 72.2% 1735 53.2 56.4 51.6 108.9 4.3 12. 68.85.246.38 78.9% 1735 65.8 57.8 51.5 98.8 4.7 13. 68.85.248.114 73.6% 1735 53.9 55.7 50.4 62.1 1.4 14. 74.95.232.29 70.0% 1735 58.8 64.3 57.8 85.8 3.5
-Vinny
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
sorry guys, haven't been watching closely today but did hear there was a fiber cut near the highway in that area... On Fri, Jul 6, 2012 at 2:42 PM, Jeremy Chadwick <outages@jdc.parodius.com> wrote:
Vinny,
Thanks -- got the screenshot. Short version is:
69.39.160.194 --> 74.95.232.29
8. 68.85.245.150 0.0% 1735 45.0 48.9 44.9 175.1 16.2 (Bearcreek) 9. 68.85.245.154 76.5% 1735 55.5 57.9 50.3 164.3 14.3 (Royalton) 10. 68.85.245.206 77.0% 1735 55.0 59.0 51.5 170.2 16.3 (Bisbee)
...and similar loss all the way to destination...
74.95.232.29 --> 69.39.160.194
5. 68.85.245.205 0.0% (Royalton) 6. 68.85.245.153 0.0% (Bearcreek) 7. 68.84.94.137 0.0% (Dallas) 8. * * * 100.0% 9. 173.167.56.182 0.0% (per ARIN, Comcast Business netblock) 10. * * * 100.0% 11. * * * 100.0%
...where the destination is eventually reachable but there is very high packet loss throughout all subsequent hops...
Agreed: to me this looks like something happened within the Comcast network within Texas. It may have been as simple as circuit issues or a router rebooting or experiencing issues "briefly".
If this is business-class service, you might be able to reach out to whoever your sales/support rep is and try to get an answer. Alternately, the only choices I see are to ask on either the Comcast HSI (publicly viewable) or Comcast Direct (customer-to-Comcast only) forums over on DSLR/BBR, respectively:
http://www.dslreports.com/forum/comcast https://secure.dslreports.com/forum/comcastdirect
Ren Provo might have some ideas or insights, if she's lurking... :-)
-- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
On Fri, Jul 06, 2012 at 06:23:05PM +0000, Vinny_Abello@Dell.com wrote:
I do, unfortunately it's a screenshot and I'm unsure if I can post to the list. I'm attaching it anyway. Hopefully it makes it through. It should to you at least, Jeremy. Look at my last post to the list as well for the updated mtr where the issue is resolved.
The problem is now cleared up and the path from the mtr initiated from my end looks to be 3 hops shorter now. It looks like they cut out the pay through Bearscreek, Royalton and Bisbee. It now goes direct from Greenspoint to Baytown. I was watching the routes change on Comcast's network. We aren't seeing an issue anymore. I was just wondering if anyone knew the cause. I'm suspecting maybe a large pipe was lost between Greenspoint and Baystown and the new path couldn't support the traffic load, but I'm just speculating. I wish I had an mtr from Comcast back to us, but alas I'm working with end users second hand on Windows when I asked for the information.
-Vinny
-----Original Message----- From: Jeremy Chadwick [mailto:outages@jdc.parodius.com] Sent: Friday, July 06, 2012 2:17 PM To: Abello, Vinny Cc: outages@outages.org Subject: Re: [outages] Any known problems with Comcast in Houston area?
Vinny,
Do you have return path traceroutes (e.g. Comcast -> Dellservices)?
When did the issue begin (include timezone)?
-- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
On Fri, Jul 06, 2012 at 06:07:28PM +0000, Vinny_Abello@Dell.com wrote:
Hello,
Is anyone aware of any issues with Comcast in the Houston area currently? We're seeing the following:
Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. vlan31.colo3.tdc.nwt.dellservices.net 0.0% 1711 7.5 5.6 0.5 201.2 27.0 2. ge1-6.core2.tdc.nwt.dellservices.net 0.0% 1711 0.5 0.5 0.4 12.1 0.5 3. ge1-9.core1.ccs.phl.dellservices.net 0.0% 1711 5.5 5.4 5.3 14.6 0.7 4. ge-5-2-pe01.philadelphia.pa.ibone.comcast.net 0.0% 1711 5.6 7.2 5.5 115.4 8.0 5. te-0-1-0-12-cr01.ashburn.va.ibone.comcast.net 0.1% 1710 19.4 15.4 9.7 28.0 3.5 6. 68.86.89.182 0.0% 1710 48.7 48.3 42.5 59.9 3.5 7. so-6-0-0-0-ar01.greenspoint.tx.houston.comcast.net 0.0% 1710 45.3 49.5 44.9 168.3 18.4 8. ae-0-0-ar04.bearcreek.tx.houston.comcast.net 0.0% 1710 45.0 49.0 44.9 175.1 16.3 9. ae-0-0-ar01.royalton.tx.houston.comcast.net 76.7% 1710 52.6 57.9 50.3 164.3 14.4 10. ae-0-0-ar01.bisbee.tx.houston.comcast.net 76.9% 1710 52.7 59.1 51.5 170.2 16.4 11. xe-0-3-0-0-sur01.baytown.tx.houston.comcast.net 72.3% 1710 56.6 56.4 51.6 108.9 4.3 12. te-4-4-ur02.baytown.tx.houston.comcast.net 78.8% 1710 56.5 57.8 51.5 98.8 4.7 13. ge-3-0-0-ten01.baytown.tx.houston.comcast.net 73.4% 1710 55.6 55.8 50.4 62.1 1.4 14. 74-95-232-29-Houston.hfc.comcastbusiness.net 69.9% 1710 62.8 64.3 57.8 85.8 3.5
Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 69.39.183.177 0.0% 1736 0.6 5.5 0.5 201.2 26.8 2. 66.97.0.13 0.0% 1736 0.5 0.5 0.4 12.1 0.5 3. 216.182.7.58 0.0% 1736 5.5 5.4 5.3 14.6 0.7 4. 173.167.56.205 0.0% 1736 5.6 7.1 5.5 115.4 7.9 5. 68.86.84.177 0.1% 1736 13.7 15.4 9.7 28.0 3.5 6. 68.86.89.182 0.0% 1735 49.2 48.3 42.5 59.9 3.5 7. 68.86.94.130 0.0% 1735 45.1 49.4 44.9 168.3 18.3 8. 68.85.245.150 0.0% 1735 45.0 48.9 44.9 175.1 16.2 9. 68.85.245.154 76.5% 1735 55.5 57.9 50.3 164.3 14.3 10. 68.85.245.206 77.0% 1735 55.0 59.0 51.5 170.2 16.3 11. 68.85.247.210 72.2% 1735 53.2 56.4 51.6 108.9 4.3 12. 68.85.246.38 78.9% 1735 65.8 57.8 51.5 98.8 4.7 13. 68.85.248.114 73.6% 1735 53.9 55.7 50.4 62.1 1.4 14. 74.95.232.29 70.0% 1735 58.8 64.3 57.8 85.8 3.5
-Vinny
_______________________________________________ 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 Fri, Jul 6, 2012 at 12:42 PM, Jeremy Chadwick <outages@jdc.parodius.com> wrote:
Vinny,
Thanks -- got the screenshot. Short version is:
69.39.160.194 --> 74.95.232.29
8. 68.85.245.150 0.0% 1735 45.0 48.9 44.9 175.1 16.2 (Bearcreek) 9. 68.85.245.154 76.5% 1735 55.5 57.9 50.3 164.3 14.3 (Royalton) 10. 68.85.245.206 77.0% 1735 55.0 59.0 51.5 170.2 16.3 (Bisbee)
...and similar loss all the way to destination...
74.95.232.29 --> 69.39.160.194
5. 68.85.245.205 0.0% (Royalton) 6. 68.85.245.153 0.0% (Bearcreek) 7. 68.84.94.137 0.0% (Dallas) 8. * * * 100.0% 9. 173.167.56.182 0.0% (per ARIN, Comcast Business netblock) 10. * * * 100.0% 11. * * * 100.0%
...where the destination is eventually reachable but there is very high packet loss throughout all subsequent hops...
Agreed: to me this looks like something happened within the Comcast network within Texas. It may have been as simple as circuit issues or a router rebooting or experiencing issues "briefly".
If this is business-class service, you might be able to reach out to whoever your sales/support rep is and try to get an answer. Alternately, the only choices I see are to ask on either the Comcast HSI (publicly viewable) or Comcast Direct (customer-to-Comcast only) forums over on DSLR/BBR, respectively:
http://www.dslreports.com/forum/comcast https://secure.dslreports.com/forum/comcastdirect
Ren Provo might have some ideas or insights, if she's lurking... :-)
This is a known issue that is being actively worked in the area. From the trouble ticket, it looks like a big fiber cut. I have no other details at the moment. Regards, John
participants (3)
-
Jeremy Chadwick -
John Neiberger -
Ren Provo