Fastly help and reporting
Customer support needs the CDN service and affected customer hostname.
Live Domain Check
Is Fastly Down? Check fastly.com Status and Outages
Run a live reachability check for fastly.com. Compare the regional responses with the problem you see in Fastly.
Find Fastly help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked-
Verdict-
Response Time-
Final URL-
Regional checks
Understanding Fastly connection and service problems
A Fastly company-site response does not test a customer's CDN service or origin.
The checker above requests fastly.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Fastly action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse infrastructure checks.
Fastly status information and official help
Open fastly.com
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Where to report problems with Fastly
Open Fastly help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Details to include in your report
Service/hostname, request reference, client location, status and UTC time with internal details redacted.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Fastly.
What to check when Fastly is not working
These are troubleshooting comparisons, not claims that Fastly is currently experiencing a particular incident.
Start with the action that failed
Capture the failing customer hostname, URL and response headers and compare a second public path.
Narrow down the affected service
An authorised operator should compare edge and origin evidence with the relevant Fastly service incident.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Fastly is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the fastly.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open Fastly help and use its guidance or announcements for the exact feature. Do not treat a general homepage as an outage bulletin.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If Fastly Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Fastly seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open fastly.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Fastly issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Fastly support.
Frequently asked questions about Fastly problems
Is Fastly down, or is the problem limited to one feature?
Run the fastly.com check and compare its original timestamps and responses with your actual error. A Fastly company-site response does not test a customer's CDN service or origin.
Where can I report a problem with Fastly?
Use the official help/reporting resource linked above. Customer support needs the CDN service and affected customer hostname.
What should I check first when Fastly is not working?
Capture the failing customer hostname, URL and response headers and compare a second public path. An authorised operator should compare edge and origin evidence with the relevant Fastly service incident.
What information helps Fastly support investigate?
Service/hostname, request reference, client location, status and UTC time with internal details redacted.