System status
Manifest API, edge delivery, signing and dashboard are healthy in all 13 regions. Subscribe to incidents by email at status@nl5.enotcloud.com or add a webhook in workspace settings.
Components
Manifest API
Operational · 99.99% over 90 daysEdge delivery
Operational · 99.97% over 90 daysSigning service
Operational · 100% over 90 daysDashboard and API
Operational · 99.99% over 90 daysWebhooks and log streaming
Operational · 99.94% over 90 daysRegions
| Region | Location | Status | Manifest p50 | 30 days |
|---|---|---|---|---|
| eu-west | Amsterdam | Operational | 9 ms | 11.2 PB |
| eu-north | Stockholm | Operational | 8 ms | 3.1 PB |
| eu-central | Frankfurt | Operational | 9 ms | 9.8 PB |
| us-east | Ashburn | Operational | 10 ms | 10.4 PB |
| us-west | Hillsboro | Operational | 11 ms | 5.9 PB |
| us-central | Dallas | Operational | 11 ms | 3.6 PB |
| sa-east | São Paulo | Operational | 16 ms | 2.8 PB |
| ap-south | Mumbai | Operational | 14 ms | 4.4 PB |
| ap-southeast | Singapore | Operational | 13 ms | 3.9 PB |
| ap-northeast | Tokyo | Operational | 12 ms | 3.6 PB |
| oc-east | Sydney | Operational | 15 ms | 1.3 PB |
| af-south | Johannesburg | Operational | 21 ms | 0.6 PB |
| me-central | Dubai | Operational | 18 ms | 0.8 PB |
Manifest p50 is median response time measured from probes in the region's metro area. The last column is volume delivered from that region over the 30 days to 5 November 2026: 61.4 PB in total.
Past incidents
Elevated manifest latency in sa-east
From 18:12 to 18:50 UTC, manifest responses in São Paulo took up to 900 ms. A cache node with a failing disk was slow rather than down, so health checks kept it in rotation. Traffic was shifted to the neighbouring nodes, the node was replaced, and the health check now also looks at read latency. No updates were lost; devices retried.
Delivery errors in ap-southeast
Between 02:31 and 02:57 UTC, 6% of download requests in Singapore returned errors after a configuration push reduced the cache tier's connection limit. The change was reverted after 26 minutes. Downloads resumed from the last received byte. We now apply cache configuration to one node first and wait for error rates before continuing.
Delayed webhooks
Webhook deliveries and log streams were up to 52 minutes late between 11:05 and 11:57 UTC while a queue was rebalanced. All events were delivered in order and none were dropped.
New regions: Johannesburg and Dubai
af-south and me-central began serving production traffic. Existing devices were not affected; new routing takes effect on each device's next check.
Older incidents are available in the incident log on request: status@nl5.enotcloud.com.