[outages] NTT to Level3 routing issue in NYC?

[Job Snijders]

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! :-)

	job at ntt02.ring.nlnog.net:~$ ping 45.31.217.222
	PING 45.31.217.222 (45.31.217.222) 56(84) bytes of data.
	64 bytes from 45.31.217.222: icmp_req=1 ttl=51 time=128 ms
	64 bytes from 45.31.217.222: icmp_req=1 ttl=51 time=128 ms (DUP!)
	64 bytes from 45.31.217.222: icmp_req=2 ttl=51 time=128 ms
	64 bytes from 45.31.217.222: icmp_req=2 ttl=51 time=128 ms (DUP!)
	^C
	--- 45.31.217.222 ping statistics ---
	2 packets transmitted, 2 received, +2 duplicates, 0% packet loss, time 999ms
	rtt min/avg/max/mdev = 128.434/128.668/128.947/0.484 ms
	job at ntt02.ring.nlnog.net:~$

or in new york:

	RP/0/RP0/CPU0:r07.nycmny01.us.bb#ping 45.31.217.222 source 129.250.0.143
	Type escape sequence to abort.
	Sending 5, 100-byte ICMP Echos to 45.31.217.222, timeout is 2 seconds:
	!!!!!
	Success rate is 100 percent (5/5), round-trip min/avg/max = 43/43/44 ms
	RP/0/RP0/CPU0:r07.nycmny01.us.bb#

Kind regards,

Job