Opened 7 years ago

Closed 7 years ago

Last modified 5 weeks ago

#368 closed request (fixed)

Missing / broken routes?

Reported by: Ray.Bellis@… Owned by: jim@…
Priority: tbd Milestone: ietf-080
Component: network Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

FYI - I'm seeing broken connectivity to some destinations:

% traceroute www.bellis.me.uk.
traceroute to d1.s2.web.ci-net.com (195.72.163.66), 64 hops max, 52 byte packets
1  130.129.96.2 (130.129.96.2)  1.187 ms  9.182 ms  1.906 ms
2  82.113.59.4 (82.113.59.4)  2.324 ms  1.069 ms  2.025 ms
3  * *^C

% telnet www.me.com 80
Trying 88.221.181.47...
^C

% traceroute www.me.com
traceroute www.me.com
traceroute to e1235.b.akamaiedge.net (88.221.181.47), 64 hops max, 52 byte packets
1  130.129.96.2 (130.129.96.2)  1.259 ms  0.632 ms  1.247 ms
2  * *^C

If I VPN via my Amazon EC2 instance I can reach both of these.

kind regards,

Ray Bellis



Change history (13)

comment:1 Changed 7 years ago by llynch@…

Owner: changed from llynch@… to msackett@…
Status: newassigned

comment:2 Changed 7 years ago by llynch@…

Component: incomingnetwork

comment:3 Changed 7 years ago by msackett@…

Another user reports some more. He is trying from both vlans 32 and 96.

Steve Conte (steve@…)
can't get to isoc.org
no http://thestringdusters.com/
can get to google fine (v4)
no www.ustti.org
facebook is fine
it's really hit and miss

comment:4 Changed 7 years ago by ray.bellis@…

I've lost connectivity into RIPE's web sites, too.

% traceroute labs.ripe.net.
traceroute to labs.ripe.net (193.0.6.153), 64 hops max, 52 byte packets
1 130.129.96.2 (130.129.96.2) 1.736 ms 0.912 ms 0.548 ms
2 82.113.59.4 (82.113.59.4) 1.356 ms 0.804 ms 1.225 ms
C

This happened about 20 minutes ago for 5 minutes, was then OK, but is broken again right now.

Ray

comment:5 Changed 7 years ago by jim@…

Owner: changed from msackett@… to jim@…
Status: assignedaccepted

Everything seems to be working now ... we're guessing that one of our upstreams was doing maintenance this morning. We'll check with them, and keep this ticket open for now. Please let us know if you have any continuing problems.

  • Jim

comment:6 Changed 7 years ago by Ray Bellis

From where I am here on the ietf-a.1x network I'm still seeing the exact same results.

comment:7 Changed 7 years ago by Ray Bellis

that is, RIPE is OK now, but the originally reported routes are still down. I also can't reach (some?) other Akamai hosted sites, e.g. www.apple.com. Nor can I reach the other sites reported by Steve Conte.

comment:8 Changed 7 years ago by anonymous

Ray,

I'm on the ietf-a.1x net as well and am reaching all of the sites you mentioned. Including isoc.org from steve.

Jim@Beorn:/Users/jim/Downloads>ifconfig en1
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 00:25:00:4b:ab:29
inet6 fe80::225:ff:fe4b:ab29%en1 prefixlen 64 scopeid 0x5
inet6 2001:df8::96:225:ff:fe4b:ab29 prefixlen 64 autoconf
inet 130.129.100.243 netmask 0xfffff800 broadcast 130.129.103.255
media: autoselect
status: active

Jim@Beorn:/Users/jim/Downloads>traceroute www.bellis.me.uk.
traceroute to d1.s2.web.ci-net.com (195.72.163.66), 64 hops max, 52 byte packets

1 130.129.96.2 (130.129.96.2) 1.530 ms 0.974 ms 1.259 ms
2 82.113.59.4 (82.113.59.4) 1.287 ms 1.106 ms 1.157 ms
3 cz-prg-asbr1-be4.dialtelecom.cz (82.119.246.29) 1.835 ms 2.506 ms 1.803 ms
4 asbr9-po1.dialtelecom.cz (82.119.245.66) 1.771 ms 1.628 ms 1.708 ms
5 linx-gw1.as8844.net (195.66.224.236) 29.649 ms 30.105 ms 30.027 ms
6 gi5-2.r1.the.core.as8844.net (195.72.174.149) 31.518 ms 31.334 ms 31.508 ms
7 gi0-47.r2.mk2.core.as8844.net (195.72.174.222) 31.787 ms 32.140 ms 32.025 ms
8 ipv4-95-152-224-1.static.as8844.net (95.152.224.1) 31.937 ms 31.942 ms 31.884 ms
9 d1.s2.web.ci-net.com (195.72.163.66) 31.589 ms 31.624 ms 31.481 ms

Jim@Beorn:/Users/jim/Downloads>telnet www.me.com 80
Trying 96.6.213.47...
Connected to e1235.b.akamaiedge.net.
Escape character is ']'.
]
telnet> q
Connection closed.

Jim@Beorn:/Users/jim/Downloads>ping www.isoc.org
PING www.isoc.org (212.110.167.157): 56 data bytes
64 bytes from 212.110.167.157: icmp_seq=0 ttl=55 time=37.669 ms
64 bytes from 212.110.167.157: icmp_seq=1 ttl=55 time=37.352 ms
64 bytes from 212.110.167.157: icmp_seq=2 ttl=55 time=37.699 ms
64 bytes from 212.110.167.157: icmp_seq=3 ttl=55 time=148.652 ms
C
--- www.isoc.org ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 37.352/65.343/148.652/48.099 ms

When you have a minute, could you swing by the NOC (in Chez Luis) to figure out the differences in our behaviour?

Thanks!

  • Jim

comment:9 Changed 7 years ago by Ray Bellis

Sure, will come around in about 20 minutes or so.

comment:10 Changed 7 years ago by Ray Bellis <ray@…>

Sorry, I got distracted in the hallway. All seems OK now, though! Thanks.

comment:11 Changed 7 years ago by jim@…

Great ... let us know if you have any further (network) issues.

  • Jim

comment:12 Changed 7 years ago by jim@…

Resolution: fixed
Status: acceptedclosed

Closing the ticket for now, but if you find additional issues, please let us know.

  • Jim

comment:13 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-80ietf-080

Milestone renamed

Note: See TracTickets for help on using tickets.