Dec 17, 23:01 PST
Resolved – This incident has been resolved.
Dec 17, 01:25 PST
Investigating – We are currently investigating this issue
Day: December 17, 2024
Snowflake – Azure – East US 2 (Virginia): INC0122743
Dec 17, 17:13 PST
Resolved – Current status: We’ve implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community.
Customer experience: Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features.
Incident start time: 14:00 UTC December 17, 2024
Incident end time: 23:42 UTC December 17, 2024
Preliminary root cause: The current root cause investigation is focused on a recent load balancer change that manages transaction IDs in order to minimize conflicts within the metadata database.
A root cause analysis (RCA) document will be published within seven business days.
Dec 17, 16:31 PST
Monitoring – Current status: We’ve implemented the fix for this issue, and we’ll continue to monitor the environment until we’re confident all services are functioning properly.
Customer experience: Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features.
Incident start time: 14:00 UTC December 17, 2024
Incident end time: 23:42 UTC December 17, 2024
Preliminary root cause: The current root cause investigation is focused on a recent load balancer change that manages transaction IDs in order to minimize conflicts within the metadata database.
Dec 17, 15:43 PST
Update – Current status: We’re continuing to investigate the issue with Snowflake Data Cloud. The current investigation is focused on a recent load balancer change that manages transaction IDs in order to minimize conflicts within the metadata database. We’ll provide another update within 60 minutes.
Customer experience: Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features.
Incident start time: 14:00 UTC December 17, 2024
Dec 17, 14:42 PST
Update – Current status: We’re continuing to investigate the issue with Snowflake Data Cloud. We’ll provide another update within 60 minutes.
Customer experience: Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features.
Incident start time: 14:00 UTC December 17, 2024
Dec 17, 13:50 PST
Update – Current status: We’re continuing to investigate the issue with Snowflake Data Cloud. We’ll provide another update within 60 minutes.
Customer experience: Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features.
Incident start time: 14:00 UTC December 17, 2024
Dec 17, 13:03 PST
Investigating – Current status: We’re investigating an issue with Snowflake Data Cloud. We’ll provide an update within 60 minutes.
Customer experience: Customers hosted in the specified regions may intermittently experience delays or failures while attempting to use various Snowflake services and features.
Incident start time: 14:00 UTC December 17, 2024
OpenAI – Degraded Performance in ChatGPT Advanced Voice Mode
Dec 17, 15:23 PST
Resolved – Between 12:37 PM and 03:17 PM PST some users experienced degraded performance on Advanced Voice Mode. The impact was that these conversations were not appearing in the conversation history. We have now mitigated the issue and recovered.
Dec 17, 14:44 PST
Update – We’re continuing to investigate the issue. Users can still have conversations in Advanced Voice Mode, but they will not appear in the conversation history when returning. We’ll provide updates as soon as we have more information.
Dec 17, 13:30 PST
Update – We are still investigating this issue.
Dec 17, 12:37 PST
Investigating – We are currently experiencing degraded performance of ChatGPT Advanced Voice. Some of the conversation transcripts might not show up in the conversation history.
Anthropic – Unauthorized post from @AnthropicAI X.com account
Dec 17, 13:16 PST
Resolved – We have identified and addressed the root cause of unauthorized posts on @AnthropicAI, our official X account. No Anthropic systems or services were affected in this incident.
Dec 17, 09:08 PST
Monitoring – We have regained secure access to the @AnthropicAI account and will be continuing our investigation, with the support of X, into how these unauthorized posts were made.
Dec 17, 08:43 PST
Identified – We are aware of a second unauthorized post on @AnthropicAI on X.com, and are continuing to work to regain access to the impacted account. There are no impacts to other Anthropic services.
Dec 17, 08:04 PST
Investigating – We are aware of an unauthorized post originating from our official X.com account, @AnthropicAI. At this time the post has been removed, and we are investigating the issue.
Zapier – Stripe Auth Expiration and Reconnection Errors
Dec 17, 11:38 PST
Resolved – This incident has been resolved.
On Dec 16th at 4:27 PM UTC, Stripe connections began failing, and attempts to reconnect returned the following error:
‘Invalid auth connection’
Our team implemented a fix at 5:30 PM UTC on the same day.
Due to these authentication errors, some Zaps using a Stripe trigger were turned off. As of 9:30 PM UTC on Dec 16th, our team unpaused these Zaps. During the downtime, we continued to receive hooks for paused Zaps, and any failed Zap runs were replayed by our team as of Dec 17th at 6:01 PM UTC. No data was lost.
We appreciate your patience during this incident and sincerely apologize for any inconvenience caused. If you have any further questions, please don’t hesitate to reach out to our support team here: https://zapier.com/app/get-help.
Dec 16, 10:48 PST
Monitoring – We are currently looking into an issue where users experienced errors when trying to establish a connection with Stripe. The specific error message was ‘Invalid auth connection.’
We are pleased to report that we have implemented a fix and users should now be able to reconnect/enable any Zaps using Stripe without encountering the earlier problem.
If any further issues arise or you do have questions, please do not hesitate to contact our dedicated Support Team, which can be reached via this link: https://zapier.com/app/get-help
We do apologize for any inconvenience that this may have caused and appreciate your understanding as we worked to resolve the issue. We will continue to monitor the situation closely.
Dec 16, 09:00 PST
Investigating – We’re currently investigating an issue where Stripe auths are expiring, and attempts to reconnect return the following error:
‘Invalid auth connection.’
We’ll update this page with more information as it becomes available. If you have any questions, please contact our support team at https://zapier.com/app/get-help.