BlastRadius

Live service status

Production blastradius.live

Event browse 99.99%24h 99.99%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 164ms · p95 230ms
API 99.99%24h 99.98%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 214ms · p95 297ms
CF monitor plane 100.00%24h 100.00%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 123ms · p95 142ms
Ingestion API 99.99%24h 99.98%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 179ms · p95 232ms
App links 100.00%24h 100.00%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 83ms · p95 112ms
Website 100.00%24h 100.00%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 335ms · p95 557ms
Sign-in & sessions● Operational

Staging blastradius-dev.live

Event browse 100.00%24h 99.94%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 168ms · p95 250ms
API 99.93%24h 99.92%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 233ms · p95 396ms
Ingestion API 99.93%24h 99.91%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 182ms · p95 286ms
App links 100.00%24h 100.00%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 112ms · p95 161ms
Website 100.00%24h 99.96%7d ● Operational
apac-singapore● ok
eur-belgium● ok
sa-brazil-sao_paulo● ok
usa-iowa● ok
usa-oregon● ok
usa-virginia● ok
Latency (24h, 5-min buckets averaged across regions): p50 421ms · p95 600ms
Sign-in & sessions● Operational

Monitoring planes

Cloudflare-plane monitor● Operational

Past incidents auto-derived from prober data, 14-day window

API Staging Sep 2, 21:37 UTC · 5 min
Ingestion API Staging Sep 2, 21:37 UTC · 5 min
Website Staging Aug 31, 19:37 UTC · 10 min
Website Staging Aug 31, 19:22 UTC · 5 min
Website Staging Aug 30, 19:42 UTC · 20 min
Website Staging Aug 30, 19:12 UTC · 25 min
Website Staging Aug 30, 18:32 UTC · 5 min
Ingestion API Staging Aug 25, 19:12 UTC · 5 min
An incident is a sustained multi-region failure (under 70% of probe regions passing for a 5-minute bucket). Brief single-region blips lower the uptime percentages above without appearing here — which is why an uptime under 100% can coexist with an empty incident list.