No, Fastly is up.
No outage detected, and no user reports in the last hour.
Status just changed to . Refresh for details
1 report in total, counted in 15-minute windows
No problem reports came in for Fastly in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 1 report. There has been no spike in reports since 6 October. These are user reports from the US, where most people report Fastly problems.
Around the world right now: normal in 71 other countries. By country
In the past 24 hours, 1 user report came in for Fastly. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 1 report, about 6 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
People who report a problem with Fastly to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
In the last 24 hours, 3 problem reports about Fastly came in from 2 countries. Right now reports are at the usual level in every country.
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 0 | 2 |
| Sweden | Normal | 0 | 1 |
| Japan | Normal | 0 | 0 |
| Argentina | Normal | 0 | 0 |
| The Netherlands | Normal | 0 | 0 |
| Germany | Normal | 0 | 0 |
| Belgium | Normal | 0 | 0 |
| The UK | Normal | 0 | 0 |
| France | Normal | 0 | 0 |
| Italy | Normal | 0 | 0 |
| India | Normal | 0 | 0 |
| Canada | Normal | 0 | 0 |
Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.
Since 6 October, Fastly had no outage spikes or periods of elevated reports.
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
Country history starts on 29 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 6 October 2026. Monthly reports for all services
Fastly is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach fastly.com over your own connection, right now. Nothing is sent to us or stored.
Look at the report level at the top of this page, which counts user problem reports in 15-minute windows over the last 24 hours. Then open the official status page to see if Fastly has an active incident. This site does not ping or probe the service, so a quiet report level does not prove Fastly is healthy for you.
Turn off your VPN and switch from Wi-Fi to cellular data, then load the same URL again. If the page works there, your router or local DNS resolver is the likely problem. On Windows, run ipconfig /flushdns; on macOS, run sudo killall -HUP mDNSResponder. Try a private window next.
In the Fastly control panel, select the service and open Purge; choose Purge URL and enter the full URL that fails. If you prefer the API, send a PURGE request to that URL with your API key in the Fastly-Key header. A stale edge object can break one visitor while others see the site fine.
Open the service in the Fastly control panel, then check Origins to confirm the origin host and port match your backend. If the domain uses TLS, verify the certificate covers the full hostname and is not expired. Test your origin directly. Fastly cannot serve content when the backend refuses connections.
ping fastly.comTest whether Fastly's servers replynslookup fastly.comCheck that Fastly's DNS resolvestracert fastly.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadping -c 4 fastly.comTest whether Fastly's servers replynslookup fastly.comCheck that Fastly's DNS resolvestraceroute fastly.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadFastly is a content delivery network and edge cloud platform that many large sites, streaming services, e-commerce stores, and apps use to serve pages, images, video, and API traffic. When it fails, those sites and apps can go blank, stall, show missing content, or return errors.
During an outage, cached assets usually fail first: images, stylesheets, scripts, and fonts stop loading, so pages appear unstyled or broken. Video and audio streams that rely on the service can stall or drop, and API calls routed through it may time out or return server errors. You might see a blank screen or a generic service unavailable message. Problems can be regional or partial because traffic reaches different edge locations, though a bad configuration can affect many regions at once.
Checked from our server in Frankfurt, Germany, 3 days ago, for www.fastly.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
All 11 locations got an answer from www.fastly.com. Fastest from Amsterdam (15 ms), slowest from Los Angeles (3,759 ms). Every location connected through Fastly, Inc. (AS54113), using 5 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 286 ms | 151.101.1.57 |
| ViennaAustria | Up | 460 ms | 151.101.1.57 |
| MilanItaly | Up | 1,570 ms | 151.101.193.57 |
| ParisFrance | Up | 383 ms | 151.101.1.57 |
| AmsterdamNetherlands | Up | 15 ms | 151.101.65.57 |
| MadridSpain | Up | 1,928 ms | 151.101.1.57 |
| WarsawPoland | Up | 3,634 ms | 151.101.1.57 |
| Los AngelesUSA | Up | 3,759 ms | 151.101.1.57 |
| São PauloBrazil | Up | 1,527 ms | 151.101.5.57 |
| SingaporeSingapore | Up | 1,090 ms | 151.101.129.57 |
| TokyoJapan | Up | 1,468 ms | 151.101.1.57 |
Checked with check-host.net from its servers in these cities 3 days ago, for www.fastly.com. Time is how long each server took to load the page.
No posts about problems from @fastly in the last 14 days. The latest is from .
Fastly@fastly2:15 AM. Errors spiking. Attack? Outage? Industry-wide botnet? Fastly AEDA (built with Google Cloud's Gemini Enterprise) figures it out for you — autonomous root-cause analysis at the edge, before traffic hits your origin. MTTR: hours → seconds. Early access is open now. 🧵 https://www.fastly.com/blog/fastly-unveils-aeda-autonomous-edge-security-gemini-enterprise
Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.
<a href="https://isitdownrightnow.app/services/fastly/"><img src="https://isitdownrightnow.app/badge/fastly.svg" alt="Fastly status" height="20"></a>[](https://isitdownrightnow.app/services/fastly/)The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.
The status on this page comes from user-submitted problem reports for Fastly, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Fastly, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Fastly's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.
Strips: user reports, last 6 hours, 15 minutes a segment.