Servd Outage History

Between 09:36 and 09:40 UTC, our US-EAST-6 cluster received a large-scale DDoS attack which briefly caused the cluster's load balancers to return 502 Bad Gateway responses to a subset of projects hosted in US-EAST-6. At 09:37 UTC, our automated Cloudflare-backed DDoS protections activated and began blocking malicious traffic. Meanwhile, the clusters load balancers scaled up and error rates dropped back to normal levels. In response, we've permanently increased the baseline capacity of the clusters load balancer and are prioritising measures to better absorb the initial shock of similar DDoS attacks in the future. Apologies for the interruption.

At 00:57 UTC, Servd's US-EAST-1 cluster received a large DDoS attack which lasted 30 seconds. At which point our Cloudflare-backed DDoS protections activated and ended the attack. In the interim, we saw elevated 502 responses as our infrastructure quickly scaled up to handle the load. Apologies for any interruptions to your projects. For those looking to insulate themselves from such attacks we recommend employing [Servd's Private Load Balancer addon](https://servd.host/docs/private-load-balancer-addon).

We're confident the issue has fully resolved. Thanks for your patience.

We've now resolved the incident. Thanks for your patience.

We've now resolved the incident. Thanks for your patience.

We've now resolved the incident. Thanks for your patience.

We've now resolved the incident. Thanks for your patience.

Cloudflare has published a post-mortem blog post about the issue which prompted this disruption to service on Servd. You can read more about it here [https://blog.cloudflare.com/cloudflare-outage-february-20-2026/](https://blog.cloudflare.com/cloudflare-outage-february-20-2026/)

Cloudflare have marked their as resolved https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q We're seeing service back to normal, thanks for your patience.

Between 20:59 and 21:17 UTC there were two drops in connectivity to the US-EAST-7 cluster due to a large scale DDoS attack. The attack was mitigated by our Ingress Platform's DDoS defences, however some attack traffic was able to reach the cluster before the defences automatically activated. We're exploring strategies to better deal with attack traffic prior to our DDoS protections activating.

Cloudflare have marked their incident as fully resolved, and we're no longer seeing any issues across Servd, so are marking this incident as resolved too. Apologies for the disruption.

The upstream AWS issue is now fully resolved.

SSL validation appears to be going through normally now. Thanks for your patience.

Docker Hub (Servd's bundle storage provider) [suffered an incident](https://www.dockerstatus.com/pages/incident/533c6539221ae15e3f000031/68d47a2f93c09e05486d93a9) which prevented Servd's task runner from exporting new bundles during bundles builds and pulling existing bundles during syncs. The upstream incident was fixed by Docker Hub at 1:09 UTC, and all Servd systems are operational once again.

Between 14:04 UTC and 14:32, project requests routing to 74.220.21.86 experienced time outs. The impact was confined to projects that were previously located in our decommissioned UK-LONDON-1 and UK-LONDON-3 clusters that were then migrated over to our active UK-LONDON-4 cluster. These requests utilise our deprecated legacy ingress. To avoid similar issues in the future, we strongly recommend upgrading your impacted projects to our Ingress Platform. https://servd.host/docs/upgrading-to-new-ingress

We've now resolved the incident. Thanks for your patience.

The issue has been resolved with the upstream provider and builds are now progressing as expected.

We've had confirmation from our server provider (DigitalOcean) that the issue originated with their infrastructure. Specifically they state they detected an issue with one of their European carriers which caused outbound traffic from a subset of their locations in London, Amsterdam and Frankfurt to fail. They're working with their carrier to ensure the issue does not reoccur. If you'd like to add resilience against these kinds of incidents to your project, drop a message to [email protected] and we'd be happy to advise.

We've now resolved the incident. Thanks for your patience.

We've now resolved the incident. Thanks for your patience.

We've now resolved the incident. Thanks for your patience.

After monitoring for a few hours, we're satisfied the issue has been resolved.