All systems operational

Everything is running smoothly.

No incidents declared. We are not actively mitigating any known issues; all three services are responding within normal limits.

Last check

— ago

--:--:-- UTC · every 60 s

Customer-Facing 2 services

API Operational

130 ms

p50 · 24 h

99.97 %

90-day uptime

90 days agoToday

Web App Operational

136 ms

p50 · 24 h

99.64 %

90-day uptime

90 days agoToday

Infrastructure 1 service

Background Jobs Operational

121 ms

p50 · 24 h

99.87 %

90-day uptime

90 days agoToday

Incident history last 90 days

Nov 5

02:19 UTC

Elevated error rate 4 updates → Partial

A configuration push caused one region of Background Jobs to return 5xx responses for a subset of requests. Rolled back and confirmed healthy.

Background Jobs · resolved in 20 min

Oct 14

03:53 UTC

Increased latency 4 updates → Partial

A slow database query introduced in a deploy increased response times for Web App. The query was optimized and latency returned to baseline.

Web App · resolved in 1 h 30 min

Oct 6

05:45 UTC

Increased latency 4 updates → Partial

A slow database query introduced in a deploy increased response times for Web App. The query was optimized and latency returned to baseline.

Web App · resolved in 27 min

Oct 2

01:18 UTC

Network connectivity issue 4 updates → Major

A networking change at our cloud provider made API unreachable from some regions. Traffic was rerouted until the change was reverted.

API · resolved in 43 min

Sep 18

02:25 UTC

Worker pool outage 4 updates → Major

The Background Jobs worker pool failed to restart after a scheduled node upgrade. Service was restored by rolling back the upgrade.

Background Jobs · resolved in 2 h 34 min

Aug 29

01:38 UTC

Service unavailable 4 updates → Major

A failed database failover left Web App unable to serve requests. Traffic was restored after promoting a healthy replica.

Web App · resolved in 2 h 25 min

Aug 11

04:46 UTC

Processing delays 4 updates → Partial

A spike in large uploads created a queue backlog in Web App. No data was lost; processing caught up after additional workers were added.

Web App · resolved in 3 h 28 min