Welcome to the service status page. Here, you can stay up to date with the operational status of all your key services. Subscribe to receive instant notifications when incidents or maintenance occur. If you’re experiencing any issues not reflected here, please report them, or contact our support team directly for assistance. We’re committed to keeping everything running smoothly for you!
As of March 25, we deployed an update globally and continue to see stable service operation. At this time, we are not observing any new instances of this issue. Our engineering team continues follow-up work with Microsoft and internal engineering efforts to ensure all previously impacted scenarios are fully addressed and to drive a permanent resolution. We expect to have additional updates in the next few days and will share another update as soon as we have more information.
Last update on
We have identified the issue affecting the Business Intelligence (BI) Connector in MongoDB Atlas for Government. We are working on a fix. While no workaround exists, data remains accessible to MongoDB clients. Affected users will not be able to connect to their clusters' BI Connectors. Cluster health is unaffected.
Last update on
Since 01:35 UTC, we’ve been experiencing US SMS delivery issues affecting 2FA and OTP codes for Dashboard, Link, Issuing, and Express users. Non-SMS 2FA methods (security keys, authenticator apps) still work. We’re actively monitoring and will update when resolved.
Last update on
We are providing an update on the ongoing service disruptions affecting the AWS Middle East (Bahrain) Region (ME-SOUTH-1). We continue to make progress on recovery efforts across multiple workstreams. With the immediate phase of this event now better understood, we are moving to a more targeted communication model. Going forward, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. We continue to strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. Customers should enact their disaster recovery plans, recover from remote backups stored in other Regions, and update their applications to direct traffic away from the affected Regions. For customers requiring guidance on alternate regions, we recommend considering AWS Regions in the United States, Europe, or Asia Pacific, as appropriate for your latency and data residency requirements.
Last update on
Monitors
Intermittent SharePoint item download failures in Veeam Data Cloud for Microsoft 365
Veeam
MongoDB
Increased Connectivity Issues and API Error Rates
Amazon Web Services
StatusGator