System status
All systems operational Last checked from this node moments ago. Component checks run every 30 seconds from three independent regions.
| Component | Status | p50 latency | Uptime, 90d |
|---|---|---|---|
| Edge delivery — Europe | operational | 11 ms | 99.997% |
| Edge delivery — North America | operational | 14 ms | 99.995% |
| Edge delivery — Asia Pacific | operational | 19 ms | 99.991% |
| Edge delivery — South America | operational | 24 ms | 99.988% |
| Edge delivery — Africa & Middle East | operational | 31 ms | 99.972% |
| Control plane API | operational | 48 ms | 99.994% |
| Purge pipeline | operational | 340 ms | 99.999% |
| Certificate issuance | operational | 2.1 s | 99.981% |
| Log delivery | operational | 6 s | 99.966% |
Recent history
4 August 2026 — Elevated latency at bom1
resolved · 41 minutes. A transit provider in Mumbai reconverged after a submarine cable fault on SEA-ME-WE 5. Traffic shifted to sin1 automatically; p95 latency for affected users rose to 84 ms for the duration. No requests were dropped.
19 July 2026 — Purge pipeline backlog
resolved · 12 minutes. A schema migration on the purge coordinator held a lock longer than its timeout. Purges queued rather than failing, and drained within four minutes of the lock clearing. Cache correctness was not affected. We have since split the migration path from the request path.
2 July 2026 — Scheduled maintenance, mil1
completed · 2 hours. Facility power maintenance at Caldera 21. The site was drained ahead of the window and returned to service without incident.
11 June 2026 — Certificate issuance delays
resolved · 3 hours 20 minutes. Rate limiting upstream at our ACME provider slowed new issuance. Existing certificates and renewals were unaffected; new domains waited an average of 26 minutes. We now spread issuance across two ACME providers.
Subscribe to updates at status@digitalprovider.online, or poll /v1/edge/status from your own monitoring.