Skip to content

Outage tracker / Fastly

Is Fastly down?

I'm having a problem

Checks passingchecked moments ago

Our checks of Fastly pass from all 10 regions we check.

As of Nov 5, 2026, 2:28 PM UTC, RealUptime's checks of Fastly passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Fastly did not fail from two or more distant regions in the 77 days we have checked it (since Aug 20, 2026). This does not show Fastly works for users.

our check readinglive · checked Nov 5, 2026, 2:28 PM UTC
US-East1149 msChecks passing
US-West745 msChecks passing
Europe828 msChecks passing
Asia-Pacific789 msChecks passing
US-Central198 msChecks passing
Canada758 msChecks passing
UK347 msChecks passing
Southeast Asia269 msChecks passing
Australia823 msChecks passing
South America1364 msChecks passing
their status pagetheir claim, not our reading

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

Fastly response time, by region

US-East
1.0sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 643ms2026-10-08 UTC: p95 554ms2026-10-09 UTC: p95 533ms2026-10-10 UTC: p95 494ms2026-10-11 UTC: p95 548ms2026-10-12 UTC: p95 484ms2026-10-13 UTC: p95 502ms2026-10-14 UTC: p95 525ms2026-10-15 UTC: p95 570ms2026-10-16 UTC: p95 535ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
US-West
1.3sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 437ms2026-10-08 UTC: p95 422ms2026-10-09 UTC: p95 390ms2026-10-10 UTC: p95 400ms2026-10-11 UTC: p95 459ms2026-10-12 UTC: p95 579ms2026-10-13 UTC: p95 608ms2026-10-14 UTC: p95 671ms2026-10-15 UTC: p95 664ms2026-10-16 UTC: p95 617ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Europe
852msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 252ms2026-10-08 UTC: p95 265ms2026-10-09 UTC: p95 269ms2026-10-10 UTC: p95 254ms2026-10-11 UTC: p95 345ms2026-10-12 UTC: p95 397ms2026-10-13 UTC: p95 314ms2026-10-14 UTC: p95 298ms2026-10-15 UTC: p95 272ms2026-10-16 UTC: p95 274ms2026-10-17 UTC: p95 796ms2026-10-18 UTC: p95 896ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 712ms2026-10-23 UTC: p95 685ms2026-10-24 UTC: p95 675ms2026-10-25 UTC: p95 598ms2026-10-26 UTC: p95 618ms2026-10-27 UTC: p95 653ms2026-10-28 UTC: p95 441ms2026-10-29 UTC: p95 670ms2026-10-30 UTC: p95 792ms2026-10-31 UTC: p95 625ms2026-11-01 UTC: p95 916ms2026-11-02 UTC: p95 732ms2026-11-03 UTC: p95 648ms2026-11-04 UTC: p95 658ms2026-11-05 UTC: p95 852ms
Oct 7Oct 21Nov 5
Asia-Pacific
1.5sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 919ms2026-10-08 UTC: p95 864ms2026-10-09 UTC: p95 1s2026-10-10 UTC: p95 752ms2026-10-11 UTC: p95 836ms2026-10-12 UTC: p95 931ms2026-10-13 UTC: p95 918ms2026-10-14 UTC: p95 947ms2026-10-15 UTC: p95 986ms2026-10-16 UTC: p95 989ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 401ms2026-10-26 UTC: p95 754ms2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 873ms2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 993ms2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
US-Central
1.1sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 409ms2026-10-08 UTC: p95 449ms2026-10-09 UTC: p95 465ms2026-10-10 UTC: p95 407ms2026-10-11 UTC: p95 392ms2026-10-12 UTC: p95 374ms2026-10-13 UTC: p95 452ms2026-10-14 UTC: p95 507ms2026-10-15 UTC: p95 464ms2026-10-16 UTC: p95 332ms2026-10-17 UTC: p95 702ms2026-10-18 UTC: p95 814ms2026-10-19 UTC: p95 894ms2026-10-20 UTC: p95 830ms2026-10-21 UTC: p95 666ms2026-10-22 UTC: p95 325ms2026-10-23 UTC: p95 501ms2026-10-24 UTC: p95 402ms2026-10-25 UTC: p95 680ms2026-10-26 UTC: p95 628ms2026-10-27 UTC: p95 586ms2026-10-28 UTC: p95 496ms2026-10-29 UTC: p95 537ms2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Canada
1.3sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 828ms2026-10-08 UTC: p95 879ms2026-10-09 UTC: p95 868ms2026-10-10 UTC: p95 840ms2026-10-11 UTC: p95 874ms2026-10-12 UTC: p95 946ms2026-10-13 UTC: p95 834ms2026-10-14 UTC: p95 781ms2026-10-15 UTC: p95 938ms2026-10-16 UTC: p95 940ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 879ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
UK
692msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 412ms2026-10-08 UTC: p95 473ms2026-10-09 UTC: p95 443ms2026-10-10 UTC: p95 443ms2026-10-11 UTC: p95 443ms2026-10-12 UTC: p95 475ms2026-10-13 UTC: p95 373ms2026-10-14 UTC: p95 371ms2026-10-15 UTC: p95 419ms2026-10-16 UTC: p95 337ms2026-10-17 UTC: p95 822ms2026-10-18 UTC: p95 965ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 661ms2026-10-23 UTC: p95 824ms2026-10-24 UTC: p95 849ms2026-10-25 UTC: p95 812ms2026-10-26 UTC: p95 836ms2026-10-27 UTC: p95 677ms2026-10-28 UTC: p95 729ms2026-10-29 UTC: p95 606ms2026-10-30 UTC: p95 559ms2026-10-31 UTC: p95 570ms2026-11-01 UTC: p95 599ms2026-11-02 UTC: p95 931ms2026-11-03 UTC: p95 688ms2026-11-04 UTC: p95 650ms2026-11-05 UTC: p95 692ms
Oct 7Oct 21Nov 5
Southeast Asia
1.5sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 996ms2026-10-17 UTC: p95 2.3s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.5s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 2.0s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
Australia
1.4sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 662ms2026-10-08 UTC: p95 708ms2026-10-09 UTC: p95 713ms2026-10-10 UTC: p95 657ms2026-10-11 UTC: p95 696ms2026-10-12 UTC: p95 696ms2026-10-13 UTC: p95 695ms2026-10-14 UTC: p95 791ms2026-10-15 UTC: p95 735ms2026-10-16 UTC: p95 793ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 925ms2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 938ms2026-10-26 UTC: p95 908ms2026-10-27 UTC: p95 966ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 999ms2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
South America
2.0sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 944ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 951ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 8.9s2026-10-24 UTC: p95 1.0s2026-10-25 UTC: p95 974ms2026-10-26 UTC: p95 933ms2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5

