OFFICIAL DOWNTIME THREAD

[Inaotia]

ohes noes did we just crash?

[Llexa]

hmm, i didnt see a crash message i just got disconnected

[OldManAlewar]

ohes noes did we just crash?

[Phiore]

Awww I was just about to buy something from Llex when we crashed
Don't sell it I will make it back on

[Inaotia]

Meow?

[Memphesian2007]

Server down again. Something is up.

[Zodart]

Ahh....no, don't say it happened again? *paranoid*

[Inaotia]

I blame old Man Alewar.....

[OldManAlewar]

I blame old Man Alewar.....

pah

[+Colibri]

I blame global warming...


Ok 2 disconnects both of 10 minutes. The first one happened just as I was going to bed so the moment after you all disconnected, I shrunk all your pets and put them in your backpack.

The guy at the ISP support (probably someone who has a thing for Apple products and doesn't know much about real networking) said that this was already announced. They say there's no way to get updates from that website via email, but well in case it goes down again, here's the link to the page with downtime schedules:

http://www.t-2.net/?ctxID=001865&funcID=1

Basically, if you see "Ljubljana" in bold, then that's us. I just hope they won't be doing these maintenances every week or two... I'd hate to see the network to be so well maintained

[OldManAlewar]

i killed the shard again

also: t-2.net is down

[edit] t-2.net is back up
[edit] down again

Zaradi napake na sistemu za napajanje z električno energijo je bila centrala Ljubljana-Podgorica v izpadu od 14:00, dne 12.11. Dežurna ekipa je napako odpravila do 17:30. Uporabnikom se za nevšečnosti opravičujemo.

some very timeshifted schedueled downtime ?

[Adin]

Routenverfolgung zu shard.uoex.net [93.103.6.33] über maximal 30 Abschnitte:

1 203 ms 328 ms 172 ms 10.210.19.196
2 125 ms 156 ms 79 ms 139.7.127.6
3 109 ms 157 ms 172 ms dus-145-253-21-169.arcor-ip.net [145.253.21.16

4 172 ms 110 ms 93 ms dus-145-254-4-169.arcor-ip.net [145.254.4.169]
5 125 ms 125 ms 156 ms ffm-145-254-19-121.arcor-ip.net [145.254.19.12

6 94 ms 125 ms 125 ms ffm-145-254-16-74.arcor-ip.net [145.254.16.74]
7 125 ms 94 ms 78 ms TenGigabitEthernet4-3.ar1.FRA4.gblx.net [64.21.225.141]
8 125 ms 93 ms 78 ms te1-2-10G.ar2.FRA4.gblx.net [67.16.131.129]
9 140 ms 188 ms 375 ms ffm-b6-link.telia.net [213.248.103.41]
10 219 ms 203 ms 141 ms ffm-bb1-link.telia.net [80.91.251.150]
11 203 ms 203 ms 203 ms Win-b2-link.telia.net [80.91.248.77]
12 * 344 ms 2375 ms t2-ic-123816-win-b2.c.telia.net [213.248.104.1]
13 406 ms 203 ms 329 ms 84-255-250-25.core.t-2.net [84.255.250.25]
14 * * * Zeitüberschreitung der Anforderung.
15 297 ms 360 ms 328 ms 93-103-6-33.static.t-2.net [93.103.6.33]

Ablaufverfolgung beendet.

[OldManAlewar]

viele leute sprechen kein Deutch, anglisch bitte

[Devilman]

Couple of Tracert's here from the UK...

First one you can see that one of telia's routers is playing up aswell as T2..

1 <1 ms <1 ms <1 ms smoothwall [192.168.0.1]
2 30 ms 31 ms 31 ms 62.241.160.185
3 30 ms 31 ms 31 ms 62.241.167.133
4 29 ms 31 ms 31 ms po2-104.cr05.hx2.bb.gxn.net [62.72.139.25]
5 30 ms 31 ms 31 ms lon1-core.gigabiteth3-0.swip.net [195.66.226.87]
6 37 ms 39 ms 47 ms 130.244.192.17
7 54 ms 55 ms 55 ms wen3-core-1.pos8-0-0.swip.net [130.244.207.54]
8 54 ms 55 ms 55 ms wen1-core-1.pos0-0.swip.net [130.244.205.49]
9 * * 33 ms adm-bb2-link.telia.net [80.91.254.130]
10 37 ms 44 ms 39 ms hbg-bb2-link.telia.net [80.91.252.43]
11 67 ms 71 ms 71 ms win-b2-link.telia.net [80.91.248.125]
12 109 ms 79 ms 77 ms t2-ic-123816-win-b2.c.telia.net [213.248.104.158]
13 83 ms 87 ms 103 ms 84-255-250-25.core.t-2.net [84.255.250.25]
14 * * 97 ms 84-255-250-25.core.t-2.net [84.255.250.25]
15 * 108 ms 103 ms te2-4.cr05.tn5.bb.gxn.net [62.72.137.249]
16 78 ms 79 ms 79 ms 93-103-6-33.static.t-2.net [93.103.6.33]


However after a few mins I did another and telia seems to have re-routed around the "adm-bb2" router..

1 <1 ms <1 ms <1 ms smoothwall [192.168.0.1]
2 25 ms 31 ms 31 ms 62.241.160.185
3 29 ms 31 ms 31 ms 62.241.167.133
4 29 ms 39 ms 23 ms 158.43.31.29
5 29 ms 31 ms 31 ms so-1-1-1.XR1.LND9.ALTER.NET [158.43.150.157]
6 26 ms 31 ms 31 ms GigabitEthernet0-0-0.BR1.LND18.ALTER.NET [146.188.3.250]
7 30 ms 31 ms 32 ms ldn-b4-link.telia.net [213.248.104.45]
8 30 ms 31 ms 31 ms ldn-bb1-link.telia.net [80.91.249.77]
9 37 ms 39 ms 47 ms hbg-bb1-link.telia.net [80.239.147.182]
10 70 ms 71 ms 71 ms win-b2-link.telia.net [80.91.252.81]
11 71 ms 71 ms 79 ms t2-ic-123816-win-b2.c.telia.net [213.248.104.158]
12 78 ms 79 ms 79 ms 84-255-250-25.core.t-2.net [84.255.250.25]
13 * * * Request timed out.
14 76 ms 87 ms 87 ms 93-103-6-33.static.t-2.net [93.103.6.33]

Seems that while there may have been a "slight hiccup" with the connection between colibri's ISP and the backbone, there was also connection issues higher up at the peering level (Telia), which is not uncommon tbh... many times Telia has caused problems for the european World of Warcraft servers, for the same reason.

[Adin]

Code: Select all

Routenverfolgung zu shard.uoex.net [93.103.6.33]  über maximal 30 Abschnitte:

  1    78 ms   109 ms    94 ms  10.210.19.196
  2    94 ms   218 ms   219 ms  139.7.127.6
  3   203 ms   219 ms   218 ms  88.79.17.5
  4   219 ms   234 ms   235 ms  esn-145-254-12-61.arcor-ip.net [145.254.12.61]
  5   218 ms   219 ms   235 ms  dus-145-254-19-178.arcor-ip.net [145.254.19.178]

  6   265 ms   250 ms   282 ms  dus-145-254-18-154.arcor-ip.net [145.254.18.154]

  7   203 ms   234 ms   235 ms  62.67.32.165
  8   235 ms   250 ms   234 ms  ae-31-51.ebr1.Dusseldorf1.Level3.net [4.68.119.3
0]
  9   250 ms   250 ms   250 ms  ae-2.ebr2.Frankfurt1.Level3.net [4.69.132.138]
 10   234 ms   297 ms   234 ms  ae-2-56.edge3.Frankfurt1.Level3.net [4.68.118.17
8]
 11   218 ms   235 ms   234 ms  fra36-core-2.tengigabiteth3-3.swip.net [130.244.
200.85]
 12   234 ms   235 ms   250 ms  130.244.52.174
 13   265 ms   250 ms   250 ms  wen1-core-1.pos8-0-0.swip.net [130.244.207.50]
 14   250 ms   265 ms   266 ms  wen3-core-1.pos2-0.swip.net [130.244.205.50]
 15   250 ms   282 ms   265 ms  130.244.49.118
 16   281 ms   313 ms   250 ms  81.189.132.150
17     *        *        *     Zeitüberschreitung der Anforderung.
 18   265 ms   422 ms   406 ms  93-103-6-33.static.t-2.net [93.103.6.33]

Ablaufverfolgung beendet.

One of the routers is still very dead. And i remain lagging -.-