MongoDB CloudCluster connectivity issues in Azure westus
Azure has rolled out mitigation for the networking incident affecting the West US region and recovery is complete.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Azure has rolled out mitigation for the networking incident affecting the West US region and recovery is complete.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. Visibility performance has been restored.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have resolved issues affecting customers ability to load some products into the shopping cart
Resolved
The issue has now been resolved and we have directly notified all customers who were impacted by this outage. We’re sorry for any inconvenience caused.
Resolved
Between 11:17 AM EDT (UTC -04:00) and 12:14 PM EDT (UTC -04:00), some customers in all affected regions experienced issues with service tools. This was caused by a data fetching issue. As of 12:14 PM EDT (UTC -04:00), our service tools are working properly 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
Resolved
This incident has been resolved.
Resolved
Delivery delays have been resolved, MFA email delivery is fully functional for all customers.
Resolved
The system remains stable, and imports through the API, CSV upload, or SFTP are processing normally. Imports that failed during the incident were not reprocessed automatically. If an import you started between 8:00 AM and 11:00 AM US/Eastern on July 23, 2026 did not complete, please re-run it to ensure those profiles are imported. This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue affecting MMS delivery reports to T-Mobile has been resolved. MMS delivery reports are now processing as expected.
Resolved
The incident is now resolved and the system is full operational. Delays began around 14:03 UTC caused by an issue publishing to a new Kafka topic. Recovery began around 14:40 UTC as the team was able to isolate this topic. The consuming services which schedules new function runs was scaled out and began to consume the backlog. No events were dropped during this incident, all functions were scheduled, but with delays during this time window. No action is needed for manual recovery.
Resolved
We had a brief recurrence of yesterday's <a href="https://status.snyk.io/incidents/n0mqq1rwbmgw">incident</a>, affecting customers in two short windows: 14:27–14:36 UTC 14:37–14:42 UTC Service has now recovered. Customers should re-import any imports that errored or failed during these windows.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The topics fully drained and everything is back to baseline and operational again. No data was lost.
Resolved
This incident has been resolved.
Resolved
Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade. The affected cluster has since recovered, and connectivity is operating as expected.
Resolved
This incident has been resolved. Thanks a lot for your patience while we worked on a fix here.
Resolved
We have identified a process on a single server causing Basic DRM transformation failures, and was the cause of intermittent video freezes/500s. This has been rectified by the Engineering team.
Resolved
This incident has been resolved.
Resolved
Our team has resolved the issue impacting some partners when navigating XPM and Xero HQ. We apologise for any inconvenience this has caused.
Resolved
This incident has been resolved.
Resolved
No further impact was observed during our monitoring period. Customers should re-import any imports that errored or failed during the outage window. The Snyk Incident Response has been stood down.
Resolved
This issue is now resolved.
Resolved
We can confirm that the issue was mitigated at 04:36 UTC on 16 July 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
Resolved
Between 19:24 UTC on 22 July and 01:50 UTC on 23 July, customers using the gen3 preview machine (Linux VM) resource classes experienced delays and, in some cases, jobs failing to start. We have removed the gen3 resource classes while we address stability issues affecting them. Unfortunately, workflows that we were unable to provision compute capacity for during this period were cancelled. Affected customers should change their resource class from gen3 to gen2 and rerun those workflows. We thank you for your patience while our team worked to resolve this.
Resolved
All actions have fully recovered.
Resolved
Log ingestion is stable.
Resolved
The delays affecting exports and analytics within Recurly Subscription Management have been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved