This incident has been fully resolved. Following the deployment of a fix to our servers, all v3 frontend services have been stable and performing normally. The monitoring period has now concluded with no further issues detected.
We sincerely apologize for the inconvenience caused during this incident and thank you for your patience.
Posted Jun 09, 2026 - 13:57 UTC
Monitoring
We have deployed the fix and it is taking effect. We are observing recovery across our frontend services and will continue to monitor the situation closely.
Posted Jun 09, 2026 - 12:09 UTC
Update
We have identified a possible root cause for the ongoing degraded performance on our frontend services and we have begun implementing a fix.
We are monitoring the situation closely and will share another update once the fix has been applied and verified.
Posted Jun 09, 2026 - 12:05 UTC
Update
Our investigation into the issue is still ongoing. We do not have a root cause or resolution to share yet, but our team remains fully focused on this.
We appreciate your patience and will provide another update.
Posted Jun 09, 2026 - 10:50 UTC
Update
We are continuing to investigate the ongoing issue. We have not yet identified a resolution, but are actively working on it and monitoring the situation closely.
We appreciate your patience and will provide another update.
Posted Jun 09, 2026 - 09:09 UTC
Identified
We have identified that the degraded performance on our frontend services is caused by issues with our CDN provider. We are actively investigating the root cause and working on a resolution.
We will provide a further update as soon as we have more information.
Posted Jun 09, 2026 - 07:38 UTC
Investigating
We are currently facing a degraded performance on our v3 frontend services. We are investigating this issue.