No, Fastly is not down
fastly.com is currently up. Our monitoring probes can reach fastly.com and complete a check without errors. Latest response time was 57 ms. The latest automated check was run 2026-08-14 18:20 UTC from primary location.
- Current status
- Operational
- Last check
- Checked every 3 minutes
- Last 24 hours
- 100%
Currently up for 2h 40m
Latest 2026-08-14 18:20 UTC · Primary location
0 incidents, 0m down
- Official status
- Operational
- Our check
- Operational
- Active incident
- None
- Last outage
- 2026-08-13
- Response time
- 57 ms
- User reports
- Normal
None today
Current incident
No active incidents reported by the official Fastly status source.
Response time
Latest 370 ms
Loading response-time chart…
Uptime
Availability from independent checks, with recorded incidents and downtime in each window.
Today
100%
0 incidents, 0m down
Last 7 days
100%
0 incidents, 0m down
Last 30 days
100%
0 incidents, 0m down
Last 365 days
100%
0 incidents, 0m down
Latest Fastly incidents
Recorded outages with duration and start time.
Last recorded 2026-08-13 07:12 UTC
| Incident | Duration | Started |
|---|---|---|
Retrospective: Impacted Performance for Next-Gen WAF (NGWAF) Request Logs and Telemetry Data Resolved | 1 min | 2026-08-13 07:12 UTC |
Retrospective: Impacted Performance for Next-Gen WAF (NGWAF) Request Logs and Telemetry Data Resolved | 1 min | 2026-08-13 06:01 UTC |
Retrospective: Impacted Performance in Johannesburg (JNB) Resolved | 1 min | 2026-08-12 16:57 UTC |
Retrospective: Impacted Performance in Johannesburg (JNB) Resolved | 1 min | 2026-08-12 16:47 UTC |
Retrospective: Impacted Performance in India Resolved | 1 min | 2026-08-12 12:00 UTC |
Retrospective: Impacted Performance in India Resolved | 1 min | 2026-08-12 11:05 UTC |
Elevated Errors for API & Configuration Management Resolved | 1 min | 2026-08-11 09:54 UTC |
How this status checker works
Who's Down Today monitors Fastly independently of the company that runs it. We send reachability checks from our primary location every 3 minutes and record response time, HTTP errors, and timeouts.
When Fastly publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.
This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.
Frequently asked questions
Is Fastly down right now?
- No. No, Fastly is not down. Who's Down Today shows Fastly as operational based on the latest official signals and independent checks. If you still cannot reach fastly.com, the issue may be local to your connection, DNS, VPN, browser, or device.
Is Fastly down for everyone or just me?
- Who's Down Today currently shows Fastly as operational from our monitoring location, which means fastly.com is responding normally to our checks. If you are still having trouble, try another browser, device, or network, and check DNS or VPN settings.
What should I do if fastly.com is up but I still cannot access it?
- Try opening fastly.com from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Fastly outage.
How does Who's Down Today check if Fastly is down?
- We combine independent HTTP reachability checks with public status information where it exists. When Fastly publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.
What does a Fastly outage mean?
- An outage on this page means recorded incidents or failed checks indicated that Fastly was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.
Can this page tell me the root cause of a Fastly outage?
- Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to Fastly's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.
How do I report an issue with Fastly?
- Use the report form on this page if Fastly looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.