FlexyNode - Notice history

All systems operational

Notice history

Sep 2026

No notices reported this month

Aug 2026

Discord bots on gamenode01
  • Resolved
    UTC
    Resolved

    Discord has lifted the block on the outgoing IP address of gamenode01. We have removed our own block and all bots are able to connect again.

    If your bot is still offline, restart it once and it should come online normally. There is no need to change anything in your code or your token.

    Thanks for your patience.

  • Update
    UTC
    Update

    Discord has temporarily blocked the outgoing IP address of gamenode01 due to rate limiting on their side. Bots on this node cannot complete the login to Discord because of this. This is not caused by your bot or your token.

    To help the block expire, we have temporarily blocked outgoing Discord traffic on gamenode01 ourselves. Every connection attempt keeps the block alive on Discord's side.

    This means bots that were still working earlier have now lost their Discord connection as well. That is expected and temporary. Other traffic from your server, such as downloads and other APIs, works normally.

    As soon as Discord lifts the block we will remove ours and the bots will come back online. This does not happen automatically, we do it manually and will report it here.

  • Identified
    UTC
    Identified

    We have identified the issue and are currently working on resolving it. This means that Discord bots can be taken offline.

  • Investigating
    UTC
    Investigating

    On gamenode01, Discord bots are currently having trouble reconnecting.

    Bots that are already running and connected continue to work normally; you won't notice anything.

    The problem only occurs with bots that are restarting right now: they load their commands and events normally, but then get stuck when trying to log into Discord.

    The best thing to do: do not restart your bot for a while.

    Is it still running? Then leave it running, even if you wanted to roll out an update - postpone that for a moment. If you have just restarted and it isn't coming online, just let it run: it will connect automatically as soon as it can again. Repeatedly restarting does not help and can make it take longer.

    You do not need to change anything in your code or your token. It does not seem to be due to individual bots; it is affecting multiple bots on this node simultaneously. Other services and other nodes are not affected.

    What we are doing

    We are investigating the source of the problem and will let you know here as soon as there is news,

    or as soon as things are running normally again.

Jul 2026

Network maintenance rack Digital Realty AMS5
  • Completed
    July 24, 2026 at 12:00 AMUTC
    Completed
    July 24, 2026 at 12:00 AMUTC
    Maintenance has completed successfully
  • In progress
    July 23, 2026 at 10:00 PMUTC
    In progress
    July 23, 2026 at 10:00 PMUTC
    Maintenance is now in progress
  • Planned
    July 21, 2026 at 7:11 PMUTC
    Planned
    July 21, 2026 at 7:11 PMUTC

    Our hosting provider is performing network maintenance on the rack in Digital Realty AMS5, replacing equipment with newer network hardware. During this maintenance, brief service interruptions may occur on the VPS Panel.

Recurring network instability affecting multiple nodes
  • Resolved
    UTC
    Resolved

    The cabling fault has been corrected by a datacentre specialist and connectivity has fully stabilized. All affected nodes are back online and operating normally. We’ll continue to keep an eye on things, but the issue is now resolved. Thanks for your patience.

  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    UTC
    Identified

    We’ve identified the cause of the instability. Our network provider found a cabling fault on their side that was causing an unstable connection to our nodes. The nodes stayed online throughout, but connectivity was flapping. Our provider is correcting the cabling as soon as possible, and the connection should stabilize as they complete the work. We’ll confirm once everything is fully recovered.

  • Investigating
    UTC
    Investigating

    We are currently experiencing intermittent network instability affecting several nodes in our BIT (Ede) location. Over the past hour, multiple systems including BIT-1, BIT-2C, and GameNode 01 have gone down and recovered repeatedly, which points to an underlying network issue rather than isolated hardware failures.

    Affected services may experience connectivity loss, latency, or brief unavailability. We have already contacted our network provider and are working with them to identify the root cause and stabilize the network.

    We will post updates as we learn more. Thank you for your patience.

Emergency Maintenance: Kernel Update & Reboot
  • Completed
    July 09, 2026 at 1:14 AMUTC
    Completed
    July 09, 2026 at 1:14 AMUTC
    Maintenance has completed successfully.
  • In progress
    July 09, 2026 at 1:03 AMUTC
    In progress
    July 09, 2026 at 1:03 AMUTC

    Reboot is now in progress.

  • Planned
    July 09, 2026 at 12:59 AMUTC
    Planned
    July 09, 2026 at 12:59 AMUTC

    We are performing an urgent kernel security update, which requires a brief server reboot. Expect a short loss of connectivity during this window.

Client Area (my.flexynode.com) Unavailable
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating

    Our client area at my.flexynode.com is currently unreachable due to an outage at our hosting provider. All other FlexyNode services, including game servers and hosting, remain fully operational and are not affected.

    This means you may temporarily be unable to log in, manage services, or view invoices, but your running services are unaffected.

    We are in contact with our provider and monitoring the situation closely. Updates will follow as soon as we have more information.

    We apologize for the inconvenience and appreciate your patience.

Emergency data center migration (Amsterdam → Ede)
  • Completed
    July 07, 2026 at 3:00 PMUTC
    Completed
    July 07, 2026 at 3:00 PMUTC
    Maintenance has completed successfully
  • Update
    July 07, 2026 at 8:40 AMUTC
    Update
    July 07, 2026 at 8:40 AMUTC

    We have arrived with al of our equipment in BIT, Ede and we will start configuring the rack soon.

  • Update
    July 07, 2026 at 6:14 AMUTC
    Update
    July 07, 2026 at 6:14 AMUTC

    We have now started shutting our own servers off and moving them out of Amsterdam towards Ede

  • In progress
    July 06, 2026 at 7:00 PMUTC
    In progress
    July 06, 2026 at 7:00 PMUTC
    Maintenance is now in progress
  • Planned
    July 06, 2026 at 5:30 PMUTC
    Planned
    July 06, 2026 at 5:30 PMUTC

    We are currently performing an emergency migration of our data center location in Amsterdam to a new location in Ede. This is the result of an acute situation at a party further up our supply chain, causing the power on our current floor to be shut down at very short notice. This is entirely outside our control.

    Downtime will occur during the migration. The exact duration is not yet known; we're keeping it as short as possible and will update this page as soon as we know more.

    No action is required on your part. Thank you for your understanding and patience.

Jul 2026 to Sep 2026

Next