WixRESOLVED: Issues Affecting Multiple Wix Services
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
Resolved
The system has been restored to normal operational levels
Resolved
The system has been stable; we consider this incident to be over.
Resolved
Payouts are no longer impacted by settlement delays. Normal service has been restored. Impact start time: 22/07/2026, 08:18 BST Impact end time: 22/07/2026, 08:30 BST Client actions: None
Resolved
Between 03:18 UTC and 06:04 UTC on July 22, 2026, a subset of customers were unable to access app.circleci.com. The issue has been resolved and access has returned to normal. We thank you for your patience while our team worked on implementing a fix.
Resolved
Our team has resolved the issue impacting some partners when navigating Xero HQ. We apologise for any inconvenience this has caused.
Resolved
This has been resolved.
Resolved
We were aware of some customers receiving errors when accessing Expenses in Xero. A product release caused this feature to become temporarily unavailable. Our team has resolved the issue. We apologise for any inconvenience this has caused.
Resolved
Between 8:50pm and 9:10pm America/New_York on July 21st, there were availability blips during an upgrade of our nginx proxy layer. SDK clients will have retried during this event and we recovered from a backlog by 9:30pm.
Resolved
Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.
Resolved
Commerce Engineers identified and fixed the root cause of the intermittent errors affecting the control panel. This incident has been resolved.
Resolved
The fix has been deployed, and search functionality has been restored
Resolved
Image generation functionality has fully recovered, and error rates have returned to normal levels.
Resolved
We identified and fixed the issue. AuthKit SSO has fully recovered.
Resolved
This issue is now resolved.
Resolved
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates. <br /><br />The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.<br /><br />To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.
Resolved
This incident has been 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
SMS subscriptions, SMS sending, and the creation and scheduling of SMS and WhatsApp campaigns are operating as expected. This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident is now resolved.
Resolved
Webhook latency is back to normal levels. We have identified that this latency only affected a very small subset of customers.
Resolved
This issue is now resolved.
Resolved
This incident has been resolved.
Resolved
All affected API Platform functionality has now fully recovered.
Resolved
Impact: Customers were not able to update their docs Root Cause: Updates failed due to a hitting a rate limit on Github Time Range: 4:40 AM - 8:00 AM PST
Resolved
Some Apps are failing during the publishing step. Existing Published Apps are unaffected.
Resolved
Some customers in North America experienced issues with Content previews. This was caused by hubspotpreview-na2.com being blocked by some internet providers. As of 06:40 PM GMT+1 (UTC +01:00), our preview domain is loading correctly 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
This incident has been resolved.
Resolved
The issue has been resolved. All impacted systems are now operating normally as of Monday 11:00 AM PDT.
Resolved
This incident has been resolved.
Resolved
We experienced a window of errors on an upstream provider that we use to store artifacts produced when publishing lovable apps. This provider has now recovered and publishing success rates have returned to normal
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved. All impacted systems are operating normally since 11:00 AM PT Monday.
Resolved
Normal service has been restored. Payouts are no longer impacted by delayed settlements. Impact start time: 21/07/2026, 14:12 BST Impact end time: 21/07/2026, 15:51 BST Client actions: None
Resolved
On July 18, 2026, between approximately 00:30 UTC and 04:00 UTC, users might have experienced 5xx errors while trying to create a new bucket in the Object Storage for the following endpoints. * [us-ord-1.linodeobjects.com](http://us-ord-1.linodeobjects.com) * [us-lax-1.linodeobjects.com](http://us-lax-1.linodeobjects.com) * [us-iad-1.linodeobjects.com](http://us-iad-1.linodeobjects.com) * [us-sea-1.linodeobjects.com](http://us-sea-1.linodeobjects.com) * [fr-par-1.linodeobjects.com](http://fr-par-1.linodeobjects.com) The issue began when the infrastructure supporting Object Storage entered a degraded state across all nodes. This prevented the service from processing requests, resulting in failures during bucket creation operations. To mitigate the impact, we have applied a fix at the backend system responsible for bucket creation. The impact was mitigated following this action. Our subject matter experts are investigating the root cause and will take appropriate preventive actions. We apologize for the impact and appreciate your patience and ongoing support. We are making configuration and operational changes to our systems to help prevent this from happening again, and remain committed to continuous improvement. This summary provides an overview of our current understanding of the incident, given the information available. Our investigation is ongoing, and any information herein is subject to change.
Resolved
Query Insights functionality is restored on all Postgres development branches.
Resolved
This incident was resolved on Jul 20 14:00 UTC, and was posted retroactively.
Resolved