Opened 10 years ago

Closed 10 years ago

#101 closed request (fixed)

Slow connections/long pingtimes to many off-site webservers

Reported by: yngve@… Owned by: nweis@…
Priority: major Milestone:
Component: network Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description (last modified by randy@…)

an issue with an upstream router config has been worked. are you still seeing a problem?

Change history (5)

comment:1 Changed 10 years ago by anonymous

dhcp-17e8.meeting.ietf.org:/Users/randy> traceroute !$
traceroute www.vg.no
traceroute to www.vg.no (193.69.165.21), 64 hops max, 40 byte packets

1 rtra (130.129.1.2) 4.475 ms 1.003 ms 1.162 ms
2 66.114.246.1 (66.114.246.1) 19.091 ms 19.201 ms 9.144 ms
3 t3-3-1-0-3.edge7.SanJose1.Level3.net (4.53.20.13) 3.881 ms 4.018 ms 2.956 ms
4 ae-15-15.car1.SanJose1.Level3.net (4.68.106.249) 3.677 ms 3.547 ms ae-25-25.car2.SanJose1.Level3.net (4.68.106.253) 3.602 ms
5 vlan99.csw4.SanJose1.Level3.net (4.68.18.254) 4.330 ms 3.152 ms 3.899 ms
6 ae-84-84.ebr4.SanJose1.Level3.net (4.69.134.249) 19.820 ms ae-94-94.ebr4.SanJose1.Level3.net (4.69.134.253) 12.973 ms ae-84-84.ebr4.SanJose1.Level3.net (4.69.134.249) 9.913 ms
7 ae-2.ebr4.NewYork1.Level3.net (4.69.135.186) 76.751 ms 79.392 ms 73.173 ms
8 ae-84-84.csw3.NewYork1.Level3.net (4.69.134.122) 78.368 ms 75.361 ms 82.603 ms
9 ae-93-93.ebr3.NewYork1.Level3.net (4.69.134.109) 80.006 ms 72.110 ms 74.636 ms

10 ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 77.832 ms 78.862 ms 78.070 ms
11 ae-42-42.ebr2.Frankfurt1.Level3.net (4.69.137.53) 170.248 ms 167.664 ms 168.067 ms
12 ae-2-2.ebr1.Dusseldorf1.Level3.net (4.69.132.137) 171.950 ms 171.779 ms 170.783 ms
13 ae-6-6.car1.Copenhagen1.Level3.net (4.69.134.29) 183.603 ms 183.624 ms 184.163 ms
14 ae-11-11.car2.Copenhagen1.Level3.net (4.69.134.26) 185.844 ms 183.740 ms 183.866 ms
15 213.242.108.18 (213.242.108.18) 202.677 ms 192.841 ms 193.954 ms
16 c10G-ge-7-1-0.cr1.osls.no.catchbone.net (81.0.128.245) 193.754 ms 190.833 ms 190.467 ms
17 v4092.rs2.m323.no.catchbone.net (193.75.1.142) 191.416 ms 190.194 ms 191.761 ms
18 193.69.165.11 (193.69.165.11) 195.404 ms 192.892 ms 283.809 ms
19 193.69.165.11 (193.69.165.11) 193.699 ms 191.876 ms 192.251 ms

comment:2 Changed 10 years ago by yngve@…

Things seem to have improved somewhat.

I have been able to use Remote Desktop without too many problems, although there were occasional slow spots.

For traceroute, I have noticed occasional timeouts, as well as a couple of long pingtimes, as in the example below.

All those seem, however, to be closer to the US east coast, than the west coast.

I'll continue to monitor the situation.

C:\Documents and Settings\Administrator>tracert www.vg.no

Tracing route to www.vg.no [193.69.165.21] over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 130.129.16.2
2 5 ms 6 ms 7 ms 66.114.246.1
3 14 ms 11 ms 10 ms t3-3-1-0-3.edge7.SanJose1.Level3.net [4.53.20.13]
4 136 ms 11 ms 3 ms ae-15-15.car1.SanJose1.Level3.net [4.68.106.249]
5 10 ms 3 ms 21 ms vlan79.csw2.SanJose1.Level3.net [4.68.18.126]
6 17 ms 26 ms 13 ms ae-74-74.ebr4.SanJose1.Level3.net [4.69.134.245]
7 79 ms 85 ms 89 ms ae-2.ebr4.NewYork1.Level3.net [4.69.135.186]
8 90 ms 95 ms 91 ms ae-94-94.csw4.NewYork1.Level3.net [4.69.134.126]
9 81 ms 87 ms 73 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]

