Cogent / Internap issue ??

Mailman List Mirror (Read Only)
1

We are having troubles reaching services on the other side of cogent/internap peering. Anyone else seeing issues?

Basically 14607 -> 6128 -> 174 -> 14744.

Type escape sequence to abort.
Tracing the route to 72.5.52.199
VRF info: (vrf in name/id, vrf out name/id)
  1 24.157.32.249 [AS 6128] 4 msec 4 msec 4 msec
  2 24.38.117.6 [AS 6128] 4 msec 8 msec 4 msec
  3 167.206.183.29 [AS 6128] 4 msec 4 msec 8 msec
  4 * * *
  5 * * *
  6 154.54.47.17 [AS 174] 4 msec
    154.54.47.29 [AS 174] 8 msec
    154.54.44.69 [AS 174] 4 msec
  7 66.28.4.202 [AS 174] 28 msec 28 msec
    154.54.6.190 [AS 174] 28 msec
  8 154.54.6.85 [AS 174] 40 msec
    154.54.24.81 [AS 174] 36 msec
    154.54.6.117 [AS 174] 40 msec
  9 154.54.26.113 [AS 174] 52 msec
    154.54.26.121 [AS 174] 52 msec
    154.54.26.129 [AS 174] 48 msec
10 154.54.25.70 [AS 174] 64 msec
    154.54.25.66 [AS 174] 60 msec
    154.54.25.70 [AS 174] 60 msec
11 154.54.2.197 [AS 174] 92 msec 88 msec 84 msec
12 154.54.0.249 [AS 174] 80 msec
    154.54.0.253 [AS 174] 80 msec
    154.54.0.249 [AS 174] 84 msec
13 154.54.41.142 [AS 174] 152 msec 224 msec 92 msec
14 38.122.90.42 [AS 174] 84 msec 84 msec
    38.104.124.82 [AS 174] 80 msec
15 63.251.160.18 [AS 14744] 76 msec 76 msec 72 msec
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

2

Just to clarify, it's not just a traceroute issue. I can't ping nor connect to port 80/443 to the ip address 72.5.52.199 from our network, although I can do both from an external shell account. It's very possible that it's a routing issue on the other side, and I'm reaching out to them as well.

3

We haven't seen Cogent-related issues at SEF today and that IP address is currently pingable through the Cogent looking glass. From your trace, Internap's equipment is reachable and responding (the two last hops are Internap-controlled), so the actual endpoint network (beyond Internap) seems to be either explicitly filtering your source or sending traffic back to it over a different and broken path.

The Internap NOC is responsive when it comes to investigating routing problems, so they're a good place to turn for such concerns. If you're having problems reaching them or would like some external help in exploring the problem from inside and outside that PNAP, shoot me an email off-list.

-John