Is Fastly Down? Current Status, Outage Reports & User Feedback
Operational Last checked: 6 minutes ago
User Reports (Last 12 Hours)
Quick Actions
Incident History
Resolved Incidents
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
We have detected a potential outage for Fastly.
Started:
Resolved:
Frequently Asked Questions
503 errors typically indicate that your origin server is unavailable or responding too slowly to Fastly's requests. Check your origin server's health and capacity, verify Fastly's health check configuration for your service, and examine your origin's error logs for specific failure reasons.
Caching issues can result from cache configuration, origin headers, or service disruptions. Verify your cache settings and TTLs are correctly configured, check if your origin is sending appropriate cache headers, and examine Fastly's cache hit ratio metrics to identify problem content.
Performance issues may be caused by origin response times, configuration optimization, or regional service disruptions. Check your origin server's response times, verify you're using appropriate shielding and caching configurations, and examine if performance varies by geographic location.
Access issues can stem from authentication problems, account status, or service disruptions. Verify your login credentials or API tokens are valid, check if your account has any restrictions, and try accessing through a different browser or network connection.
Propagation issues may be caused by activation failures, configuration errors, or service disruptions. Verify your configuration changes have been properly activated, check for any validation errors in your VCL, and be aware that some changes may take a few minutes to propagate globally.
502 errors indicate that Fastly received an invalid response from your origin server. Check your origin server for errors or malformed responses, verify connectivity between Fastly and your origin, and examine your server logs for specific error information during the time of the failures.
Logging issues can result from configuration problems, destination availability, or service disruptions. Verify your logging configuration is correct, check if your log destination is accessible and has sufficient capacity, and examine any error messages in your Fastly account related to log delivery.
SSL/TLS issues may be caused by certificate expiration, configuration problems, or service disruptions. Verify your certificates are valid and not expired, check your TLS configuration in the Fastly control panel, and ensure your certificate covers all domains being served through Fastly.
About Fastly
Fastly is a content delivery network (CDN) and edge cloud platform that accelerates web and application delivery by distributing content closer to users through a global network of points of presence. The service provides edge computing capabilities, image optimization, video streaming, security features, and load balancing, enabling organizations to deliver faster, more secure digital experiences while reducing origin server load through intelligent caching and request handling at the edge.
Website operators use Fastly to accelerate content delivery and reduce server costs, leveraging the platform's caching capabilities to serve static assets from edge locations closer to end users. E-commerce businesses implement Fastly to improve page load times and handle traffic spikes during promotional events or seasonal peaks. Media companies utilize Fastly's video streaming capabilities for delivering on-demand and live content with reduced buffering and startup times, while development teams leverage Fastly's programmable edge for creating custom logic that executes closer to users, reducing latency for dynamic content and API responses.
Users may experience various types of issues when using Fastly, including temporary cache inconsistencies after configuration changes, occasional propagation delays when updating security settings, or brief routing inefficiencies during network optimizations. API rate limiting might affect high-volume automated operations, while real-time statistics and logging might experience collection or display delays during exceptionally high traffic events. Custom Varnish Configuration Language (VCL) deployments could temporarily affect cache behavior until fully propagated across the network. During major internet infrastructure events, users might notice regional performance variations as traffic is automatically rerouted around affected areas. Configuration changes to purge rules or cache settings might require time to take full effect across all edge locations.