Blog
Notes from the node
What changed, what broke, and why a decision was made the way it was. No announcements about office birthdays.
-
Hardware refresh on the Tallinn node
We replaced the storage layer on Tallinn over one night in a maintenance window. No world data moved between hosts, and no server was offline for longer than four minutes.
-
Voice relay update for Tallinn
Opus stereo is now on by default for voice servers on the Tallinn node. Mono remains available if your group prefers it.
-
How we size a Minecraft world backup
Why a 3 GB world can produce a 40 GB backup window, and the three settings that keep backups from eating the disk.
-
What the Tallinn node moved last quarter
A short, unglamorous report on traffic, peak hours and why the node is not packed to the ceiling.
-
Palworld, three months later — what actually eats memory
Player count matters less than explored map area. Numbers from servers on our nodes, and why we set the minimum plan where we did.
-
Postmortem: 41 minutes of packet loss on the Frankfurt uplink
A faulty optics module, a bad monitoring threshold, and what changed afterwards.
-
Traffic limits, explained without the marketing
What counts, what does not, what happens at the limit, and why "unmetered" usually means "we will find a reason later".
-
Backups are not a checkbox
Why we stop the server to take a backup, and the three ways a "backup" turns out to be useless when someone actually needs it.
-
Why we cap the number of instances per host
The arithmetic behind a node that runs at 61% CPU instead of 95%, and why that number is the product rather than a missed target.
Tell us what you are running
Write a few lines about the game, the player count and the region you need. We answer within one business day with a concrete node and a date.