Stack Status

AWS me-central-1 (UAE) and me-south-1 (Bahrain) have suffered damage in these regions. Workloads in me-central-1 (UAE) continue to experience significant impairments. In addition, workloads in me-south-1 (Bahrain) are currently not operational, cannot be modified, and are not able to migrate to other regions or support other disaster recovery actions such as backup and restore. According to the AWS Service Health Dashboard update from April 30th, recovery is expected to take several months. The latest information from AWS is available at: https://health.aws.amazon.com/health/status. We strongly recommend that customers with workloads in AWS me-central-1 act now to move their clusters to alternate regions instead of waiting for full availability to be restored. There are currently no recovery options available for data that is only present in the AWS me-south-1 region. We continue to assist customers in their chosen remediation path to the extent possible. Customers running workloads in the Middle East should consider alternate Atlas regions, such as those in North America, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements. Customers may continue to extend their backup snapshot expirations in me-central-1 as needed. We will move to an as-needed status post update cadence as new information becomes available. If you would like assistance assessing how these events may affect your Atlas deployment, our support team is available: * Open a support case through the MongoDB Support Portal * Start a chat with Support using the Intercom widget within the MongoDB Atlas interface

Started 125d ago

A fix has been implemented and we are monitoring the results.

Started 3d ago

Our upstream provider has implemented a fix, and we’re seeing hosted site loading times and SSL certificate provisioning return to expected performance levels. We’re continuing to monitor the situation closely and will share another update if needed.

Started 3d ago

Twilio customers may be experiencing SMS delivery failures from Twilio to Tigo network subscribers in Bolivia. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 8 hours or as soon as more information becomes available.

Started 3d ago

Twilio is aware that some Sender IDs used to send messages to Australia are being incorrectly overwritten as Unverified even though they are compliant with ACMA. Verify customers may see traffic incorrectly being sent using the TWVerify sender and a brandless template. We are working on identifying the impacted accounts and resolving the issue. We expect to provide another update in 16 hours or as soon as more information becomes available.

Started 4d ago

Core functionality has been restored but we are aware of known and ongoing issues in FedRAMP workspaces with Codex, workspace analytics, conversation search, searching for custom GPTs, ChatGPT user invites, and the Compliance Logs Platform download endpoint. We are working to resolve these issues and will share further updates we have more information available.

Started 4d ago

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Started 86d ago

Cloudflare is aware of and investigating Workers AI experiencing degraded availability in some models. Impacted models: - @cf/moonshotai/kimi-k2.6 - @cf/moonshotai/kimi-k2.7-code

Started 18d ago

The service degradation affecting Meta integration for Zoom has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.

Started 3d ago

We've shipped a fix and confirmed that it’s working. We’re going to keep a close eye on things for the next few hours just to be absolutely sure everything is stable.

Started 30d ago

We have identified an issue affecting a small subset of accounts in the EU1 region. As a result, data ingestion for impacted integrations may have stopped.

Started 12d ago