Compare

Cloudflare vs Heroku

Admitted uptime

Last 30 daysTime not covered by a Sev 1 the provider posted itself. A best case.
100.00%
100.00%
Last 90 days
100.00%
100.00%
Last 12 months
100.00%
100.00%

Grades (90 days)

OverallSeverity weight × minutes, summed over the window. Fewer points, better grade.
F · 12,221 pts
A+ · 0 pts
ProductionYour users are hit: apps, APIs, databases, inference
F
A+
ShippingYou can't deploy, build or manage: CI, CLI, dashboard, auth, billing
B
A+

Incidents (90 days)

Total incidentsEverything posted on the status page except scheduled maintenance.
54
0
Sev 1 · Lights outProd site, API or database down, or data loss
0
0
Sev 2 · BleedingProd degraded or partly down
34
0
Sev 3 · Can't shipCan't deploy, build or manage it
13
0
Sev 4 · PapercutDocs, status page, slow dashboard
7
0
Median fixMedian time to resolve. Half of incidents were fixed faster.
1h 13m
–
LongestLongest single incident, start to resolved.
55d 20h
–
Security incidentsIncidents the provider flagged as security. They count one tier higher.
0
0

Trend and communication

Last 6 months vs 6 beforeIncident count, last 6 months against the 6 before.
Worse (0 → 54)
Flat (0 → 0)
Sev 1–2 postmortemsSev 1–2 incidents with a published write-up.
0 of 34
0 of 0

Cost

Per month512 MB app on all month, 1M requests, 100 GB out, commercial use, one seat. Cheapest plan that runs it.
~$5
$7
Plan or model
Workers Paid
Basic dyno
Best valueNobody else here costs the same or less with the same or better grade.
Yes
Yes
VerdictHeroku has the best 90-day record; Cloudflare resolves incidents fastest.Running app? Watch Production. Deploying all day? Watch Shipping.

Matchups

Uptime as admitted on each status page. How grades work