Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Job Snijders via Outages
On Wed, Nov 23, 2016 at 01:19:13PM -0600, Doug Roberts wrote: > What about 45.31.217.222? It seems to respond from everywhere except NTT: > https://puu.sh/ss7RV/82cedcec8e.png double bang for your buck in some cases! :-) j...@ntt02.ring.nlnog.net:~$ ping 45.31.217.222 PING 45.31.2

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Jared Mauch via Outages
Yeah, so totally unreachable from any of the ATLAS probes, but measurement is still running. https://atlas.ripe.net/measurements/6939080/#!probes - Jared > On Nov 23, 2016, at 2:08 PM, Doug Roberts wrote: > > Here's what I see from here: > > https://puu.sh/ss76o/27b9de01e6.png > > > > >

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Doug Roberts via Outages
What about 45.31.217.222? It seems to respond from everywhere except NTT: https://puu.sh/ss7RV/82cedcec8e.png The footer is corporate placed :p. -- *Doug Roberts* d...@dougr.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX)

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Job Snijders via Outages
Hi Doug, On Wed, Nov 23, 2016 at 01:08:19PM -0600, Doug Roberts via Outages wrote: > Here's what I see from here: > > https://puu.sh/ss76o/27b9de01e6.png I can't ping that IP address from anywhere outside AT&T, so this is not NTT specific. Used the NLNOG RING to do the measurement: https://ring

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Jared Mauch via Outages
I see that going to AT&T not Level3, let me keep looking, eg: r02.atlnga05.us.bb-re1> traceroute 107.207.236.1 traceroute to 107.207.236.1 (107.207.236.1), 30 hops max, 40 byte packets 1 ge-100-0-0-1.r04.atlnga05.us.bb.gin.ntt.net (129.250.4.88) 1.027 ms 0.807 ms 0.760 ms 2 192.205.36.

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Doug Roberts via Outages
Here's what I see from here: https://puu.sh/ss76o/27b9de01e6.png -- *Doug Roberts* d...@dougr.com 251-308-4040 (Mobile) 228-254-3035 (Biloxi) 850-361-3300 (Pensacola) 334-543-0222 (Montgomery) 251-308-1333 (FAX) CONFIDENTIALITY NOTICE: The contents of this e-mail message and

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Jared Mauch via Outages
> On Nov 23, 2016, at 1:33 PM, Doug Roberts via Outages > wrote: > > NTT is indeed having issues. Pinging from ATL to us here in Alabama fails: > > Query Results: > Router: Atlanta, GA - US > Command: ping 45.31.x.x > > Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds:

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Dovid Bender via Outages
>From NY: r...@homer.my.net> ping source 165.254.XX.XX 45.31.217.222 PING 45.31.217.222 (45.31.217.222): 56 data bytes 64 bytes from 45.31.217.222: icmp_seq=0 ttl=53 time=43.286 ms 64 bytes from 45.31.217.222: icmp_seq=0 ttl=53 time=44.087 ms (DUP!) 64 bytes from 45.31.217.222: icmp_seq=1 ttl=53 ti

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Ca By via Outages
Must be a hashing issue if 1 works but 2 does not on peering between Level3 and NTT Other NYC looking glass show both 1 and 2 up. http://imgur.com/a/Z6JiM On Wed, Nov 23, 2016 at 10:31 AM, Dylan Page wrote: > The A resolver responds when testing from NTT New York > > *Query Results:* > *Rou

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Doug Roberts via Outages
NTT is indeed having issues. Pinging from ATL to us here in Alabama fails: *Query Results:* *Router: *Atlanta, GA - US *Command:* ping 45.31.x.x Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds: . Success rate is 0 percent (0/5) -- *Doug Roberts* d...@dougr.com 251-308

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Dylan Page via Outages
The A resolver responds when testing from NTT New York *Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.1 Sending 5, 100-byte ICMP Echos to 4.2.2.1, timeout is 2 seconds: ! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms B resolver is still down *Quer

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Dovid Bender via Outages
Must have been a temp. issue. Working from me from 60 Hudson and from their LG as well. *Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2 Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: . Success rate is 0 percent (0/5) On Wed, Nov 23, 2016 at 1:17 PM, C

Re: [outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Michael Snyder via Outages
No issues with our NYC location. We are in the Financial District... On Wed, Nov 23, 2016 at 12:17 PM, Ca By via Outages wrote: > http://www.us.ntt.net/support/looking-glass/ > > *Query Results:* > *Router: *New York, NY - US > *Command:* ping 4.2.2.2 > > > Sending 5, 100-byte ICMP Echos to 4.2.

[outages] NTT to Level3 routing issue in NYC?

2016-11-23 Thread Ca By via Outages
http://www.us.ntt.net/support/looking-glass/ *Query Results:* *Router: *New York, NY - US *Command:* ping 4.2.2.2 Sending 5, 100-byte ICMP Echos to 4.2.2.2, timeout is 2 seconds: . Success rate is 0 percent (0/5) But it seems to work fine from Ashburn *Query Results:* *Router: *Ashburn,