Fastly · Maintenance
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Fastly status

Fastly · Statuscast
Maintenance
StatusCast reports 0 unresolved incident(s), 2 maintenance window(s), and 221 leaf components.
Edge cloud services
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

No active incidents were included in this vendor report.

Maintenance

Changes to Fastly IP Address Space

On October 13, 2026, at 00:00 UTC, Fastly will publish additional public IP address ranges to our Public IP List API endpoint. To prepare for future use, we recommend updating your IP prefix lists as soon as possible. The following IP block(s) will be added to our range list: IPv4: 90.98.0.0/17 , 90.98.128.0/18 IPv6: 2a04:4e42::/31 (expanded from 2a04:4e42::/32 ), 2a04:4e44::/32 The deployment of these new prefixes for active use is scheduled for January 11, 2027, at 00:00 UTC, and all currently published IP prefixes will remain unchanged. Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated Customer Success team members.

Status InProgress Starts Updated

Data Center Capacity Expansion for Marseille (MRS)

Fastly will be adding capacity at our Marseille (MRS) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 21 September 2026 at 21:30 UTC. Our estimated duration is 6h. 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 ). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com .

Status Future Starts Updated

Component health

Reported
221
Retained
100
Affected retained
18
Projection scope: complete · 100 retained of 221 reported components across 30 source groups · bounded/truncated source projection.
www.fastlystatus.com Group: Fastly Web Pages Maintenance
https://fiddle.fastly.dev Group: Fastly Web Pages Maintenance
https://www.fastly.com/ Group: Fastly Web Pages Maintenance
https://docs.fastly.com/ Group: Fastly Web Pages Maintenance
https://developer.fastly.com Group: Fastly Web Pages Maintenance
Chatbot Feature Group: https://support.fastly.com Maintenance
New Support Case Group: https://support.fastly.com Maintenance
Support Ticketing System Group: Support Systems Maintenance
Support Phone System Group: Support Systems Maintenance
General Updates Group: Customer Services Maintenance
API Services Group: API & Configuration Management Maintenance
Configuration Management Services Group: API & Configuration Management Maintenance
AI Assistant Group: Fastly Control Panel Maintenance
Notification Center Group: Fastly Control Panel Maintenance
Edge Ecosystem Group: Fastly Maintenance
Fastly Public IPs Group: Fastly Maintenance
Global POP Network (SEV1/0) Group: Fastly Maintenance
Third Party Service Provider Group: Fastly Maintenance
TLS Encryption Group: Domain Management Operational
Origin Connect Group: Domain Management Operational
Showing 20 of 100 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Maintenance
HTTP 200 · 283.99 ms feed latency
Maintenance
HTTP 200 · 492.9 ms feed latency
Maintenance
HTTP 200 · 267.2 ms feed latency
Maintenance
HTTP 200 · 305.58 ms feed latency
Maintenance
HTTP 200 · 391.43 ms feed latency
Maintenance
HTTP 200 · 346.04 ms feed latency
Maintenance
HTTP 200 · 362.14 ms feed latency
Maintenance
HTTP 200 · 524.15 ms feed latency
Maintenance
HTTP 200 · 490.68 ms feed latency
Maintenance
HTTP 200 · 363.69 ms feed latency

Collection details

Provider adapter
Statuscast
Feed response
HTTP 200
Feed latency
346.22 ms