Node 3 has been quiet for more than two hours: no further attacks, normal load, and connections and voice chat work directly. The protection measures stay in place. This incident is resolved.

Our network provider has adjusted its filter and UDP reaches Node 3 directly again. Voice chat has been running without the detour since 11:58 CET; the affected server was restarted once briefly for this. Players are connecting normally again. We will keep monitoring for a while.

Further attack waves hit Node 3 overnight and this morning (most recently around 23:06 and today at 10:37 CET). They targeted the web server port and a port with no customer server behind it. Both are fully filtered and game servers are running normally. Establishing new connections may occasionally take a little longer. Voice chat continues to run via the detour until our network provider adjusts its filter.

More attack waves hit Node 3 in the evening (most recently around 21:00 CET). They were caught completely and the game servers ran without restrictions. A single port that was flooded at 17:31 CET was blocked until 21:04 CET and has been released again. New connections to Node 3 work reliably again. Voice chat keeps running over the alternate path until our network provider adjusts its filter.

Another wave of the attack hit Node 3 at 16:56 CET, for about two minutes. Our filters caught it completely: the game servers kept running without delay and without disconnects. We keep monitoring.

Node 3 was attacked in several waves today, most recently at 16:20 CET. It has been quiet since 16:22 CET. The attacks no longer reach the game servers: we tightened the filters on all nodes, and a port that gets flooded is now blocked automatically until our team releases it.

The game servers are running. Our network provider's protection still slows down new connections to Node 3: joining can take up to a second, and occasionally works only on the second try. Voice chat keeps running over an alternate path. We are clarifying this with the network provider and keep monitoring.

The attack on Node 3 continues. We have added further filters and the server itself is stable. New connections to game servers on Node 3 may be delayed by our network provider's protection (higher ping, occasional disconnects). Voice chat runs over an alternate path.

Voice chat works again over the alternate path and voice connections are up. We are monitoring and clarifying the filter with the network provider.

Node 3 was flooded with connection requests. Since then the upstream network filters UDP to this machine. The attacking addresses are blocked, and we are rerouting voice chat for affected servers over a second path.

UDP connections (e.g. voice chat mods) from outside do not reach Node 3. Game servers are running and players can join normally. We are looking into it.