2024-02-13 09:51 UTC
An issue has been found and is currently under investigation.
2024-02-14 16:33 UTC
A solution has been fully rolled out and on-call teams have verified that the impact is resolved.
No further updates are expected.
2024-02-14 05:47 UTC Fix has been deployed to all EU regions and US East. Asia Pacific and US West are scheduled to be completed by 21:00. A final update will be issued when this is complete.
2024-02-14 00:47 UTC Final testing is complete and the fix is being deployed to all production regions over the next few hours. An update will be issued when this is complete.
2024-02-13 20:37 UTC A fix has been identified and making its way to pre-production for final testing. An update will be issued when that is complete.
2024-02-13 18:25 UTC
The issue is limited to a small sub-set of customers. A workaround has been identified and is being tested. A further update will be issued in 2 hours
2024-02-13 16:26 UTC
On-call teams continue working on a solution.
Next update in 2 hours
2024-02-13 15:29 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 13:15 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 12:15 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 11:25 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 11:03 UTC
On-call teams have identified the issue and are working on a solution.
Next update in 20 mins
2024-02-13 10:44 UTC On-call teams are continuing to investigate the issue.
Next update in 20 mins
Status