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