|
Ticket ID: SIXXS #968275 Ticket Status: Invalid PoP: nlams05 - SURFnet (Amsterdam)
Delays in routing to/from 80.0.0.0/11
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Friday, 06 February 2009 20:28:14
There seems to be a >110 ms change in latancy for ipv4 traffic from/to sixxs.surfnet.nl that is passed from GlobalCrossing to OpenTransit at Frankfurt to/from 80.0.0.0/11
The problem seems to be assosiated with this links:
64.208.110.225 - 64.208.110.226 and
64.208.110.229 - 64.208.110.230
IPv4 traceroute from nlams05.sixxs.net @ SURFnet, AS1103 to router.bema.one.pl :
Hop Node Loss% Sent Last Avg Best Worst StDev
sixxs.surfnet.nl Snt: 5 Loss% Last Avg Best Wrst StDev
192.87.102.97 0.0% 0.2 0.3 0.2 0.3 0.1
145.145.18.93 0.0% 0.2 0.2 0.2 0.3 0.0
145.145.80.77 0.0% 0.3 0.3 0.3 0.3 0.0
64.209.105.157 0.0% 0.7 0.5 0.5 0.7 0.1
64.208.110.226 0.0% 133.7 133.9 131.3 136.6 1.9
??? 100.0 0.0 0.0 0.0 0.0 0.0
193.251.129.209 20.0% 138.6 137.1 135.0 138.8 1.9
??? 100.0 0.0 0.0 0.0 0.0 0.0
213.25.12.190 0.0% 168.5 167.5 164.8 169.7 2.1
83.16.194.41 20.0% 174.7 175.1 173.2 178.9 2.6
# traceroute sixxs.surfnet.nl
traceroute to sixxs.surfnet.nl (192.87.102.107), 30 hops max, 40 byte packets
1 router.bema.one.pl (83.16.194.41) 0.758 ms 0.635 ms 1.057 ms
2 gda-ru2.idsl.tpnet.pl (213.25.2.59) 7.926 ms 6.665 ms 6.389 ms
3 z.gda-ru2.do.gda-r2.tpnet.pl (213.25.5.189) 7.036 ms 7.809 ms 7.349 ms
4 194.204.175.89 (194.204.175.89) 12.428 ms 12.697 ms 11.835 ms
5 pos0-5-1-0.ffttr1.FrankfurtAmMain.opentransit.net (193.251.250.109) 35.077 ms pos0-6-0-0.ffttr1.FrankfurtAmMain.opentransit.net (193.251.250.113) 35.700 ms 35.247 ms
6 64.208.110.229 (64.208.110.229) 35.576 ms 38.021 ms 35.986 ms
7 64.209.105.158 (64.209.105.158) 166.342 ms 164.027 ms 164.426 ms
8 AE2.500.JNR01.Asd001A.surf.net (145.145.80.78) 171.509 ms 159.127 ms 158.436 ms
9 V1105.sw14.amsterdam1.surf.net (145.145.18.94) 164.165 ms 167.926 ms 162.629 ms
10 sixxs.surfnet.nl (192.87.102.107) 158.589 ms 158.645 ms 178.003 ms
Delays in routing to/from 80.0.0.0/11
What are we supposed to do with this problem?
Delays in routing to/from 80.0.0.0/11
Shadow Hawkins on Saturday, 07 February 2009 14:23:14
The hops that are introducing the delay belong to GBLX.
GBLX is the upstream provider for SURFnet.
I was expecting that SURNnet creates a troubleticket with GBLX to have that checked.
Delays in routing to/from 80.0.0.0/11
Contact your own ISP and let them contact GBLX. SixXS is not an ISP complaint desk.
You are not connected to nlams05, thus there is no relation to you to nlams05 either.
State change: user
The state of this ticket has been changed to user
State change: invalid
The state of this ticket has been changed to invalid
|
![[ch]](/s/countries/ch.gif)
on Saturday, 07 February 2009 13:19:16
Posting is only allowed when you are