It looks like they just rerouted traffic through another device and I'm
able to hit 4.2.2.2 now.
Tracing route to b.resolvers.Level3.net [4.2.2.2]
over a maximum of 30 hops:
1<1 ms<1 ms<1 ms gw
2 8 ms 8 ms 7 ms 142.254.150.77
324 ms23 ms21 ms ae59.nolm
I'm seeing the same problem from RoadRunner/Spectrum 96.10.190.170
$ mtr --report-wide 4.2.2.2
Start: 2019-10-09T14:29:48-0400
HOST: asdfLoss% Snt Last Avg Best
Wrst StDev
1.|-- _gateway 0.0%100.3 0.3 0.2
0.3
We have a customer saying there are issues between Level3/CenturyLink and
them, but I'm not seeing anything from traceroutes/mtr's.
Well besides the normal deny exceed rules in place on both providers.
Sincerely,
Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300
___
My ticket # is sci-251834 and I sent them Shawn's traceroutes as well.
Thanks,
Eric Rechnitzer
eric.rechnit...@gmail.com
On Wed, Oct 9, 2019 at 11:16 AM Jordan Morris via Outages <
outages@outages.org> wrote:
> I think you are correct that this is the root cause a few of the sites
> even the al
I think you are correct that this is the root cause a few of the sites even the
alternative DNS servers routed out 0.ae1.pr0.dca20.tbone.rr.com and went dead
in the water after that.
Jordan Morris
SALES: 800-249-1348
SUPPORT: 888-920-5685
www.crosswindvoip.com
2201 N. Camino Principal Ste. 125
I've noticed the exact same thing since yesterday on my home Spectrum
network. Traceroute to 4.2.2.2 dies on the same hop. I spent the last hour
on the phone arguing with them and they're finally opening a ticket to look
into it.
C:\Users\Eric>tracert 4.2.2.2
Tracing route to b.resolvers.Level3.n
potentially related, we are seeing problems with
rr/charter/spectrum/brighthouse/tw getting traffic back to
level3/centurylink this morning. Seems anything routing via
0.ae0.pr0.dca20.tbone.rr.com
just dies if its destined for as3356. If it takes a path via
Atlanta, works great. Interestingly,
Seeing some odd name resolutions errors in the NC and SC regions getting random
name resolutions that resolve to mail*.newsgeni.us. This is happening across
multiple domain names even seeing it with reverse IP resolutions. Our
monitoring alerts detected this so far at about 10+ sites in those st
