Skip to content

System status

All systems operationalUpdated 5 Nov 2026, 09:40 UTC

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 days
90 days agoToday

Edge delivery

Operational · 99.97% over 90 days
90 days agoToday

Signing service

Operational · 100% over 90 days
90 days agoToday

Dashboard and API

Operational · 99.99% over 90 days
90 days agoToday

Webhooks and log streaming

Operational · 99.94% over 90 days
90 days agoToday

Regions

RegionLocationStatusManifest p5030 days
eu-westAmsterdamOperational9 ms11.2 PB
eu-northStockholmOperational8 ms3.1 PB
eu-centralFrankfurtOperational9 ms9.8 PB
us-eastAshburnOperational10 ms10.4 PB
us-westHillsboroOperational11 ms5.9 PB
us-centralDallasOperational11 ms3.6 PB
sa-eastSão PauloOperational16 ms2.8 PB
ap-southMumbaiOperational14 ms4.4 PB
ap-southeastSingaporeOperational13 ms3.9 PB
ap-northeastTokyoOperational12 ms3.6 PB
oc-eastSydneyOperational15 ms1.3 PB
af-southJohannesburgOperational21 ms0.6 PB
me-centralDubaiOperational18 ms0.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

DegradedResolved

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.

Partial outageResolved

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.

DegradedResolved

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.

MaintenanceCompleted

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.