[TriLUG] Time-Warner (Spectrum) outage tonight
Brian via TriLUG
trilug at trilug.org
Wed Jan 3 11:08:22 EST 2018
I had the same initial thought, but the thread on nanog that Zach
mentioned is probably the explanation this time; just good old bad
behavior on the internet instead of corporate collusion.
On 01/03/2018 10:01 AM, Jeremy Davis via TriLUG wrote:
> hmmm.. almost smells like the compromise of net neutrality.. maybe not but
> it still offers a glimpse of what to expect if net neutrality goes away.. I
> can see how the ISPs would love to cramp Google's style if they could.. I
> don't fully understand the net neutrality Legislation that is supposedly
> being repealed. However, after all the Google Fiber competition that forced
> the ISPs to react.. a smart retaliation tactic may be to entrench more
> lobbyists on the the net neutrality repeal. Google was and probably still
> is the site with the most traffic on the Internet. So I would assume, based
> on my limited knowledge, Google would be among the first victims the ISPs
> go after.
>
> Hopefully we can still access trilug.org after the net neutrality
> Legislation is finalized... the ISPs would probably LOL at our pizza fund..
>
> Jeremy
>
>
> On Jan 2, 2018 8:55 PM, "David Burton via TriLUG" <trilug at trilug.org> wrote:
>
> How many of y'all on Spectrum/TWC in the Triangle area are having internet
> problems?
>
> I'm in Cary, and my Spectrum/TWC internet is working fine.
>
> However, my friends in Raleigh have no internet connectivity to Google,
> Yahoo, etc. They can get to my server, in my house, and everything works
> fine, including remote control w/ VNC, but they can't get to much of
> anything else. They can't even get to *http://spectrum.com/support/
> <http://spectrum.com/support/>*
>
> The problem has been ongoing since before 6pm (at least 3 hours, at this
> point).
>
> Here's a tracert from Raleigh (my friends' house) to me; as you can see, it
> works fine:
>
> *C:\>tracert 98.26.64.108 <http://98.26.64.108>
>
> Tracing route to cpe-98-26-64-108.nc.res.rr.com
> <http://cpe-98-26-64-108.nc.res.rr.com> [98.26.64.108]
> over a maximum of 30 hops:
>
> 1 1 ms 1 ms 1 ms 192.168.3.1
> 2 11 ms 16 ms 13 ms mta-107-13-224-1.nc.rr.com
> <http://mta-107-13-224-1.nc.rr.com> [107.13.224.1]
> 3 25 ms 37 ms 42 ms cpe-174-111-105-193.triad.res.rr.com
> <http://cpe-174-111-105-193.triad.res.rr.com> [174.111.105.193]
> 4 * 15 ms 20 ms cpe-024-025-041-000.ec.res.rr.com
> <http://cpe-024-025-041-000.ec.res.rr.com> [24.25.41.0]
> 5 34 ms 1047 ms 154 ms cpe-024-025-062-049.ec.res.rr.com
> <http://cpe-024-025-062-049.ec.res.rr.com> [24.25.62.49]
> 6 15 ms 14 ms * cpe-174-111-102-193.triad.res.rr.com
> <http://cpe-174-111-102-193.triad.res.rr.com> [174.111.102.193]
> 7 28 ms 34 ms 40 ms cpe-98-26-64-108.nc.res.rr.com
> <http://cpe-98-26-64-108.nc.res.rr.com> [98.26.64.108]
>
> Trace complete.*
>
>
> Going from my house to theirs also works fine.
>
> But here's a tracert from my friends' house to Google:
>
> *C:\>tracert www.google.com <http://www.google.com>
>
> Tracing route to www.google.com <http://www.google.com> [172.217.7.228
> <http://172.217.7.228>]
> over a maximum of 30 hops:
>
> 1 1 ms <1 ms <1 ms 192.168.3.1
> 2 18 ms 15 ms 15 ms mta-107-13-224-1.nc.rr.com
> <http://mta-107-13-224-1.nc.rr.com> [107.13.224.1]
> 3 30 ms 32 ms 31 ms cpe-174-111-105-193.triad.res.rr.com
> <http://cpe-174-111-105-193.triad.res.rr.com> [174.111.105.193]
> 4 12 ms 12 ms 14 ms cpe-024-025-041-000.ec.res.rr.com
> <http://cpe-024-025-041-000.ec.res.rr.com> [24.25.41.0]
> 5 17 ms 15 ms 16 ms 24.93.67.200
> 6 22 ms 22 ms 23 ms
> bu-ether15.asbnva1611w-bcr00.tbone.rr.com
> <http://bu-ether15.asbnva1611w-bcr00.tbone.rr.com> [66.109.6.80]
> 7 22 ms 21 ms 56 ms 0.ae0.pr1.dca10.tbone.rr.com
> <http://0.ae0.pr1.dca10.tbone.rr.com> [107.14.17.200]
> 8 20 ms 19 ms 23 ms
> ix-ae-17-0.tcore2.AEQ-Ashburn.as6453.net
> <http://ix-ae-17-0.tcore2.AEQ-Ashburn.as6453.net> [216.6.87.149]
> 9 * * * Request timed out.
> 10 * * * Request timed out.
> 11 * * * Request timed out.
> 12 * * * Request timed out.
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.*
>
>
> After a modem reboot we did another one:
>
> *C:\>tracert www.google.com <http://www.google.com>
>
> Tracing route to www.google.com <http://www.google.com> [216.58.217.68
> <http://216.58.217.68>]
> over a maximum of 30 hops:
>
> 1 3 ms 1 ms 1 ms 192.168.3.1
> 2 15 ms 19 ms 19 ms mta-107-13-224-1.nc.rr.com
> <http://mta-107-13-224-1.nc.rr.com> [107.13.224.1]
> 3 28 ms 32 ms 32 ms cpe-174-111-118-177.triad.res.rr.com
> <http://cpe-174-111-118-177.triad.res.rr.com> [174.111.118.177]
> 4 14 ms 14 ms 14 ms cpe-024-025-041-002.ec.res.rr.com
> <http://cpe-024-025-041-002.ec.res.rr.com> [24.25.41.2]
> 5 17 ms 33 ms 26 ms be31.chrcnctr01r.southeast.rr.com
> <http://be31.chrcnctr01r.southeast.rr.com> [24.93.64.186]
> 6 25 ms 30 ms 31 ms
> bu-ether14.atlngamq46w-bcr00.tbone.rr.com
> <http://bu-ether14.atlngamq46w-bcr00.tbone.rr.com> [66.109.6.82]
> 7 25 ms 31 ms 24 ms
> bu-ether11.atlngamq47w-bcr01.tbone.rr.com
> <http://bu-ether11.atlngamq47w-bcr01.tbone.rr.com> [66.109.6.35]
> 8 27 ms 40 ms 24 ms 0.ae0.pr1.atl20.tbone.rr.com
> <http://0.ae0.pr1.atl20.tbone.rr.com> [107.14.17.184]
> 9 30 ms 22 ms 23 ms
> ix-ae-14-0.tcore1.A56-Atlanta.as6453.net
> <http://ix-ae-14-0.tcore1.A56-Atlanta.as6453.net> [64.86.113.37]
> 10 * * * Request timed out.
> 11 * * * Request timed out.
> 12 * * * Request timed out.
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.*
>
>
> I spent a lot of time on the phone with a pleasant, foreign-sounding,
> Spectrum tech support rep named "J.C." He was very sympathetic, but all he
> could tell me is that they are working on it.
>
> I sent him those tracert logs by pasting them into a text file on my
> server, and then reading the URL over the phone to him. (The powers that be
> at Spectrum don't want their tech support reps to be able to solve
> customers' problems, so they block their tech support reps' access to email
> -- and they wonder why we all hate them so much.)
>
> Anyhow, I'm wondering: how widespread is this outage, tonight?
>
> Dave
> M: 919-244-3316 <(919)%20244-3316>
> --
> This message was sent to: Jeremy Davis <jeremyhwllc at gmail.com>
> To unsubscribe, send a blank message to trilug-leave at trilug.org from that
> address.
> TriLUG mailing list : https://www.trilug.org/mailman/listinfo/trilug
> Unsubscribe or edit options on the web : https://www.trilug.org/mailman
> /options/trilug/jeremyhwllc%40gmail.com
> Welcome to TriLUG: http://trilug.org/welcome
>
More information about the TriLUG
mailing list