Skip to content

Outage tracker / Fastly

Is Fastly down?

I'm having a problem

Operationalchecked moments ago

We reached Fastly from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 12 days we have measured Fastly (since Aug 20, 2026).

our independent probeslive · checked Sep 1, 2026, 4:09 AM UTC
US-East488 msOperational
US-West109 msOperational
Europe166 msOperational
Asia-Pacific359 msOperational
their status pagetheir claim, not our reading

Fastly publishes no status feed we can read, so the only independent reading here is ours on the left.

Fastly response time, by region

US-East
539msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 379ms2026-08-21 UTC: p95 392ms2026-08-22 UTC: p95 378ms2026-08-23 UTC: p95 554ms2026-08-24 UTC: p95 492ms2026-08-25 UTC: p95 523ms2026-08-26 UTC: p95 464ms2026-08-27 UTC: p95 407ms2026-08-28 UTC: p95 568ms2026-08-29 UTC: p95 585ms2026-08-30 UTC: p95 750ms2026-08-31 UTC: p95 664ms2026-09-01 UTC: p95 539ms
Aug 3Aug 17Sep 1
US-West
371msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 441ms2026-08-21 UTC: p95 364ms2026-08-22 UTC: p95 393ms2026-08-23 UTC: p95 333ms2026-08-24 UTC: p95 458ms2026-08-25 UTC: p95 414ms2026-08-26 UTC: p95 422ms2026-08-27 UTC: p95 557ms2026-08-28 UTC: p95 527ms2026-08-29 UTC: p95 535ms2026-08-30 UTC: p95 800ms2026-08-31 UTC: p95 678ms2026-09-01 UTC: p95 371ms
Aug 3Aug 17Sep 1
Europe
266msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 151ms2026-08-21 UTC: p95 189ms2026-08-22 UTC: p95 214ms2026-08-23 UTC: p95 346ms2026-08-24 UTC: p95 603ms2026-08-25 UTC: p95 357ms2026-08-26 UTC: p95 556ms2026-08-27 UTC: p95 333ms2026-08-28 UTC: p95 549ms2026-08-29 UTC: p95 333ms2026-08-30 UTC: p95 338ms2026-08-31 UTC: p95 318ms2026-09-01 UTC: p95 266ms
Aug 3Aug 17Sep 1
Asia-Pacific
379msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 480ms2026-08-21 UTC: p95 768ms2026-08-22 UTC: p95 772ms2026-08-23 UTC: p95 892ms2026-08-24 UTC: p95 856ms2026-08-25 UTC: p95 882ms2026-08-26 UTC: p95 801ms2026-08-27 UTC: p95 707ms2026-08-28 UTC: p95 752ms2026-08-29 UTC: p95 732ms2026-08-30 UTC: p95 733ms2026-08-31 UTC: p95 764ms2026-09-01 UTC: p95 379ms
Aug 3Aug 17Sep 1

Is it Fastly, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Fastly -- it cannot diagnose Fastly's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 488msstatus code: 200checked: Sep 1, 2026, 4:09 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Fastly normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 109msstatus code: 200checked: Sep 1, 2026, 4:07 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Fastly normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 166msstatus code: 200checked: Sep 1, 2026, 4:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Fastly normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 359msstatus code: 200checked: Sep 1, 2026, 4:04 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Fastly normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionFastly is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionFastly is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionFastly is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionFastly is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionFastly is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionFastly is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Fastly, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Fastly yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Fastly.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Fastly since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Fastly covering any window you pick, with our measurements and Fastly's own claim at the time, side by side.

Full availability history for Fastly: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Fastly, and again when they can reach it again. That is our own measurement from ten regions, not Fastly's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Fastly uptime measured by RealUptimeLive, from this page's own readings.
[![Fastly uptime measured by RealUptime](https://realuptime.io/outages/fastly/badge.svg?days=30)](https://realuptime.io/outages/fastly)
<a href="https://realuptime.io/outages/fastly"><img src="https://realuptime.io/outages/fastly/badge.svg?days=30" alt="Fastly uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Fastly's SLA implies, from our measurement

At or above your target

We measured none of downtime for Fastly over the 292h 10m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 17 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Fastly's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.fastly.com/public-ip-list
RealUptime is not affiliated with Fastly; the name identifies what we measured, and nothing here speaks for Fastly's own team. We send a single web request to Fastly from 4 regions on our own schedule and time the response. We do not see inside Fastly's systems, do not use an account or real transaction, and are not the same signal Fastly's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Fastly is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Fastly operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 20, 2026 (12 of 14 days so far, 6154 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.