Check your own site while you wait on Fastly

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 we measured, function by function

Fastly answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Edge deliveryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Fastly APIUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Get an email when our checks of Fastly fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Fastly fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Fastly's official status.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1149msstatus code: 200checked: Nov 5, 2026, 2:23 PM 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
      Checks passinglatency: 745msstatus code: 200checked: Nov 5, 2026, 2:22 PM 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.
    • US-Central
      Checks passinglatency: 198msstatus code: 200checked: Nov 5, 2026, 2:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Fastly normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 758msstatus code: 200checked: Nov 5, 2026, 2:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Fastly normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1364msstatus code: 200checked: Nov 5, 2026, 2:24 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Fastly normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 828msstatus code: 200checked: Nov 5, 2026, 2:28 PM 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.
    • UK
      Checks passinglatency: 347msstatus code: 200checked: Nov 5, 2026, 2:13 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Fastly normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 789msstatus code: 200checked: Nov 5, 2026, 2:05 PM 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.
    • Southeast Asia
      Checks passinglatency: 269msstatus code: 200checked: Nov 5, 2026, 2:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Fastly normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 823msstatus code: 200checked: Nov 5, 2026, 2:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Fastly normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

No probe events on record yet for Fastly.

check 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 check readings and Fastly's own claim at the time, side by side.

Full check history for Fastly: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Fastly uptime by RealUptime's checksLive, from this page's own readings.
[![Fastly uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Fastly down?", https://realuptime.io/outages/fastly. The readings change with every check, so give the date you read them.

How our checks compare with Fastly's stated SLA

At or above your target

Our checks of Fastly failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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
secondary
https://api.fastly.com/service
secondary
https://www.fastly.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: api.fastly.com

RealUptime is not affiliated with Fastly; the name identifies what we checked, and nothing here speaks for Fastly's own team. We send a single web request to Fastly from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.