Ticket ID: SIXXS #10975630 Ticket Status: Resolved PoP: gblon03 - Gyron Internet LTD - Limited UK Company (London)
gblon03 unrechable again
![]()
gblon03 seems to back in the same state as ticket #10964330, as of around 10:00 GMT.
I can't reach it via 89.145.125.38 , which is the route every connection I have access to wants to take.
gblon03 unavailable
![]()
gblon03 has been unavailable since midnight today (20140129T0000Z). This is confirmed by the traffic charts at https://www.sixxs.net/misc/traffic/?pop=gblon03&last=1week.
gblon03 unavailable
![]()
Not totally true Chris.
It is available if you get routed via
ae3.core-2.maylands.hml.uk.as29017.net (89.145.125.34)
but if you are routed via
ae3.core-1.maylands.hml.uk.as29017.net (89.145.125.38) then it times out.
So the POP itself is up. It's just not reachable via certain routes.
See :- https://www.sixxs.net/forum/?msg=general-10964246 for actual traceroutes.
Also the graph you quoted does show the problem. But if you zoom in
https://www.sixxs.net/misc/traffic/?pop=gblon03&last=1week.
then you can see the outage last night and it coming back opnline but with much much less traffic than before.
gblon03 unavailable
![]()
Which is practically most users since it is showing next to no traffic.
gblon03 unavailable
![]()
Yes. Also true.
I emailed gyron to see if they would check it out and/or recommend who to contact to try and get the problem fixed. But they closed the issue without investigating as I wasn't a customer.
Just have to be patient and wait until it gets fixed.
gblon03 unavailable
![]()
I have heard a report that it seems to be back up now. Indeed I am able to ping the tserv again as usual.
64 bytes from gblon03.sixxs.net (212.113.147.150): icmp_seq=1 ttl=56 time=5.03 ms
4: xe-0-0-3.border-1.sov.lon.uk.as29017.net (195.66.224.141) 5.168ms asymm 9
5: ae3.core-1.maylands.hml.uk.as29017.net (89.145.125.38) 5.113ms asymm 8
6: ae0.core-2.maylands.hml.uk.as29017.net (89.145.125.74) 4.854ms asymm 7
7: ae3.core-2.centro.hml.uk.as29017.net (89.145.125.70) 5.539ms asymm 8
8: gblon03.sixxs.net (212.113.147.150) 5.116ms reached
4 xe-0-0-1.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::1a) 13.259 ms 13.202 ms xe-1-2-2.core-2.centro.hml.uk.as29017.net (2a00:14f0:0:1::a) 18.031 ms
5 ae3.core-1.centro.hml.uk.as29017.net (2a00:14f0:0:1::2e) 14.379 ms xe-1-2-2.core-2.centro.hml.uk.as29017.net (2a00:14f0:0:1::a) 17.863 ms ae3.core-1.centro.hml.uk.as29017.net (2a00:14f0:0:1::2e) 14.356 ms
6 ae0.core-2.centro.hml.uk.as29017.net (2a00:14f0:0:1::2) 14.260 ms ae3.core-1.centro.hml.uk.as29017.net (2a00:14f0:0:1::2e) 5.537 ms ae0.core-2.centro.hml.uk.as29017.net (2a00:14f0:0:1::2) 5.945 ms
7 gblon03.sixxs.net (2a00:14f0:1:2::5) 5.825 ms 5.819 ms 5.810 ms
gblon03 unavailable
![]()
Yes, confirmed..status quo returned here too.
gblon03 unrechable again
![]()
Reachable again now, at least for me (apparently via ae3.core-1.maylands.hml.uk.as29017.net).
http://pyro.eu.org/f/zUUz8IQyRuqr-hltBCOm4A.gblon03.png
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 62.3.87.147 0.0% 100 15.2 11.4 10.6 15.5 1.0
2. 62.3.87.165 0.0% 100 11.6 15.0 10.3 81.6 11.3
3. 62.3.80.45 0.0% 100 18.2 23.0 17.4 47.3 6.1
4. 195.66.224.141 0.0% 100 18.9 21.8 18.3 69.6 8.3
5. 89.145.125.38 0.0% 100 18.8 20.9 18.5 71.4 6.9
6. 89.145.125.74 0.0% 100 18.7 20.6 18.3 73.4 6.6
7. 89.145.125.70 0.0% 100 19.3 21.4 18.5 65.1 8.3
8. 212.113.147.150 0.0% 100 18.9 19.2 18.5 22.7 0.7
gblon03 unrechable again
![]()
Yes - back for me too, via 89.145.125.38
|