CheckUpstream measured Fastly at 100.000% availability across 672 independent checks (global · api). 149 incidents were recorded in the past 12 months; the most recent resolved earlier today after 27 minutes. Status signals are polled from Fastly's official status feed, alongside independent probes and community reports.
7 days measured availability how this is computed
100.000%
global · api · n=672 · p95 93ms (7d)
Share of our own checks against Fastly endpoints that returned Fastly's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 6 incidents · 3 of 7 days with none posted · 3h 11m of declared impact
Fewer incidents in the last 30 days than 3% of 232 tracked services.
Share of each window with no impact declared by Fastly
7d
98.104%
30d
94.508%
90d
97.840%
180d
92.429%
1y
96.266%
Downtime like this can be refundable
If you're a paying Fastly customer, outages in these windows may count against Fastly's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Fastly entitlement →Does Fastly actually matter to you?
A Fastly outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=51~220m (p25 66m – p75 2389m)
Based on 51 historical Major incidents · currently 37m elapsed.
From 5 incidents Fastly published and resolved in the last 7 days, measured between their own start and resolution times. It describes how long Fastly takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 1 still open.
Sep 1, 06:13 UTC · resolved in 27m · Resolved
Sep 1, 06:13 UTC · in progress · Investigating
Aug 29, 03:45 UTC · resolved in 1h 5m · Resolved
Aug 29, 03:45 UTC
Live Fastly status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/fastly)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Fastly is currently Partial Outage. CheckUpstream tracks Fastly in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Fastly's last resolved incident started earlier today and lasted 27 minutes (a partial outage).
Looking for the live "is Fastly down" view? See the Fastly Live status page.
Aug 26, 07:00 UTC · resolved in 1h 50m · Resolved
Aug 24, 15:20 UTC · resolved in 20m · Resolved
Aug 22, 04:06 UTC · resolved in 9m · Resolved
Aug 22, 04:04 UTC · resolved in 11m · Resolved
Aug 22, 03:15 UTC · resolved in 20m · Resolved
Aug 21, 00:33 UTC · resolved in 28m · Resolved
Aug 20, 23:32 UTC · resolved in 29m · Resolved
Aug 20, 22:33 UTC · resolved in 37m · Resolved
Aug 20, 22:33 UTC · resolved in 36m · Investigating
Aug 20, 21:24 UTC · resolved in 46m · Resolved
Aug 20, 21:24 UTC · resolved in 46m · Resolved
Aug 20, 06:21 UTC · resolved in 1h 50m · Investigating
Aug 19, 22:09 UTC · resolved in 1m · Resolved
Fastly's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Fastly endpoints. It is the share of checks that returned the expected response, not a figure taken from Fastly's status page.
Sign up to CheckUpstream and add Fastly to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Fastly's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.