Ticket ID: SIXXS #1002944 Ticket Status: User PoP: nlede01 - BIT BV (Ede)
nlede01 down (untraceroutable etc)
Shadow Hawkins on Wednesday, 18 March 2009 04:17:10
I have not gotten replies when trying to 193.109.122.244 from three different hosts. One is XS4All, one is at GN-IX and one is in Rotterdam. I get no ping replies either. The output of traceroute:
% traceroute 193.109.122.244
traceroute to 193.109.122.244 (193.109.122.244), 30 hops max, 40 byte packets
1 csw-1.cpl-mkb.grafix.nl (217.67.238.1) 1.487 ms 2.304 ms 2.875 ms
2 * * *
3 * * *
4 * * *
5 * * *
traceroute to 193.109.122.244 (193.109.122.244), 30 hops max, 52 byte packets
1 89.188.20.253 (89.188.20.253) 0.302 ms 0.283 ms 0.272 ms
traceroute to 193.109.122.244 (193.109.122.244), 30 hops max, 40 byte packets
1 124.ae0.xr4.1d12.xs4all.net (194.109.21.1) 0.795 ms !N 0.790 ms !N 0.779 ms !N
nlede01 down (untraceroutable etc)
Shadow Hawkins on Wednesday, 18 March 2009 09:20:43
Having the same problem here from KPN (AS8737) though the box is still reachable from my colo box in AS25525.
nlede01 down (untraceroutable etc)
Shadow Hawkins on Wednesday, 18 March 2009 09:21:20
Actually never mind, the second I posted that it sprung to life again.
State change: user
Jeroen Massar on Wednesday, 18 March 2009 11:12:37
The state of this ticket has been changed to user
nlede01 down (untraceroutable etc)
Jeroen Massar on Wednesday, 18 March 2009 11:14:51
Looks to me there is an internal routing issue with the above as it doesn't even hit a single route from BIT and stays inside the network where your host resides.
Did you check the traceroute tool at the time when this was happening?
nlede01 down (untraceroutable etc)
Shadow Hawkins on Wednesday, 18 March 2009 11:47:24
I have no idea then, it seems to be working alright now from all of the same hosts. Seems like it came back to life indeed :)
Posting is only allowed when you are logged in. |