Term activation delayed after confirmed payments
Payments & invoicing · Provisioning pipeline
Timeline
-
Resolved
Resolved at 10:56 UTC. Duration: 17 minutes. Terms were activated up to 11 minutes late; every term runs its full length from the actual activation time.
-
Identified
The activation worker crashed on a malformed order record and did not restart. It has been restarted and the record corrected.
-
Investigating
Payments are being confirmed but the step that activates the term and hands the order to provisioning is not running since 10:39 UTC. Confirmed payments are queued, not lost.
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.