Anyone from Global Crossing network engineering on-list? We're experiencing a connectivity issue from 63.228.227.0/24 to 64.233.187.99 that appears to be originating in Global Crossing's network. Other prefixes we announce from our AS (13941) such as 207.109.251.0/24 aren't having the problem. Tried the NOC email and phone number and was told that I can't open a case since we're not a direct customer. Unfortunately, I also can't reach the company today who we interconnect with that does peer with GLBX. To everyone else, sorry about the spam. -K grps-edge-rtr-1#ping ip 64.233.187.99 source 63.228.227.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 64.233.187.99, timeout is 2 seconds: Packet sent with a source address of 63.228.227.1 ..... Success rate is 0 percent (0/5) grps-edge-rtr-1#ping ip 64.233.187.99 source 207.109.251.253 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 64.233.187.99, timeout is 2 seconds: Packet sent with a source address of 207.109.251.253 !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/85/88 ms grps-edge-rtr-1#trace ip 64.233.187.99 source 63.228.227.1 Type escape sequence to abort. Tracing the route to google.com (64.233.187.99) 1 fa-6-0.grps-edge-rtr-2.visp.net (208.74.128.9) 0 msec 4 msec 0 msec 2 c1-mdfd-s40-visp.mind.net (69.9.134.65) [AS 6296] 4 msec 0 msec 4 msec 3 so-2-1-0.ar2.SEA1.gblx.net (64.212.109.181) [AS 3549] 12 msec 16 msec 12 msec 4 ge9-2-1000M.ar5.SEA1.gblx.net (67.17.109.250) [AS 3549] 12 msec 16 msec 12 msec 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 216.239.49.222 [AS 15169] 92 msec * * 11 * * * 12 google.com (64.233.187.99) [AS 15169] 84 msec 84 msec * grps-edge-rtr-1#trace ip 64.233.187.99 source 207.109.251.253 Type escape sequence to abort. Tracing the route to jc-in-f99.google.com (64.233.187.99) 1 fa-6-0.grps-edge-rtr-2.visp.net (208.74.128.9) 0 msec 0 msec 0 msec 2 c1-mdfd-s40-visp.mind.net (69.9.134.65) [AS 6296] 0 msec 0 msec 0 msec 3 so-2-1-0.ar2.SEA1.gblx.net (64.212.109.181) [AS 3549] 16 msec 8 msec 8 msec 4 ge9-2-1000M.ar5.SEA1.gblx.net (67.17.109.250) [AS 3549] 12 msec 8 msec 8 msec 5 74.125.49.1 [AS 15169] 44 msec 20 msec 20 msec 6 209.85.255.63 [AS 15169] 20 msec 24 msec 20 msec 7 66.249.95.210 [AS 15169] 12 msec 12 msec 12 msec 8 209.85.242.255 [AS 15169] 84 msec 84 msec 108 msec 9 72.14.239.21 [AS 15169] 84 msec 84 msec 72.14.236.15 [AS 15169] 88 msec 10 216.239.43.249 [AS 15169] 96 msec 216.239.43.189 [AS 15169] 88 msec 216.239.43.249 [AS 15169] 88 msec 11 jc-in-f99.google.com (64.233.187.99) [AS 15169] 84 msec 92 msec 84 msec -- Kameron Gasso | Senior Systems Administrator | visp.net Direct: 541-955-6903 | Fax: 541-471-0821
Kameron Gasso wrote:
Anyone from Global Crossing network engineering on-list?
We're experiencing a connectivity issue from 63.228.227.0/24 to 64.233.187.99 that appears to be originating in Global Crossing's network. Other prefixes we announce from our AS (13941) such as 207.109.251.0/24 aren't having the problem.
Thanks to everyone who replied off-list (including the GBLX engineer who fixed it). -K -- Kameron Gasso | Senior Systems Administrator | visp.net Direct: 541-955-6903 | Fax: 541-471-0821
participants (1)
-
Kameron Gasso