User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
fastly.com · Cloud & developer
Something is off: our checks are slower than usual or had a single recent failure, the vendor reports a minor incident. Official status: Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact
Live diagnosis
Tests fastly.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
Reachable from all 4 regions we check from.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Slow or flaky
Last check reached it in 161 ms · 3 min ago.
Minor incident
Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 1 | 0 | 0.0 | 275 ms | 0 |
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 this status badge · JSON
No outages on record for Fastly yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Fastly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
When Fastly has trouble, these services often do too.
Something is off: our checks are slower than usual or had a single recent failure, the vendor reports a minor incident. Official status: Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact | Osaka (ITM) with Possible Impact
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.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.