Status

System status

All systems operational

Last updated 25 September 2026 · times in UTC

OperationalDegradedPartial outage
S3 API100.000% uptime
90 days agoToday
Edge delivery100.000% uptime
90 days agoToday
Management API99.991% uptime
90 days agoToday
Console100.000% uptime
90 days agoToday
Cross-region replication100.000% uptime
90 days agoToday
Event notifications100.000% uptime
90 days agoToday

Regions

Frankfurtfra1 · operational
Amsterdamams1 · operational
Warsawwaw1 · operational
Stockholmsto1 · operational
Istanbulist1 · operational
Yerevanevn1 · operational
Almatyala1 · operational
Dubaidxb1 · operational
Singaporesin1 · operational
Tokyotyo1 · operational

Incident history

Degraded

Elevated replication lag between ams1 and sto1

A misconfigured rate limit on an internal transfer queue slowed replication for objects larger than 1 GiB. Reads and writes were not affected. The limit was corrected and the backlog drained within 47 minutes.

Cross-region replication · duration 47 min · resolved

Degraded

Increased cache-miss latency in sin1

A regional shield node was drained for hardware maintenance before its replacement finished warming. Cache misses in sin1 took up to 180 ms longer for 18 minutes. We now gate drains on a warm-cache check.

Edge delivery · duration 18 min · resolved

Partial outage

Management API returned 503 for bucket creation

A schema migration held a lock longer than expected. Creating and deleting buckets failed for 12 minutes; existing buckets and the S3 API were unaffected. Migrations now run in online mode with a lock timeout.

Management API · duration 12 min · resolved

Degraded

Console usage charts delayed

The metrics pipeline fell behind after a traffic spike, so usage charts lagged by up to 40 minutes. Billing data was complete. We doubled pipeline partitions and added lag alerting.

Console · duration 26 min · resolved

Degraded

Elevated 5xx rate for PUT requests in fra1

A rolling deploy of the metadata tier briefly reduced write capacity. 0.4% of PUT requests in fra1 returned 503 SlowDown for 9 minutes; SDK retries succeeded. Deploy batch size was reduced.

S3 API · duration 9 min · resolved

Incidents older than twelve months are archived and available from support on request.