On March 25th, 2025, Servebolt experienced a network routing issue that resulted in degraded performance and, for some users, temporary unavailability. The issue primarily affected traffic routed through Cloudflare in Amsterdam and was due to routing irregularities between Cloudflare and ERA-IX (Eranium Internet Exchange), which lies outside Servebolt’s infrastructure.
While the root of the problem was external, we treat any service disruption with the utmost seriousness. Our team responded quickly and worked actively with our upstream partners to identify and resolve the issue.
Who was affected: Clients with traffic routed through Cloudflare’s node in Amsterdam, primarily clients in the Netherlands and nearby regions. This includes traffic to website running Accelerated Domains and Servebolt CDN.
What happened: Intermittent or complete unavailability of services.
Who was not affected: Clients served via other regions of the Cloudflare network, or clients not using Cloudflare, Accelerated Domains or Servebolt CDN
Current information indicates that the operator of ERA-IX, a major internet exchange in Amsterdam, identified a routing issue between their systems and Cloudflare at 10:46 CET. To mitigate the issue, they temporarily disabled their connection to Cloudflare at 11:16 CET.
However, the change did not fully take effect across all upstream networks. This caused inconsistencies in how traffic was routed, which continued to disrupt connectivity for some users.
Although our upstream provider was not the source of the issue, a manual refresh of their network configuration at 15:30 CET successfully restored normal traffic flow between Cloudflare, ERA-IX, and affected networks.
This incident occurred within one of the foundational layers of the internet — completely outside of Servebolt’s infrastructure — but it still impacted how some users were able to reach our platform, primarily in and around the Netherlands.
Identifying the root cause of incidents at this level of the internet is often time-consuming. The infrastructure involved spans multiple independent networks, each with limited visibility into the others. This is why resolution and confirmation took several hours, despite active collaboration between the involved parties.
We are currently awaiting further clarification from Cloudflare, Blix, and Eranium. A full and final report will be published once this information is available — expected this week.