Increase in Billing for Backup Usage
We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us.
We have resolved the issue that caused the overage and usages should be reflected correctly by April 28th. If you still see incorrect usages after this date, please reach out to us.
This incident has been resolved.
Some Atlas users may be unable to access Charts and the Visualization page due to repeated login prompts or unauthorized errors when attempting to sign in. Our engineers have identified a recent change as the likely cause, have rolled it back, and are monitoring the service to confirm that normal access has been restored.
We are no longer seeing capacity issues in Azure East US 2. This issue is now resolved.
We are no longer seeing intermittent spikes in HTTP 503 errors.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Azure has an active service issue for virtual machines in East US 2. According to their service health page, "customers using Virtual Machines in East US 2 may have encountered errors when performing service management operations - such as create, update, scale, or start - for resources in this region. [...] During peak impact, an unexpected surge in usage caused backend Virtual Machine components to reach operational limits, resulting in deployment failures for some VMs. We are actively mitigating through load balancing and resource reclamation. Capacity constraints for affected SKUs persist, and our teams continue working to restore normal levels."
We are actively engaging with Azure support.
At approximately 10:30 AM CT, we identified an issue affecting stream processing within the AWS US-EAST-1 region. As of now, normal operations have resumed. We have initiated a full investigation to determine the root cause and prevent future recurrence.