[status] Monitoring: A workaround has been implemented on our side. The Chromium team is currently testing their fix together with our CDN provider. We are monitoring the situation, and everything should remain fully operational even … https://t.co/uJb08Hh1KU
[status] Identified: A recent Chrome update (version 145) introduced an issue that may lead to occasional CORS errors and HTTP 425 responses when making Delivery API calls. Our CDN provider and the Chromium team are already investigat… https://t.co/9dgiA0oYid
[status] Identified: There is currently a delay in the appearance of assets when accessing an asset's preview URL due to our preview storage being overloaded in the U.S. data center. Accessing the published version of an asset still f… https://t.co/3go4uQdszg
[status] Resolved: Delays accessing assets by preview URL have resolved. Accessing both published and preview versions of assets is functioning normally. https://t.co/rZxg6cu6jL
[status] Identified: There is currently a delay in the appearance of assets when accessing an asset's preview URL due to our preview storage being overloaded in the U.S. data center. Accessing the published version of an asset still f… https://t.co/qsFHwm8PIr
[status] Resolved: This incident has been resolved. Ultimately, the issue stemmed from an error that prevented entities from being deleted in a given database table. All of the failed deletion's were manually cleared, and now cache pu… https://t.co/ilRV9WArjY
[status] Investigating: We are experiencing a problem in which the Fastly API isn't purging outdated content in the US and EU regions. We are currently investigating the issue and will provide updates as soon as possible. https://t.co/VYrA5Y3aUk
[status] Monitoring: Our integrated chat tool is currently experiencing a full outage:
https://t.co/uooe8YyddJ
If you're in need of technical support, please reach out to our Support team using the following email: [email protected]. https://t.co/7Id4Xqhvrf
[status] Identified: Our Learn portal is currently experiencing slower loading times. Our development team has identified the root cause and is actively working on a fix. https://t.co/pVDtZ68dsN
[status] Investigating: The UI of https://t.co/wQ2PuSdWK7 doesn't load properly due to internal api problems. We are investigating the issue at the moment. All public APIs (Delivery API, GraphQL, Management API) work properly. https://t.co/7OgggM2ri3
[status] Monitoring: The server was restored, and everything seems to be up and working as usual. We keep monitoring all the services for any issues. https://t.co/lXVa9VizzD