ObjectBasin

Service status

All systems operational · updated 19 Nov 2026 00:30 UTC

RegionNodeAPILatency p50Requests/min
eu-centralfra1Operational17 ms11 k
eu-westams1Operational26 ms9 k
eu-northhel1Operational26 ms2 k
us-eastash1Operational90 ms3 k

Uptime, last 90 days

RegionUptimeDowntime
eu-central (fra1)99.97%45 min
eu-west (ams1)99.94%1 h 21 min
eu-north (hel1)99.98%25 min
us-east (ash1)100.00%0 min

Incident history

DateRegionImpactDurationSummary
2026-11-10ams1Read errors14 minTwo read nodes lost their cache after a failed firmware update and were drained and restarted.
2026-10-28fra1Degraded writes27 minMetadata service leader election took longer than usual; a subset of writes returned 503.
2026-10-15hel1Read errors9 minCache node restart after a kernel update; reads failed over to ams1 automatically.
2026-10-02fra1Partial18 minMultipart complete returned 503 during a rollback; retries succeeded after the deploy settled.
2026-09-19ams1Elevated latency42 minUpstream switch maintenance caused retries on the write path; clients saw p99 above 400 ms.
2026-09-06hel1Partial16 minReplication lag exceeded the alert threshold after a large customer upload finished.
2026-08-24ams1Elevated latency25 minA backup job saturated the metadata disk; read latency rose until the job was rescheduled.

Subscribe to status mail at status@objectbasin.com. Historical metrics are available on request.