Hum, Traceroute is not as nice traceroute to 192.250.24.1 (192.250.24.1), 30 hops max, 60 byte packets 1 GW (192.168.0.2) 0.459 ms 0.435 ms 0.422 ms 2 * * * 3 10.170.182.81 (10.170.182.81) 18.417 ms 18.711 ms 18.702 ms 4 216.113.124.126 (216.113.124.126) 16.611 ms 17.774 ms 17.774 ms 5 216.113.122.74 (216.113.122.74) 45.746 ms 46.035 ms 46.025 ms 6 144.232.7.250 (144.232.7.250) 44.529 ms 45.507 ms 45.178 ms 7 be3013.ccr21.ord03.atlas.cogentco.com (154.54.10.37) 38.741 ms 35.537 ms 37.036 ms 8 24.156.159.153 (24.156.159.153) 31.433 ms 32.658 ms 29.417 ms 9 24.156.144.177 (24.156.144.177) 34.106 ms 32.621 ms van58-10-228-225.dynamic.rogerstelecom.net (209.148.228.225) 30.299 ms 10 24.156.144.126 (24.156.144.126) 30.339 ms 30.329 ms 30.055 ms 11 24.153.4.185 (24.153.4.185) 32.955 ms 34.112 ms 34.146 ms 12 gi-3-0-0.agw02.hrnr.phub.net.cable.rogers.com (24.153.7.82) 30.935 ms 32.375 ms 32.356 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * 206.186.1.10 (206.186.1.10) 37.869 ms Gary Baribault Courriel: gary@baribault.net GPG Key: 0x685430d1 Fingerprint: 9E4D 1B7C CB9F 9239 11D9 71C3 6C35 C6B7 6854 30D1 On 09/18/2014 05:08 PM, sthaug@nethelp.no wrote:
The 192.250.24 addresses have been reachable for several months in the current configuration with no reported issues. Since the 16th we have been hearing reports that destinations in that block are unavailable for some.
Several looking glass' report network not in table. Visible from here (AS 2116, Norway).
Do you have a pingable IP address in the range which is problematic? That would help others who are willing to debug your issue enormously. 192.250.24.1 and 192.250.24.2 (for example) are pingable from 2116.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no