500 status for Content Delivery API
Incident report for DatoCMS
Resolved The incident has been resolved.
Posted at Jun 8, 13:29 GMT+02:00
Monitoring We've removed Fastly altogheter and put plan B into action: tripled the resources and fallback to custom cache on Redis. We're back online and running again. We are monitoring requests to see how they progress over time.
Posted at Jun 8, 13:04 GMT+02:00
Monitoring Posted at Jun 8, 13:00 GMT+02:00
Investigating We're investigating the cause, seems to be related to Fastly (their status page and homepage are currently down).
Posted at Jun 8, 11:55 GMT+02:00