Where does this status come from?

From Fastly's own incident feed at https://www.fastlystatus.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Fastly's words.

How can my agent or app check Fastly status?

Fetch https://upbutler.com/status/fastly/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"fastly"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Fastly's?

Add "fastly" to the dependencies of your UpButler workspace. When one of your monitors fails while Fastly has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Fastly down?

Right now

No. Fastly is operational.

No incidents reported.

Read from www.fastlystatus.com 5 min ago · every 300s

For agents

proceed

Proceed.

GET upbutler.com/status/fastly/status.agent.json

MCP: upstream_status {"service":"fastly"}

CDN and edge compute. A Fastly incident can take down sites that never chose it, through a provider that did.

What Fastly reports

Operational

Taken as is from Fastly's own incident feed. Incident titles and component names below are theirs.

Open www.fastlystatus.com

UpButler's independent probe

There is no keyless endpoint of Fastly that says anything useful, so UpButler does not probe it. To check your own Fastly account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Fastly

Data Center Capacity Expansion for Toronto (YYZ)scheduled maintenance
Starts 2026-10-15 04:00 UTC
Fastly will be adding capacity at our Toronto (YYZ) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 15 October 2026 at 04:00 UTC. Our estimated duration is 1d. When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses ( https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges ). Customer…

Text written by Fastly, shown unchanged.

Fastly incidents, last 90 days

13 finished incidents seen since UpButler started tracking on 2026-10-10. A typical one lasted under a minute; the longest under a minute.

Started (UTC)	Incident	Impact	Lasted
2026-10-10 03:57	Retrospective: Impacted Performance in Cape Town (CPT)	minor	under a minute
2026-10-10 03:12	Retrospective: Impacted Performance in Cape Town (CPT)	minor	under a minute
2026-10-09 23:30	Sambalpur (QAK) Rerouted Traffic	minor	under a minute
2026-10-07 22:08	Sambalpur (QAK) Rerouted Traffic	minor	under a minute
2026-10-07 22:05	Delhi (QAG) Rerouted Traffic	minor	under a minute
2026-10-06 00:47	Elevated Errors for API & Configuration Management	minor	under a minute
2026-10-06 00:44	Elevated Errors for API & Configuration Management	minor	under a minute
2026-10-06 00:42	Elevated Errors for API & Configuration Management	minor	under a minute
2026-10-06 00:12	Elevated Errors for API & Configuration Management	minor	under a minute
2026-10-01 14:17	Elevated Errors for Object Storage	minor	under a minute
2026-10-01 13:45	Elevated Errors for Object Storage	minor	under a minute
2026-10-01 07:55	Elevated Errors for Object Storage	minor	under a minute
2026-09-30 23:00	Elevated Errors for Object Storage	minor	under a minute

Tell your outage from Fastly's

Declare that your project depends on Fastly. When one of your monitors fails while Fastly has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - fastly

Ask before you retry

curl -s https://upbutler.com/status/fastly/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "fastly",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Fastly down right now?: No. As of 2026-10-10 05:08 UTC, Fastly is operational. This page reads the status again every 5 minutes.
Where does this status come from?: From Fastly's own incident feed at https://www.fastlystatus.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Fastly's words.
How can my agent or app check Fastly status?: Fetch https://upbutler.com/status/fastly/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"fastly"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Fastly's?: Add "fastly" to the dependencies of your UpButler workspace. When one of your monitors fails while Fastly has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in cloud and edge

UpButler is not affiliated with Fastly. Status and incident text belong to Fastly and are read from their public status source; the probe result is UpButler's own measurement.