Cloud-B

Service status

Updated 19 November 2026, 09:40 CET. Availability is measured by monitoring from two independent locations.

90-day availability

Each bar is one day. Hover over a bar to see the date and its state.

API v1
99.995 %
B-Compute
100.000 %
B-Storage
99.942 %
B-DB
100.000 %
B-DNS
100.000 %
Network, Stockholm
100.000 %
Network, Gothenburg
100.000 %
no incidents degraded outage Data: status.json · Atom

Incident history

Scheduled maintenance: hypervisor upgrades in sto-1a

Maintenance 5 November 2026, 03:00–05:30 CET Completed

Host kernel and NIC firmware upgrades. Instances were live-migrated; no downtime was recorded, and some snapshots took 8 minutes longer than usual.

B-Storage degradation in sto-1b

Minor 14 October 2026, 08:12–09:03 CEST 51 minutes Resolved

Part of the S3 API requests received 503 SlowDown: latency on one storage node grew, and the gateway exhausted its connection pool. No data was lost and replicas remained available.

Incident review and action plan

API errors at the edge

Minor 1 September 2026, 11:42–11:49 CEST 7 minutes Resolved

During a scheduled TLS certificate rotation, some edge nodes kept serving the old chain. About 3% of requests failed with 503; the service recovered once the configuration was synchronised.

DNS latency in got-1a

Minor 27 March 2026, 21:05–21:19 CET 14 minutes Resolved

Response time on secondary servers in Gothenburg rose to 900 ms because of a queue on one resolver. Requests were still served, and no packets were lost.

Notifications. Subscribe to the Atom feed or email status@cloud-b.myftp.org and we will add you to the incident and maintenance mailing list.