- Normal
- Informational
- Maintenance
- Degraded
- Unavailable
- Investigating
- Identified
- MonitoringFanout Control Panel
Our engineers detected an unplanned event that contained impact to our Compute service.
This event is resolved, and there is no remaining impact.
Customers may have experienced delays in change requests to configurations on Compute from 17:29 to 17:46 UTC. (~17min duration)
All other Compute requests remain unaffected during the impact duration.
Please engage with our Support team through https://support.fastly.com if you have any questions and/or concerns.
Fastly engineers are currently investigating into intermittent WebSocket Connections. Customers attempting to connect to WebSocket services may experience intermittent periods of elevated errors.
All other Fastly products and services are unaffected.
Our engineers have identified the issue and are applying a fix to WebSocket Connection services.
All other Fastly products and services are unaffected.
Engineering has deployed a fix and have confirmed a gradual recovery for WebSocket Connection services. We will continue to monitor until we’ve confirmed that the service has been fully restored.
All other Fastly products and services remain unaffected by this incident.
Engineering has confirmed that WebSocket Connection services has been fully restored. Customers may have experienced intermittent periods of elevated errors from the 6th of March 10:00 to the 9th of March 04:49 UTC.
This incident is resolved.
Upcoming maintenance affecting Fanout Metrics.
Customers of Fanout may experience inaccuracies with the HTTP connections metric. HTTP Connections may be undercounted by 1 minute per connection (this would only affect Fanout, not Websockets).
The scheduled maintenance has been completed.
Fastly engineers are currently investigating into intermittent Fanout and WebSocket Connections. Customers attempting to connect to Fanout and WebSocket services may experience elevated errors.
All other Fastly products and services are unaffected.
This issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.