WixRESOLVED: Some Users Have Issues with Saving/Publishing Sites
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
Issue resolved 21:10.
Resolved
This incident has been resolved.
Resolved
We experienced an outage affecting Greenhouse silo 7, 9 and anz. Our team investigated the issue and restored full functionality within 8 minutes.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
On May 6, 2026 between 11:02 UTC and 11:13 UTC, users were unable to start or view Copilot Cloud Agent or remote sessions. During this time, requests to the session API returned errors, preventing users from creating new sessions or viewing existing ones. The issue was caused by a configuration change to the service's network routing that inadvertently removed the ingress path for the service. The team reverted the change at 11:13 UTC which restored service. The incident remained open until 11:59 UTC while the team verified full recovery. We are taking steps to improve our deployment validation process to prevent similar configuration changes from impacting production traffic in the future.
Resolved
Following continued monitoring by our engineers, Agent Console auto models have remained stable. This incident is now resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue causing incorrect “High Error Ratio” notifications has been resolved. Impact Some users received an email titled “High Error Ratio” indicating their Zap would be switched off. In certain cases, this did not reflect actual Zap performance, and some Zaps may have been paused incorrectly as a result. Resolution We implemented a fix and confirmed that notifications and Zap status are now behaving as expected. If you are still experiencing this issue causing your Zaps to turn off, you can reach out to our team at: https://zapier.com/app/get-help.
Resolved
We resolved the underlying issue. A distributed cache roll out for ClickHouse caused the latency and error spikes. The roll out was reverted and we see normal API performance as of now.
Resolved
We identified an issue with Claude's desktop and web connections to Coda MCP. The issue has been resolved, and you should now be able to set up connections. If you set up any connections before May 4, you may need to reconnect the Coda MCP in Claude. Find more instructions here: https://help.coda.io/hc/en-us/articles/44722661982989.
Resolved
We'll continue monitoring
Resolved
From 10:04 - 13:38 UTC, we experienced issues with elevated authentication errors affecting some Dashboard features. This is now resolved.
Resolved
This incident has been resolved. If you are still experiencing an issue, please let us know in our Etsy Forums (https://community.etsy.com/t5/Technical-Issues/bd-p/bugs).
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
Our Engineers deployed a fix, and we're no longer observing delays affecting the Issues API data freshness. The Snyk Incident Response has been stood down.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. Logged-out users who open a Notion page link should be prompted to the login page correctly.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The maintenance is complete.
Resolved
Everything is back to normal, and the incident is now resolved. We are planning long-term mitigations to prevent this issue from recurring, and we will share the results of our investigation with all affected customers.
Resolved
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC0156355](https://community.snowflake.com/s/article/INC0156355)
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Our team has confirmed that since 21:14 UTC all customers logging into Zapier via Google SSO can do so successfully. If you are still running into any issues, please contact our support team for assistance: https://zapier.com/app/get-help
Resolved
This incident has been resolved. If you are still experiencing an issue, please let us know in our Etsy Forums (https://community.etsy.com/t5/Technical-Issues/bd-p/bugs).
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We've applied our fix and confirmed this is no longer occurring. We will now mark this as resolved. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22008
Resolved
This incident has been resolved.
Resolved
We're all set! PandaDoc is working properly and the incident has been fully resolved. If you continue to experience issues with this, please contact our Support team (https://support.pandadoc.com/en/articles/9715061-how-to-contact-pandadoc-support).
Resolved
This incident has been resolved. All services are operating normally.
Resolved
Some Pulumi Cloud organizations experienced elevated errors when decrypting ESC environments. A subset of environment revisions were affected, and those revisions failed to decrypt 100% of the time during the window. Overall, 3.32% of decrypt-attempt requests across Pulumi Cloud failed due to this issue. At the start of the window, we rolled out a change that prevented secret ciphertext copied from an ESC environment from being decrypted in other environments. Customers who had previously copied ciphertext between environments were affected. Users saw a message: “decryption failed. If this secret's ciphertext was copied from a different environment, copy and paste the plaintext instead.” This change was intended as a security improvement, but the customer impact was higher than expected, so the change was rolled back. The ESC team has conducted an internal postmortem to understand the misjudged customer impact, improve our responsiveness to scenarios like this, and created a plan to launch this security improvement without customer disruption.
Resolved