WarpDegraded API reliability
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
All VPS servers and websites hosted in our BR-CAM datacenter in Brazil are back online and reachable. We are sorry for the disruption and thank you for your patience.
Resolved
The issue has been resolved.
Resolved
The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to Viaero network subscribers in the United States is operating normally.
Resolved
The incident has been resolved and MMS delivery from a subset of Twilio Long Codes to Viaero network subscribers in the United States is operating normally.
Resolved
All impacted services have now fully recovered.
Resolved
Users are able to access their private apps again.
Resolved
The Ask AI functionality in Clerk docs has been restored.
Resolved
This issue has been resolved. AT&T provisioning is now flowing normally.
Resolved
Today we released tfc-agent 1.33.3 to address the root cause of the failures we saw yesterday. A recent security patch to libcurl exposed a bug in the version of git we ship in the tfc-agent image. This causes some VCS setups to fail when the VCS provider issues an HTTP redirect. We've patched the bug in git. If you are using remote runs, you don't have to do anything, you're already on 1.33.3. If you downgraded to 1.33.1 to work around git-based VCS problems, you can safely upgrade to 1.33.3 now. Please contact support if you experience any further issues.
Resolved
This issue was mitigated 10/22 at 3:16 PM EDT
Resolved
This issue is considered resolved.
Resolved
This incident has been resolved.
Resolved
Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. We're continuing our deployment of a secondary fix to restore the remaining task graph run history for the affected time period. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the affected region may have experienced intermittent issues with scheduled or manual tasks. Most tasks completed as expected, but some may have been marked as failed even though they ran successfully. A small number of tasks may have remained in a pending state or failed to start. Affected users may have seen an error message, such as "Unexpected exception during task dispatch." After the primary mitigation, the next time each task ran, it may still have been marked as failed with an internal error message even though its query ran successfully. This may have happened up to one additional time per task. While the functional impact regarding task failures or tasks silently succeeding is resolved, affected customers may still see incomplete task graph run history. Specifically: - When customers open or refresh the Task Graphs tab on the Tasks page in Snowsight (Transformation » Tasks), or the Run History tab for individual tasks, they may not see task runs from before 10:58 UTC October 13, 2026. Some task runs from after that time may not appear. - The INFORMATION_SCHEMA.COMPLETE_TASK_GRAPHS function may not include some recently completed runs. - The INFORMATION_SCHEMA.CURRENT_TASK_GRAPHS function may show extra rows for previously scheduled runs that are no longer running. - The SNOWFLAKE.ACCOUNT_USAGE.COMPLETE_TASK_GRAPHS view will continue to show history from before 10:58 UTC October 13, 2026, but some runs after that time may not appear. Incident start time: 10:58 UTC October 13, 2026 Incident end time: 17:35 UTC October 15, 2026 Preliminary root cause: Our investigation identified a metadata mismatch within the metadata database layer. As a result, some tasks were reported as failed even though they completed successfully, while others remained pending or failed to start. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.
Resolved
The incident has been resolved and SMS delivery from Twilio to Surf Telecom network subscribers in Brazil is operating normally.
Resolved
The incident has been resolved and SMS delivery from Twilio to Surf Telecom network subscribers in Brazil is operating normally.
Resolved
The incident has been resolved and SMS delivery from a subset of Twilio Short Codes to Liberty Mobile network subscribers in Puerto Rico is operating normally.
Resolved
The incident has been resolved and SMS delivery from a subset of Twilio Short Codes to Liberty Mobile network subscribers in Puerto Rico is operating normally.
Resolved
The incident has been resolved and SMS delivery receipts from Twilio to network subscribers on affected networks in the United States and Canada are operating normally.
Resolved
The incident has been resolved and SMS delivery receipts from Twilio to network subscribers on affected networks in the United States and Canada are operating normally.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved and SMS delivery between a subset of Twilio Phone Numbers and network subscribers on affected networks in Brazil is operating normally.
Resolved
The incident has been resolved and SMS delivery between a subset of Twilio Phone Numbers and network subscribers on affected networks in Brazil is operating normally.
Resolved
Between 11:28 AM EDT (UTC -04:00) and 2:43 PM EDT (UTC -04:00), many customers in North America experienced issues accessing HubSpot.com and various tools. This was caused by underlying network connectivity issues. As of 2:43 PM EDT (UTC -04:00), the networking issue has been addressed and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.
Resolved
SLO processing has fully recovered. All services are now functional.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The incident has been resolved and SMS delivery from Twilio to Telecall network subscribers in Brazil is operating normally.
Resolved
The incident has been resolved and SMS delivery from Twilio to Telecall network subscribers in Brazil is operating normally.
Resolved
RESOLVED: PHP CVE-2026-115560 mitigation Pantheon is aware of the release of CVE-2026-115560 from PHP.net; the recommended remediations for this vulnerability were already in place prior to the announcement. No action is required.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue causing delays in Logs and Observability data has been resolved.
Resolved
We have resolved the issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial degradation to the web UI and Git operations.
Resolved
This incident has been resolved.
Resolved
This is now resolved. Errors and latency were elevated between 15:21 and 15:50 UTC primarily for requests served by MIA and ATL with some impact on the US east coast and northern South America.
Resolved
This incident has been resolved and the affected service has been restored.
Resolved
Current status: We've monitored the environment and confirmed that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified regions may have experienced intermittent delays when loading Snowsight or running queries, and some queries may have failed. Workaround: There were no available workarounds for this issue. Incident start time: 23:50 UTC October 15, 2026 Incident end time: 00:40 UTC October 16, 2026 Preliminary root cause: A routine software update caused a large number of background setup operations to run at the same time, which exhausted the resources of a subset of infrastructure responsible for processing queries in the affected region, resulting in intermittent delays and query failures. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.
Resolved