TS server down?

[Robawillis]

and again nope

[Sao]

Blame flummi, he broke it <3

But its still down as of 1026BST =]

[KoffeinFlummi]

Blame flummi, he broke it <3

But its still down as of 1026BST =]

Hey now, I wasn't the one breaking all the channels yesterday...

[Gardalop]

Still down as of 5:30 akst
EDIT: It is back up

[matsif]

was afk, everyone got DC'd, reconnected and DC'd enough times now to get flood prevention to kick in.

[matsif]

seems to have stabilized

[Fields]

Bump. The sky is falling.

[matsif]

indeed, been having lag and dropouts all week more or less.

[Kismet]

crash all the things!

[matsif]

has happened once already since I've been on there this morning

[Robawillis]

Just going to leave this here

Between approximately 9:45am EDT and 10:15am EDT on Saturday, September 7, we will be performing an emergency maintenance in NYC to update the software on our router. This update will make it more resilient to large-scale DDoS attacks. As a result of this maintenance, your service will be unreachable for approximately 3-10 minutes.

If this timeframe will not work for you, please contact us ASAP so that we can arrange for a temporary service at another location, or so that we can help you to move your service to another location temporarily.


Update @ 10:04am EDT: This maintenance was completed successfully, with two minutes of downtime.

Re: Continued DDoS attacks
Sep 06 2013 06:52:49 PM PT The attacker continues to hit seemingly random NYC servers. We're continuing to work to mitigate of each the attacks.
Re: Continued DDoS attacks
Sep 06 2013 02:19:00 PM PT The attacker who hit last night is continuing his attacks today, probably after he got home from school. We are attempting to null route IP addresses as they're hit, as there is not much else we can do.
Re: Packet loss due to DDoS at around 7:55pm EDT
Sep 05 2013 09:16:07 PM PT Another extremely large attack hit us (and Internap) in NYC at around 11:45pm EDT, causing packet loss for around three minutes. This attack was against a different host than the last one, as it continues to be null-routed.

The size of these attacks makes them very difficult to block, as even Internap's network is overwhelmed. We are working with them to try to determine how they can better handle them going forward, but there unfortunately is no quick fix if the attacker continues to target our network (at any location). We can null-route the target, but he can (and is) simply moving to a different one.

[Fields]

Thanks for the update, Rob. I suppose we'll have to watch the server over the next few weeks and see if things have persisted or improved.

[Kilo]

Hopefully this doesn't happen during the scrim

[InsanityRocks]

Hopefully this doesn't happen during the scrim

I was thinking the same

[Robawillis]

will bump this up so you can all see whats going on:


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Users\Rob>ping 66.150.121.103

Pinging 66.150.121.103 with 32 bytes of data:
Reply from 74.201.150.226: Destination host unreachable.
Reply from 74.201.150.226: Destination host unreachable.
Request timed out.
Reply from 74.201.150.226: Destination host unreachable.

Ping statistics for 66.150.121.103:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

C:\Users\Rob>tracert 66.150.121.103

Tracing route to v-66-150-121-103.unman-vds.internap-nyc.nfoservers.com [66.150.
121.103]
over a maximum of 30 hops:

1 4 ms 5 ms 3 ms BTHUB4 [192.168.1.254]
2 13 ms 17 ms 11 ms 172.16.10.132
3 * 11 ms 12 ms 217.41.216.54
4 12 ms 11 ms 15 ms 217.41.216.53
5 12 ms 11 ms 15 ms 217.32.147.202
6 13 ms 21 ms 12 ms 217.41.168.69
7 12 ms 12 ms 11 ms 217.41.168.107
8 13 ms 11 ms 13 ms acc1-10GigE-0-7-0-5.l-far.21cn-ipp.bt.net [109.1
59.249.86]
9 15 ms 19 ms 20 ms core2-te0-15-0-14.faraday.ukcore.bt.net [109.159
.249.17]
10 13 ms 12 ms 21 ms peer2-xe8-1-1.telehouse.ukcore.bt.net [109.159.2
55.103]
11 23 ms 13 ms 12 ms t2c3-xe-0-1-3-0.uk-lon1.eu.bt.net [166.49.211.16
8]
12 14 ms 14 ms 12 ms 166-49-211-38.eu.bt.net [166.49.211.38]
13 82 ms 81 ms 81 ms xe-0-0-1.nyc32.ip4.tinet.net [89.149.184.194]
14 82 ms 82 ms 82 ms internap-gw.ip4.tinet.net [216.221.159.218]
15 82 ms 81 ms 83 ms border2.pc1-bbnet1.ext1.nym.pnap.net [216.52.95.
15]
16 nuclearfallout-57.border2.ext1.nym.pnap.net [74.201.150.226] reports: Dest
ination host unreachable.

Trace complete.

Seems to me its either an attack or an internal routing error either way we can't control this as we don't have access to the server status via web control or RDP. Please be patient and I am sure the providers will fix the problem soon.