Between 14:55 and 15:10 CAT, the Public API, DNS, Monitoring, and Billing were unavailable, and parts of the platform were degraded. The cause was a backend deployment that failed to start correctly. We fixed the deployment pipeline and restored service at 15:10. Running virtual machines were not affected, and no monitoring data was lost: metrics collected during the outage were queued and delivered once service recovered.
Resolved
Between 14:55 and 15:10 CAT, the Public API, DNS, Monitoring, and Billing were unavailable, and parts of the platform were degraded. The cause was a backend deployment that failed to start correctly. We fixed the deployment pipeline and restored service at 15:10. Running virtual machines were not affected, and no monitoring data was lost: metrics collected during the outage were queued and delivered once service recovered.
Investigating
We are investigating an issue affecting the Strettch Cloud Public API, DNS, Monitoring, and Billing, and parts of the platform. Running compute instances are not affected.
