All systems operational

Refreshed just now · UTC+0
Last 24h: 100.00%
Last 7d: 100.00%
Last 90d: 99.991%

// COMPONENTS

Edge Runtime v8 isolates · WASM Operational
Deployment API api.edgeapi.date/v1 Operational
Edge KV 320-region replicated Operational
Edge D1 SQLite primary-replica Operational
Build Pipeline esbuild · cargo · tinygo Operational
Dashboard app.edgeapi.date Operational
Logs Pipeline streaming · 30d retention Operational
Authentication OAuth · API tokens Operational

// UPTIME — LAST 90 DAYS

Edge Runtime 99.991% · 4 incidents
90 days agotoday
Deployment API 99.998% · 1 incident
90 days agotoday
Edge KV + D1 100.000% · 0 incidents
90 days agotoday

// RECENT INCIDENTS

Build pipeline degraded performance — Apr 22, 2026 · resolved in 18 min

An upstream container registry returned elevated 5xx responses, causing deployment build times to increase by an average of 40%. New deployments still completed successfully but slower than usual. Existing functions continued to serve traffic normally.

14:02 UTCMonitoring detected elevated build latency in EU regions
14:08 UTCInvestigating upstream registry response codes
14:14 UTCFailover to secondary registry initiated
14:20 UTCBuild times returned to baseline · monitoring
14:35 UTCIncident closed
Logs pipeline delays in EU regions — Mar 30, 2026 · resolved in 44 min

Customers in EU regions reported log streaming latency of up to 90 seconds (normal: <3s). Function execution was unaffected. Caused by a hot partition in the log ingestion cluster after a traffic spike. Manual rebalance restored normal latency.

09:14 UTCCustomer reports of log delays in fra1, ams1
09:22 UTCIdentified hot partition in log shard pool
09:38 UTCInitiated partition rebalance
09:58 UTCLatency normalized · backlog drained
Scheduled D1 cluster maintenance — Feb 12, 2026 · completed

Planned upgrade of the Edge D1 storage layer to v2.4. Read replicas remained available throughout. Writes were paused for a 90-second window during the failover. Customers were notified 7 days in advance.

02:00 UTCMaintenance window opened
02:14 UTCPrimary failover initiated
02:15 UTCWrite pause (90s)
02:17 UTCNew primary promoted · writes resumed
02:42 UTCMaintenance window closed

// SUBSCRIBE TO UPDATES

Subscribed. We'll email you within seconds of any incident affecting your services.