Current status
HTTP 503
● Service Unavailable
Uptime 30d
99.42%
▼ SLA breach risk
Avg response 30d
168ms
excludes downtime
Check interval
30 s
2 regions
Active incident · HTTP 503
Started 6 minutes ago · still open
Duration6m 04s
Regions confirmingToronto · Frankfurt
First seen14:22:11 ET
NotifiedSlack · Email · PagerDuty
Detected on interval check, then confirmed by a second-region re-check within ~40 s. Prior incident 8 days ago (SSL renewal) resolved in 4 min.
Uptime timeline · 90 days
1 open incident · 1 resolved
Up
Degraded
Down
90 days ago60 days30 daystoday
Monitors
7 enabled503Uptimeuptime · 30 s
ValidSSL / TLSssl · 47 d left
OKDNSdns · 6 h
PausedVisual regressionvrt · daily
72Performanceperformance · 6 h
88SEOseo-comprehensive · daily
HardenedSecurity headersheaders · 12 h
Response time · 24 h
flatlines during outage
-24 h-12 h-1 hnow
p50 latencyavg 168 ms · p95 240 ms
Recent checks
Toronto + Frankfurt regions| Time (ET) | Region | Status | HTTP | Response | TTFB |
|---|---|---|---|---|---|
| 14:28:11 | Toronto | Down | 503 | — | — |
| 14:27:41 | Frankfurt | Down | 503 | — | — |
| 14:22:11 | Toronto | Down | 503 | — | — |
| 14:21:40 | Frankfurt | Up | 200 | 171 ms | 94 ms |
| 14:21:10 | Toronto | Up | 200 | 158 ms | 88 ms |
| 14:20:40 | Frankfurt | Up | 200 | 166 ms | 91 ms |