We are providing an update on the ongoing service disruption. The Middle East (UAE) Region (ME-CENTRAL-1) has suffered damage as a result of the conflict in the Middle East and is currently unable to reliably support customer applications. While some workloads continue to function normally, we strongly recommend customers migrate all accessible resources to other Regions and restore inaccessible resources from remote backups as soon as possible. Relevant billing operations are currently suspended while we restore normal operations in this AWS Region. This process is expected to take several months.
We have identified a customer configured provider that is timing out when sent posture check requests.
We have applied a mitigation and are seeing recovery from the issue causing some ChatGPT web users to be unexpectedly logged out when refreshing the page. We’ll continue monitoring closely to confirm the recovery is sustained.
We have successfully completed validation of the fix in our test environment and have begun rolling it out to production. Our teams will continue deploying the fix across all remaining impacted environments while closely monitoring services. We will provide another update as significant progress is made or sooner if additional information becomes available.
We're continuing to work on restoring messages, message edits, and file shares for a limited number of workspaces that were affected by an issue with custom data retention settings. We've fixed what triggered the issue and are running data recovery using backup restoration methods. Custom retention settings have been restored for impacted channels, and we're gradually re-enabling retention jobs.We will provide another update as additional information becomes available.
Twilio customers may be experiencing SMS delivery delays and failures from a subset of Twilio Alphanumeric Sender IDs to Viva network subscribers in the Dominican Republic. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
We are continuing to investigate an issue affecting Salesforce integrations in Zapier. Some Salesforce connections were invalidated and may show as expired or disconnected in My Apps. How to tell if you’re affected • Go to My Apps: https://zapier.com/app/connections • If your Salesforce connection shows as expired or disconnected, you’re affected • Zaps that use that Salesforce connection as a trigger (especially polling triggers) may stop firing while the connection is expired • You may also see held Zap runs or trigger authentication failures in Zap History What to do Reconnect the affected Salesforce connection from My Apps. Use a Salesforce user that has permission to authorize the connection in your org. Once reconnected, polling triggers should resume on their normal schedule. Held or missed runs should begin processing again after the connection is healthy. Other impact Zap steps that do not use the affected Salesforce connection, and workflows outside Salesforce, are not broadly affected based on what we know so far. What we’re doing Re-authentication has restored service for customers who have the required Salesforce permissions. We have not deployed a platform-wide fix yet. We are investigating why these connections were invalidated and coordinating with Salesforce. We will provide another update within 60 minutes. If you need help, contact Support: https://zapier.com/app/get-help
StatusGator