Resolved -
This incident has been resolved.
Oct 31, 08:49 PDT
Monitoring -
A hotfix has been applied to address the issue and we are actively monitoring to ensure everything remains stable.
Oct 30, 21:16 PDT
Update -
We’re continue to test a fix in our internal environments. Once it’s validated, we’ll begin rolling it out to all customer clusters. Thank you for your patience while we work to resolve this issue.
Oct 30, 19:07 PDT
Update -
We’re currently testing a fix in our internal environments. Once it’s validated, we’ll begin rolling it out to all customer clusters. Thank you for your patience while we work to resolve this issue.
Oct 30, 17:25 PDT
Update -
Deployments and validation continue. Will provide an update once we are deploying to customer clusters.
Oct 30, 16:06 PDT
Update -
We continue to deploy and validate to internal and pre-production environments. Will provide an update once we are deploying to customer clusters.
Oct 30, 15:06 PDT
Update -
We are deploying and validating a fix in our internal environments at this time. After validation we will begin rolling out to all of our customer clusters. We apologize for the inconvenience and appreciate your patience while we address this matter.
Oct 30, 14:03 PDT
Identified -
We have identified the root cause of the issue impacting reference table creation. Our engineering team is actively working on a resolution and will deploy a fix as soon as possible. All clusters were affected. We apologize for the inconvenience and appreciate your patience while we address this matter.
Oct 30, 12:56 PDT
Investigating -
We're investigating a potential issue affecting newly created reference tables. Our team is validating the scope and identifying affected clusters. Updates will be posted here as soon as more information is available.
Oct 30, 11:44 PDT