User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
fasterize.com · Cloud & developer
Is Fasterize down?
Something is off: our checks are slower than usual or had a single recent failure.
What to try while Fasterize is having problems
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → fasterize.com—
Your browser → us—
Our checksSlow or flaky
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Slow or flaky
Last check reached it in 104 ms · 9 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 61 ms | 0 |
| 03:30 | 0 | 0.0 | 233 ms | 0 |
| 03:45 | 0 | 0.0 | 289 ms | 0 |
| 04:00 | 0 | 0.0 | 92 ms | 0 |
| 04:15 | 0 | 0.0 | 136 ms | 0 |
| 04:30 | 0 | 0.0 | 52 ms | 0 |
| 04:45 | 0 | 0.0 | 68 ms | 0 |
| 05:00 | 0 | 0.0 | 54 ms | 0 |
| 05:15 | 0 | 0.0 | 95 ms | 0 |
| 05:30 | 0 | 0.0 | 114 ms | 0 |
| 05:45 | 0 | 0.0 | 36 ms | 0 |
| 06:00 | 0 | 0.0 | 64 ms | 0 |
| 06:15 | 0 | 0.0 | 106 ms | 0 |
| 06:30 | 0 | 0.0 | 118 ms | 0 |
| 06:45 | 0 | 0.0 | 116 ms | 0 |
| 07:00 | 0 | 0.0 | 213 ms | 0 |
| 07:15 | 0 | 0.0 | 50 ms | 0 |
| 07:30 | 0 | 0.0 | 75 ms | 0 |
| 07:45 | 0 | 0.0 | 52 ms | 0 |
| 08:00 | 0 | 0.0 | 84 ms | 0 |
| 08:15 | 0 | 0.0 | 55 ms | 0 |
| 08:30 | 0 | 0.0 | 81 ms | 0 |
| 08:45 | 0 | 0.0 | 51 ms | 0 |
| 09:00 | 0 | 0.0 | 52 ms | 0 |
| 09:15 | 0 | 0.0 | 70 ms | 0 |
| 09:30 | 0 | 0.0 | 55 ms | 0 |
| 09:45 | 0 | 0.0 | 81 ms | 0 |
| 10:00 | 0 | 0.0 | 40 ms | 0 |
| 10:15 | 0 | 0.0 | 61 ms | 0 |
| 10:30 | 0 | 0.0 | 84 ms | 0 |
| 10:45 | 0 | 0.0 | 108 ms | 0 |
| 11:00 | 0 | 0.0 | 106 ms | 0 |
| 11:15 | 0 | 0.0 | 54 ms | 0 |
| 11:30 | 0 | 0.0 | 114 ms | 0 |
| 11:45 | 0 | 0.0 | 34 ms | 0 |
| 12:00 | 0 | 0.0 | 74 ms | 0 |
| 12:15 | 0 | 0.0 | 80 ms | 0 |
| 12:30 | 0 | 0.0 | 98 ms | 0 |
| 12:45 | 0 | 0.0 | 43 ms | 0 |
| 13:00 | 0 | 0.0 | 72 ms | 0 |
| 13:15 | 0 | 0.0 | 50 ms | 0 |
| 13:30 | 0 | 0.0 | 97 ms | 0 |
| 13:45 | 0 | 0.0 | 135 ms | 0 |
| 14:00 | 0 | 0.0 | 83 ms | 0 |
| 14:15 | 0 | 0.0 | 279 ms | 0 |
| 14:30 | 0 | 0.0 | 148 ms | 0 |
| 14:45 | 0 | 0.0 | 5939 ms | 0 |
| 15:00 | 0 | 0.0 | 104 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Fasterize status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Fasterize yet. Outages of 10 minutes or more get their own page here.
Having trouble with Fasterize?
One report per service every 10 minutes from this network. No account.
Follow Fasterize
Get an email when Fasterize goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fasterize alerts to Slack, Discord or a webhook — free.
Questions
Is Fasterize down right now?
Something is off: our checks are slower than usual or had a single recent failure.
Fasterize not working for me but the status is fine. What now?
If Fasterize is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Fasterize's side.
How does Damn is it down decide Fasterize's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Fasterize checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.