Image writes slow in AMS
Provisioning pipeline
Timeline
-
Resolved
Resolved at 12:22 UTC. Duration: 1 h 56 min. Deliveries in AMS were up to 68 minutes late; every affected order was delivered within its promised window or the customer was told.
-
Monitoring
Image writes are back to full speed. The queue in AMS is clearing.
-
Identified
The image mirror in AMS is serving from a degraded RAID set while it rebuilds. We have pointed AMS at the Iberia mirror in the meantime.
-
Investigating
Provisioning in AMS is taking longer than usual since 10:26 UTC: the operating-system image write step is running at a fraction of its normal speed. Deliveries in other sites are on time.
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.