[outages] Comcast residential in bay area

[Grant Ridder]

Already did that :)
The issue just recovered on its own.
Thanks to those who replied!


On Sun, Dec 22, 2013 at 9:19 PM, Jeremy Chadwick <jdc at koitsu.org> wrote:

> Time to try power-cycling all involved devices.  :-)
>
> --
> | Jeremy Chadwick                                   jdc at koitsu.org |
> | UNIX Systems Administrator                http://jdc.koitsu.org/ |
> | Making life hard for others since 1977.             PGP 4BD6C0CB |
>
> On Sun, Dec 22, 2013 at 09:17:12PM -0800, Grant Ridder wrote:
> > Interesting... I am in Mountain View as well and only have native v6.  No
> > v4 still.
> >
> >
> > On Sun, Dec 22, 2013 at 9:16 PM, Jeremy Chadwick <jdc at koitsu.org> wrote:
> >
> > > From Mountain View CA.  I don't do IPv6.  This is to 8.8.8.8 -- looks
> > > fine:
> > >
> > >                                                   Packets
> > > Pings
> > >  Host                                           Loss%   Snt   Rcv  Last
> > > Avg  Best  Wrst
> > >  1. gw.home.lan                                  0.0%    31    31   0.3
> > > 0.3   0.2   0.5
> > >  2. 76.102.12.1                                  0.0%    31    31   8.6
> > > 9.0   8.1  13.0
> > >  3. te-0-2-0-5-ur06.santaclara.ca.sfba.comcast.  0.0%    31    31   8.3
> > >  10.7   8.3  14.7
> > >  4. te-1-1-0-13-ar01.oakland.ca.sfba.comcast.ne  0.0%    30    30
>  12.4
> > >  12.0  10.2  16.8
> > >  5. be-90-ar01.sfsutro.ca.sfba.comcast.net       0.0%    30    30
>  12.6
> > >  13.2  11.3  17.5
> > >  6. he-3-9-0-0-cr01.sanjose.ca.ibone.comcast.ne  0.0%    30    30
>  13.6
> > >  15.6  12.8  18.1
> > >  7. pos-0-2-0-0-pe01.529bryant.ca.ibone.comcast  0.0%    30    30  19.3
> > >  18.0  14.1  30.4
> > >  8. 66.208.228.226                               3.3%    30    29  89.4
> > >  45.7  25.7  89.5
> > >  9. 72.14.232.136                                0.0%    30    30  15.4
> > >  16.0  15.0  23.5
> > > 10. 209.85.250.60                                3.3%    30    29  15.6
> > >  16.8  15.2  29.0
> > > 11. 72.14.232.63                                 3.3%    30    29  31.3
> > >  32.3  31.1  49.4
> > > 12. 72.14.233.200                                0.0%    30    30  34.7
> > >  35.0  34.2  40.9
> > > 13. 216.239.48.167                               0.0%    30    30  34.5
> > >  36.0  34.2  59.1
> > > 14. ???
> > > 15. google-public-dns-a.google.com               0.0%    30    30
>  34.4
> > >  34.8  34.3  37.0
> > >
> > > Review of periodic mtrs to my workplace (Campbell) as well as my VPS
> > > (southern California) don't show any anomalies either.
> > >
> > > --
> > > | Jeremy Chadwick                                   jdc at koitsu.org |
> > > | UNIX Systems Administrator                http://jdc.koitsu.org/ |
> > > | Making life hard for others since 1977.             PGP 4BD6C0CB |
> > >
> > > On Sun, Dec 22, 2013 at 09:11:49PM -0800, Grant Ridder wrote:
> > > > My residential internet on Comcast started having high ping times and
> > > > packet loss to the internet.   I rebooted my router, and now i have
> > > native
> > > > IPv6 only.  I can not access IPv4 addresses.  Can anyone else in the
> Bay
> > > > area on comcast replicate this?
> > > >
> > > > -Grant
> > > >
> > > >
> > > >
> > > >
> > > > C:\Users\ridderg>tracert 8.8.8.8
> > > >
> > > > Tracing route to google-public-dns-a.google.com [8.8.8.8]
> > > > over a maximum of 30 hops:
> > > >
> > > >   1     1 ms    <1 ms    <1 ms  192.168.1.1
> > > >   2     *        *        *     Request timed out.
> > > >   3     *        *        *     Request timed out.
> > > >   4     *        *        *     Request timed out.
> > > >   5     *        *        *     Request timed out.
> > > >   6  ^C
> > > > C:\Users\ridderg>
> > > >
> > > > C:\Users\ridderg>ping google.com
> > > >
> > > > Pinging google.com [2607:f8b0:4005:802::1005] with 32 bytes of data:
> > > > Reply from 2607:f8b0:4005:802::1005: time=14ms
> > > > Reply from 2607:f8b0:4005:802::1005: time=14ms
> > > > Reply from 2607:f8b0:4005:802::1005: time=14ms
> > > >
> > > > Ping statistics for 2607:f8b0:4005:802::1005:
> > > >     Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
> > > > Approximate round trip times in milli-seconds:
> > > >     Minimum = 14ms, Maximum = 14ms, Average = 14ms
> > > > Control-C
> > > > ^C
> > > > C:\Users\ridderg>ping -4 google.com
> > > >
> > > > Pinging google.com [74.125.239.132] with 32 bytes of data:
> > > > Request timed out.
> > > > Request timed out.
> > > > Request timed out.
> > > > Request timed out.
> > > >
> > > > Ping statistics for 74.125.239.132:
> > > >     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> > > >
> > > > C:\Users\ridderg>
> > >
> > > > _______________________________________________
> > > > Outages mailing list
> > > > Outages at outages.org
> > > > https://puck.nether.net/mailman/listinfo/outages
> > >
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20131222/88ae0843/attachment.htm>