Status
1
active incident
12
healthy services
99.97
% uptime · 30d
04:18
mean response · ms
Active

In progressDatabase storage expansion

Started 2026-06-12 · 12:10 UTC · expected duration ~2h · change CHG-2026-06-1218

We are expanding storage on the primary cluster to support higher write throughput. The API will return 503 during this window. No customer data is affected. Replication is paused for the duration of the migration.

Timeline Affected services Regions
11:55 — preflight checks passed, all green
12:00 — backup verified: snap-2026-06-12-1155 hash ok
12:10 — entered maintenance state, traffic draining
12:14 — replication paused on follower-a / follower-b
12:22 — volume snap-2026-06-12-1218 attached to primary
12:36 — data copy 37% complete · 1.4 TB / 3.8 TB
12:51 — data copy 58% complete · 2.2 TB / 3.8 TB
13:02 — short blip on follower-c, recovered automatically (no impact)
13:14 — data copy 81% complete · 3.1 TB / 3.8 TB
API gatewayoffline
Dashboardoffline
Write APIoffline
Read API (replicas)degraded
Webhook deliveryqueued
Static / CDNhealthy
Status pagehealthy
eu-west-1maintenance · primary
eu-north-1read-only · replicas
us-east-1read-only · replicas
ap-southeast-1read-only · replicas
sa-east-1read-only · replicas
af-south-1read-only · replicas
Recent

CompletedPre-checks and snapshot

11:55 UTC — 12:10 UTC · duration 15 min

All preflight checks passed. Backup taken. Verification hash matched expected value. Followers acknowledged the new write lock cleanly.

CompletedEdge cache warmup

2026-06-11 · 23:00 UTC — 23:42 UTC

Pre-warmed the CDN edge caches in anticipation of the maintenance window. 4 762 origin requests served, 99.4% cache hit ratio achieved.

CompletedCustomer notification

2026-06-08 · sent 14 200 emails / 6 800 in-app banners

Maintenance window announced 96 hours in advance to all subscribed customers. Open rate 71%, no opt-outs above baseline.

Want updates by email? We'll send one note when an incident opens and one when it closes. No marketing.

About this page. Status is updated automatically from internal monitoring every 60 seconds, and manually annotated by the on-call team. If you spot a discrepancy between what you're experiencing and what we report, please write to status@chiselport.io — we'd rather know.
— operations · ChiselPort.io · paged team: ops-east-2
RSS · Atom · webhook · email subscriptions available