Elevated error rate on gpuserver.io
Website & configurator
Timeline
-
Resolved
Resolved at 14:17 UTC. Duration: 15 minutes. Order requests submitted during the window were either completed normally or shown an error immediately; none was silently lost.
-
Identified
A deployment at 14:02 UTC exhausted the application worker pool under an unexpected request pattern. We have rolled the deployment back.
-
Investigating
About 25% of requests to gpuserver.io are returning a 502 since 14:02 UTC. The configurator is affected. Machines, payments and provisioning are not.
A post-incident review is published here within five days of resolution.
Times are shown in your time zone ().
Related pages
- Service statusLive status of every gpuserver.io component and data centre, probed every 60 seconds from five cities, with 90-day uptime and the incident log since 2022.
- Incident historyEvery incident and maintenance window on gpuserver.io since monitoring began in September 2022, month by month, with its timeline and post-incident review.
- Service level agreementThe 99.9% commitment: what counts as downtime, how it is measured from outside, five minutes of term back per minute lost, and the exclusions in full.
- NetworkUnmetered ports up to 25 Gbit/s, two carriers and an IX per site, always-on DDoS filtering, routed IPv6 — and the four things we do not offer, stated up front.