|
Ticket ID: SIXXS #835959 Ticket Status: User PoP: nlams05 - SURFnet (Amsterdam)
nlams05 pop down?
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 29 October 2008 10:16:33
Seems that the nlams05 pop is down (one way). When using the traceroute tools from the SixXS website, I don't get any results from nlams05 to another pop or IP address.
IPv6:
nlams05 to bebru01
IPv4:
nlams05 to bebru01
But, the weird thing is that I can get from the SixXS NOC to nlams05
IPv6:
SixXS NOC to nlams05
IPv4:
SixXS NOC to nlams05
nlams05 pop down?
Shadow Hawkins on Wednesday, 29 October 2008 10:22:08
Regarding the links, they show this:
IPv6 traceroute
IPv6 traceroute from nlams05.sixxs.net @ SURFnet, AS1103 to bebru01.sixxs.net :
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
IPv4 traceroute
IPv6 traceroute from nlams05.sixxs.net @ SURFnet, AS1103 to bebru01.sixxs.net :
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
IPv6 traceroute
IPv6 traceroute from noc.sixxs.net @ SixXS NOC, AS12871 to nlams05.sixxs.net :
Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation
1. 2001:838:1:1::1 0.0% 5 0.4 0.5 0.4 0.5 0.0 [.nl] Netherlands, The 12871 Concepts ICT
ge-1-3-0.breda.ipv6.concepts-ict.net.
2. 2001:838:0:10::1 20.0% 5 2.4 2.4 2.3 2.5 0.1 [.nl] Netherlands, The 12871 Concepts ICT
3. 2001:7f8:1::a500:1103:1 0.0% 5 2.8 6.2 2.7 19.7 7.5
XSR03.Asd001A.surf.net.
4. 2001:610:e08:76::78 0.0% 5 3.1 3.0 2.8 3.1 0.1 [.nl] Netherlands, The 1103 SURFnet
AE2.500.JNR01.Asd001A.surf.net.
5. 2001:610:f01:8092::94 0.0% 5 2.9 2.9 2.8 2.9 0.1 [.nl] Netherlands, The 1103 SURFnet
V1105.SW14.Amsterdam1.surf.net.
6. 2001:610:1:80bb:192:87:102:1 0.0% 5 3.1 2.9 2.7 3.1 0.1 [.nl] Netherlands, The 1103 SURFnet
IPv4 traceroute
IPv4 traceroute from noc.sixxs.net @ SixXS NOC, AS12871 to nlams05.sixxs.net :
Hop Node Loss% Sent Last Avg Best Worst StDev
1. 213.148.254.9 0.0% 5 0.4 0.4 0.3 0.4 0.0
2. 213.197.27.126 0.0% 5 2.4 2.4 2.3 2.5 0.1
at-0-3-1.ams.nikhef.concepts-ict.net.
3. 195.69.144.50 0.0% 5 3.8 6.7 3.7 18.3 6.5
XSR03.Asd001A.surf.net.
4. 145.145.80.78 0.0% 5 5.9 4.5 3.7 5.9 1.1
ae2.500.jnr01.asd001a.surf.net.
5. 145.145.18.94 0.0% 5 3.8 4.0 3.8 4.8 0.4
v1105.sw14.amsterdam1.surf.net.
6. 192.87.102.107 0.0% 5 5.5 4.2 3.8 5.5 0.7
sixxs.surfnet.nl.
State change: user
The state of this ticket has been changed to user
nlams05 pop down?
Why are you claiming the PoP is down when it is indicated that it is not, connectivity is working, and the only apparent thing is that some traceroute tool fails?
nlams05 pop down?
Shadow Hawkins on Wednesday, 29 October 2008 11:21:37
The reason that I posted this, is because I got a mail from the tunnelrobot, stating that my tunnel was down. I did not change anything on my side, and I started looking into this. And I found this out.
Maybe the subject was a bit off, connectivity issues would have been a better name.
But isn't it weird that you can ping to but not from the pop? Whereas others do work.
nlams05 pop down?
That is because the tool that does the traceroute was failing, not anything to do directly with the PoP.
nlams05 pop down?
Shadow Hawkins on Wednesday, 29 October 2008 11:42:24
OK, my apologies.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 29 October 2008 10:33:09
Posting is only allowed when you are