Skip to content

Outage tracker / Fastly

Is Fastly down?

I'm having a problem

Checks passingchecked 1 minute ago

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

As of Oct 23, 2026, 12:39 AM 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 64 days we have checked it (since Aug 20, 2026). This does not show Fastly works for users.

our check readinglive · checked Oct 23, 2026, 12:39 AM UTC
US-East1165 msChecks passing
US-West927 msChecks passing
Europe270 msChecks passing
Asia-Pacific1282 msChecks passing
US-Central138 msChecks passing
Canada854 msChecks passing
UK565 msChecks passing
Southeast Asia851 msChecks passing
Australia819 msChecks passing
South America864 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
642msp95 · 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-09-24 UTC: p95 991ms2026-09-25 UTC: p95 837ms2026-09-26 UTC: p95 855ms2026-09-27 UTC: p95 782ms2026-09-28 UTC: p95 838ms2026-09-29 UTC: p95 922ms2026-09-30 UTC: p95 862ms2026-10-01 UTC: p95 618ms2026-10-02 UTC: p95 515ms2026-10-03 UTC: p95 528ms2026-10-04 UTC: p95 482ms2026-10-05 UTC: p95 634ms2026-10-06 UTC: p95 637ms2026-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 642ms
Sep 24Oct 8Oct 23
US-West
976msp95 · 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-09-24 UTC: p95 583ms2026-09-25 UTC: p95 559ms2026-09-26 UTC: p95 593ms2026-09-27 UTC: p95 529ms2026-09-28 UTC: p95 494ms2026-09-29 UTC: p95 368ms2026-09-30 UTC: p95 370ms2026-10-01 UTC: p95 421ms2026-10-02 UTC: p95 404ms2026-10-03 UTC: p95 422ms2026-10-04 UTC: p95 472ms2026-10-05 UTC: p95 635ms2026-10-06 UTC: p95 547ms2026-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 976ms
Sep 24Oct 8Oct 23
Europe
365msp95 · 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-09-24 UTC: p95 445ms2026-09-25 UTC: p95 459ms2026-09-26 UTC: p95 452ms2026-09-27 UTC: p95 447ms2026-09-28 UTC: p95 659ms2026-09-29 UTC: p95 842ms2026-09-30 UTC: p95 816ms2026-10-01 UTC: p95 658ms2026-10-02 UTC: p95 313ms2026-10-03 UTC: p95 306ms2026-10-04 UTC: p95 263ms2026-10-05 UTC: p95 270ms2026-10-06 UTC: p95 216ms2026-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 365ms
Sep 24Oct 8Oct 23
Asia-Pacific
1.3sp95 · 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-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 973ms2026-09-26 UTC: p95 803ms2026-09-27 UTC: p95 962ms2026-09-28 UTC: p95 831ms2026-09-29 UTC: p95 775ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 719ms2026-10-02 UTC: p95 739ms2026-10-03 UTC: p95 587ms2026-10-04 UTC: p95 634ms2026-10-05 UTC: p95 871ms2026-10-06 UTC: p95 1.2s2026-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.3s
Sep 24Oct 8Oct 23
US-Central
266msp95 · 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-09-24 UTC: p95 460ms2026-09-25 UTC: p95 448ms2026-09-26 UTC: p95 311ms2026-09-27 UTC: p95 285ms2026-09-28 UTC: p95 297ms2026-09-29 UTC: p95 374ms2026-09-30 UTC: p95 312ms2026-10-01 UTC: p95 384ms2026-10-02 UTC: p95 227ms2026-10-03 UTC: p95 303ms2026-10-04 UTC: p95 331ms2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 427ms2026-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 266ms
Sep 24Oct 8Oct 23
Canada
1.4sp95 · 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-09-24 UTC: p95 825ms2026-09-25 UTC: p95 758ms2026-09-26 UTC: p95 695ms2026-09-27 UTC: p95 672ms2026-09-28 UTC: p95 669ms2026-09-29 UTC: p95 547ms2026-09-30 UTC: p95 533ms2026-10-01 UTC: p95 793ms2026-10-02 UTC: p95 931ms2026-10-03 UTC: p95 924ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 961ms2026-10-06 UTC: p95 846ms2026-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.4s
Sep 24Oct 8Oct 23
UK
537msp95 · 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-09-24 UTC: p95 396ms2026-09-25 UTC: p95 275ms2026-09-26 UTC: p95 569ms2026-09-27 UTC: p95 483ms2026-09-28 UTC: p95 491ms2026-09-29 UTC: p95 435ms2026-09-30 UTC: p95 424ms2026-10-01 UTC: p95 863ms2026-10-02 UTC: p95 434ms2026-10-03 UTC: p95 464ms2026-10-04 UTC: p95 428ms2026-10-05 UTC: p95 443ms2026-10-06 UTC: p95 446ms2026-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 537ms
Sep 24Oct 8Oct 23
Southeast Asia
1.1sp95 · 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-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 915ms2026-10-01 UTC: p95 1s2026-10-02 UTC: p95 912ms2026-10-03 UTC: p95 966ms2026-10-04 UTC: p95 865ms2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.1s2026-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.1s
Sep 24Oct 8Oct 23
Australia
296msp95 · 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-09-24 UTC: p95 737ms2026-09-25 UTC: p95 692ms2026-09-26 UTC: p95 980ms2026-09-27 UTC: p95 879ms2026-09-28 UTC: p95 683ms2026-09-29 UTC: p95 768ms2026-09-30 UTC: p95 607ms2026-10-01 UTC: p95 613ms2026-10-02 UTC: p95 694ms2026-10-03 UTC: p95 614ms2026-10-04 UTC: p95 643ms2026-10-05 UTC: p95 738ms2026-10-06 UTC: p95 664ms2026-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 296ms
Sep 24Oct 8Oct 23
South America
2.7sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 901ms2026-10-05 UTC: p95 899ms2026-10-06 UTC: p95 1.1s2026-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.7s
Sep 24Oct 8Oct 23

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.

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: 1165msstatus code: 200checked: Oct 23, 2026, 12:34 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
      Checks passinglatency: 927msstatus code: 200checked: Oct 23, 2026, 12:37 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.
    • US-Central
      Checks passinglatency: 138msstatus code: 200checked: Oct 23, 2026, 12:29 AM 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: 854msstatus code: 200checked: Oct 23, 2026, 12:38 AM 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: 864msstatus code: 200checked: Oct 23, 2026, 12:33 AM 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: 270msstatus code: 200checked: Oct 23, 2026, 12:30 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.
    • UK
      Checks passinglatency: 565msstatus code: 200checked: Oct 23, 2026, 12:24 AM 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: 1282msstatus code: 200checked: Oct 23, 2026, 12:39 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.
    • Southeast Asia
      Checks passinglatency: 851msstatus code: 200checked: Oct 23, 2026, 12:21 AM 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: 819msstatus code: 200checked: Oct 23, 2026, 12:23 AM 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

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>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

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.