Specific client can't reach specific IP address

[jasonwood]

Starting today, at one of my locations, if you try to access my head office IP address (or any domains that point to it), there is no response (tried via web browser, jabber, database access, etc.). That location does not seem to have problems accessing any other IP addresses/web sites, and no other location seems to have any trouble reaching ours!

In case it helps, here is a traceroute from one of the locations that IS able to connect:

Traceroute has started ...

traceroute to 207.112.121.141 (207.112.121.141), 64 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 2.316 ms 1.183 ms 1.531 ms
2 on-tor-frn-a72-02.look.ca (207.136.64.7) 47.144 ms 49.735 ms 40.425 ms
3 on-tor-frn-r12-01-ge2-0-v212.look.ca (207.136.65.149) 42.406 ms 40.616 ms 42.660 ms
4 on-tor-frn-r12-02-pos-ch1.look.ca (207.136.65.106) 49.598 ms 49.086 ms 52.014 ms
5 gw-primus.torontointernetxchange.net (198.32.245.22) 47.944 ms 52.217 ms 47.480 ms
6 216.254.129.3 (216.254.129.3) 40.559 ms 44.681 ms 48.694 ms
7 * * *
8 * * *
9 * * *
10 * * *

(note: head office ISP is primus)

and here's a traceroute from the location that can't connect to us:

Traceroute has started ...

traceroute to 207.112.121.141 (207.112.121.141), 64 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 21.021 ms 1.083 ms 1.092 ms
2 10.18.192.1 (10.18.192.1) 12.304 ms 12.706 ms 12.627 ms
3 154.11.88.194 (154.11.88.194) 12.340 ms 12.157 ms 12.063 ms
4 154.11.10.70 (154.11.10.70) 42.829 ms 33.726 ms 32.818 ms
5 154.11.2.54 (154.11.2.54) 33.816 ms 33.327 ms 33.101 ms
6 te9-2.mpd01.sjc04.atlas.cogentco.com (154.54.0.173) 32.995 ms 32.983 ms 33.341 ms
7 te9-1.ccr02.sfo01.atlas.cogentco.com (154.54.0.177) 34.308 ms te3-1.mpd01.sfo01.atlas.cogentco.com (154.54.28.81) 34.714 ms te8-2.ccr02.sfo01.atlas.cogentco.com (154.54.7.173) 33.753 ms
8 te8-3.mpd01.mci01.atlas.cogentco.com (154.54.6.166) 71.630 ms te2-1.ccr02.mci01.atlas.cogentco.com (154.54.6.41) 72.139 ms te8-3.mpd01.mci01.atlas.cogentco.com (154.54.6.166) 71.916 ms
9 te3-1.mpd02.ord01.atlas.cogentco.com (154.54.3.201) 69.405 ms 69.080 ms *
10 te2-3.mpd01.yyz02.atlas.cogentco.com (154.54.7.17) 85.984 ms te8-1.mpd01.yyz02.atlas.cogentco.com (154.54.27.250) 87.228 ms te2-3.mpd01.yyz02.atlas.cogentco.com (154.54.7.17) 85.676 ms
11 38.104.158.130 (38.104.158.130) 275.707 ms 145.169 ms 81.118 ms
12 216.254.129.3 (216.254.129.3) 81.275 ms 80.640 ms 81.000 ms
13 * * *
14 * * *


According to this...

http://www.primustel.ca/en/business/security/performance.php

...Primus has backbone connections to both Toronto Internet Exchange and Cogent (and others). Is it possible that Primus's connection to Cogent is currently down and for some reason my bad location's ISP is still trying to route through it?

 

[jasonwood]

now working again... but I'd sure love to know what the heck that was all about.

 

[North323]

canadian pixie dust?

 

[burtsbees]

...Primus has backbone connections to both Toronto Internet Exchange and Cogent (and others). Is it possible that Primus's connection to Cogent is currently down and for some reason my bad location's ISP is still trying to route through it?"

Yes.

The packets fell into a black hole. I would have started a wireshark session on the other end, but that's just me. Now you won't be able to sleep tonight, or the next few nights for that matter...lol

/