Status · Ashburn

Current state

Two distinct things live here: what is working right now, and what has failed before. The second list is the useful one when you are deciding whether to trust a provider.

OperationalAll systems operational
  • Ashburn game nodes Operational
  • Voice relay Operational
  • Backup storage Operational
  • Control panel Operational
  • Uplink and DDoS filtering Operational

Incident history

Every interruption longer than five minutes, including the ones we caused ourselves. Durations are measured from the first failed check to full recovery.

  1. January 19, 2026

    Backups delayed by four hours

    The backup worker on Ashburn queued more jobs than it could run after a world directory grew past the size estimate. Backups finished late but completed; no data was lost.

    Duration: 4 h 12 min

  2. November 2, 2025

    Packet loss on the Ashburn uplink

    A faulty optics module on one transit link caused 3–8% packet loss for game traffic. Sessions stayed connected but tick times spiked. The module was replaced and the link rebalanced.

    Duration: 41 min

  3. June 27, 2025

    Panel unavailable after certificate renewal

    An automated certificate renewal wrote a chain the panel process did not reload. Logins failed until the service was restarted. Game servers were not affected.

    Duration: 18 min

  4. September 8, 2024

    Scheduled kernel upgrade caused two restarts

    The maintenance window ran longer than planned and two game instances restarted twice instead of once. Worlds were saved before each restart.

    Duration: 55 min

  5. October 14, 2023

    Voice relay dropped connections during peak

    A relay process reached its file descriptor limit at Saturday peak. Connections dropped and reconnected within about a minute after the limit was raised and made persistent.

    Duration: 26 min

Reporting something

If a server is unreachable and this page says everything is fine, the check is wrong or the problem is not on the node. Write to support@amber.cfngg.net with the instance name and the time; the on-call engineer sees it during 08:00–22:00 ET.

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.

Request access