10 81 ms 88 ms 88 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]
11 88 ms 77 ms 88 ms ae-84-84.csw3.Washington1.Level3.net [4.69.134.186]
12 78 ms 85 ms 78 ms ae-82-82.ebr2.Washington1.Level3.net [4.69.134.153]
13 183 ms 505 ms 168 ms ae-42-42.ebr2.Frankfurt1.Level3.net [4.69.137.53]
14 517 ms 182 ms 175 ms ae-2-2.ebr1.Dusseldorf1.Level3.net [4.69.132.137]
15 185 ms 488 ms 184 ms ae-6-6.car1.Copenhagen1.Level3.net [4.69.134.29]
16 182 ms 553 ms 184 ms ae-11-11.car2.Copenhagen1.Level3.net [4.69.134.26]
17 194 ms 191 ms 569 ms 213.242.108.18
18 549 ms 194 ms 208 ms c10G-ge-7-1-0.cr1.osls.no.catchbone.net [81.0.128.245]
19 192 ms 194 ms 489 ms v4092.rs2.m323.no.catchbone.net [193.75.1.142]
20 196 ms 195 ms 256 ms 193.69.165.11
21 202 ms 207 ms 528 ms 193.69.165.21

Trace complete.

C:\Documents and Settings\Administrator>tracert www.vg.no

Tracing route to www.vg.no [193.69.165.21] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 130.129.16.2
2 8 ms 2 ms 2 ms 66.114.246.1
3 3 ms 3 ms 10 ms t3-3-1-0-3.edge7.SanJose1.Level3.net [4.53.20.13]
4 5 ms 2 ms 4 ms ae-15-15.car1.SanJose1.Level3.net [4.68.106.249]
5 17 ms 19 ms 30 ms vlan79.csw2.SanJose1.Level3.net [4.68.18.126]
6 14 ms 21 ms 13 ms ae-74-74.ebr4.SanJose1.Level3.net [4.69.134.245]
7 74 ms 73 ms 85 ms ae-2.ebr4.NewYork1.Level3.net [4.69.135.186]
8 89 ms 76 ms 82 ms ae-94-94.csw4.NewYork1.Level3.net [4.69.134.126]
9 * 79 ms 89 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]

10 * 83 ms 90 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]
11 * 85 ms 79 ms ae-84-84.csw3.Washington1.Level3.net [4.69.134.186]
12 80 ms 78 ms 80 ms ae-82-82.ebr2.Washington1.Level3.net [4.69.134.153]
13 169 ms 535 ms 171 ms ae-42-42.ebr2.Frankfurt1.Level3.net [4.69.137.53]
14 177 ms 173 ms 190 ms ae-2-2.ebr1.Dusseldorf1.Level3.net [4.69.132.137]
15 188 ms 392 ms 187 ms ae-6-6.car1.Copenhagen1.Level3.net [4.69.134.29]
16 189 ms 546 ms 188 ms ae-11-11.car2.Copenhagen1.Level3.net [4.69.134.26]
17 230 ms 194 ms 545 ms 213.242.108.18
18 408 ms 207 ms 557 ms c10G-ge-7-1-0.cr1.osls.no.catchbone.net [81.0.128.245]
19 195 ms 191 ms 195 ms v4092.rs2.m323.no.catchbone.net [193.75.1.142]
20 564 ms 200 ms 200 ms 193.69.165.11
21 533 ms 303 ms 571 ms 193.69.165.21

Trace complete.

comment:3 Changed 10 years ago by randy@…

Description: modified (diff)
Priority: tbdmajor

comment:4 Changed 10 years ago by anonymous

After a quick check from hotel room it looks to work reasonably well now. No timeouts.

Tracerout did report a couple of high ping times for this step

3 368 ms 53 ms 45 ms ae-25-25.car2.SanJose1.Level3.net [4.68.106.253]

Not sure what that is.

Will check the conference area network later.

comment:5 Changed 10 years ago by msackett@…

Resolution: fixed
Status: newclosed

This was an issue of one of our upstream routers not being properly configured (see NOC report for IETF 74). This was resolved Tuesday evening.

Note: See TracTickets for help on using tickets.