Is Azure Database for MySQL down?
Current Azure Database for MySQL status is UP

We checked the official Azure Database for MySQL Status Page 1 min. 6 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Azure Database for MySQL Outages and Issues

Follow the recent outages and downtime for Azure Database for MySQL in the table below.

Start Time

Type

Length

Message

Details

July 19, 2024 04:03 UTC

WARN

ongoing

Investigating issues in the Central US region

See more
Start Time

July 19, 2024 04:03 UTC

Type WARN
Affected Components

Central US - Azure Database for MariaDB

Central US - Azure Database for MySQL

Central US - Azure Database for MySQL flexible servers

Message

Investigating issues in the Central US region

Details

Impact Statement: Starting at approximately 21:56 UTC on 18 Jul 2024, a subset of customers may experience issues with multiple Azure services in the Central US region including failures with service management operations and connectivity or availability of services.
Current Status: We are aware of this issue and have engaged multiple teams. We’ve determined the underlying cause. A backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of Azure Storage clusters and compute resources in the Central US region. This resulted in the compute resources automatically restarting when connectivity was lost to virtual disks. Mitigation has been confirmed for all Azure Storage clusters, we are continuing to mitigate residual and downstream impacted services. Customers should continue to see increasing recovery at this time as residual and downstream impact mitigation progresses. The next update will be provided in 60 minutes, or as events warrant.
https://learn.microsoft.com/azure/architecture/resiliency/recovery-loss-azure-region .
This message was last updated at 04:01 UTC on 19 July 2024

July 19, 2024 01:13 UTC

WARN

about 3 hours

Investigating issues in the Central US region

See more
Start Time

July 19, 2024 01:13 UTC

Type WARN
Affected Components

Central US - Azure Functions

Central US - ExpressRoute Gateways

Non-Regional - Azure AI Translator

Central US - Face API

Non-Regional - Power BI Embedded

Non-Regional - Static Web Apps

Central US - Cloud Services

Central US - Azure Service Fabric

Central US - Azure Spring Cloud

Non-Regional - Azure Virtual Desktop

Central US - Application Gateway

Central US - Application Gateway for Containers

Central US - Azure Firewall

Central US - Azure Communications Gateway

Central US - ExpressRoute Circuits

Central US - Azure Firewall Manager

Non-Regional - Azure Front Door

Central US - Load Balancer

Central US - Network Infrastructure

Central US - Network Watcher

Central US - Azure Private Link

Central US - Azure Route Server

Central US - Virtual Network

Central US - Azure Virtual Network Manager

Central US - Azure NAT Gateway

Central US - Virtual WAN

Central US - VPN Gateway

Central US - Web Application Firewall

Central US - Azure HPC Cache

Central US - Azure NetApp Files

Central US - Azure File Sync

Central US - API Management

Central US - App Service (Linux)

Central US - Web Apps Linux

Central US - Azure AI Search

Central US - Notification Hubs

Central US - Azure Container Apps

Central US - Azure Container Instances

Central US - Azure Container Registry

Central US - Azure Container Service

Central US - Azure Dev Spaces

Central US - Azure Red Hat OpenShift

Central US - Azure Managed Instance for Apache Cassandra

Central US - Azure Database for MariaDB

Central US - Azure Database for MySQL

Central US - Azure Database for PostgreSQL

Central US - SQL Server Stretch Database

Central US - Data Lake Analytics

Central US - Azure Data Lake Storage Gen1

Central US - Azure Data Share

Central US - HDInsight

Central US - Azure Stream Analytics

Central US - Azure AI services

Central US - Azure AI Anomaly Detector

Central US - Azure AI Vision

Central US - Content Moderator

Central US - Azure AI Language

Central US - Language Understanding (LUIS)

Central US - Azure AI Speech

Central US - Azure AI Immersive Reader

Central US - Azure AI Metrics Advisor

Central US - Azure AI Video Indexer

Central US - Azure Machine Learning

Central US - Azure IoT Central

Central US - Logic Apps

Central US - Azure Time Series Insights

Central US - Microsoft Entra Domain Services

Central US - Microsoft Azure Attestation

Central US - Azure DDoS Protection

Central US - Key Vault

Central US - Azure Key Vault Managed HSM

Central US - Azure DevTest Labs

Central US - Azure Automanage

Non-Regional - Azure Managed Applications

Central US - AutoScale

Central US - Log Analytics

Central US - Scheduler

Central US - Azure Site Recovery

Non-Regional - Universal Print

Central US - Azure Update Manager

Central US - Media Services

Non-Regional - Azure Migrate

Central US - Azure Database Migration Service (classic)

Central US - Azure Database Migration Service

Central US - Azure Arc enabled servers

Central US - Azure Arc enabled Kubernetes

Central US - Azure Arc enabled data services

Message

Investigating issues in the Central US region

Details

Impact Statement: Starting at 21:56 UTC on 18 Jul 2024, a subset of customers may experience issues with multiple Azure services in the Central US region including failures with service management operations and connectivity or availability of services.
Current Status: We are aware of this issue and have engaged multiple teams to investigate. As part of the investigation, we are reviewing previous deployments, and are running other workstreams to investigate for an underlying cause. The next update will be provided in 60 minutes, or as events warrant. 
Customers with disaster recovery procedures set up can consider trying to take steps to failover their services to another regions, and may consider using programmatic options for this if they experience issues.
https://learn.microsoft.com/azure/architecture/resiliency/recovery-loss-azure-region .
This message was last updated at 01:10 UTC on 19 July 2024

April 19, 2024 07:04 UTC

WARN

less than a minute

Active - Azure Databricks issues in West US, West US2, and South Central US

See more
Start Time

April 19, 2024 07:04 UTC

Type WARN
Affected Components

South Central US - Azure Database for MySQL

West US 2 - Azure Database for MySQL

Message

Active - Azure Databricks issues in West US, West US2, and South Central US

Details

Impact Statement: Starting at 04:26 UTC on April 19, 2024, customer using Azure Database for My SQL in West US, and Azure Databricks in West US, West US2, and South Central US may experience failures and timeouts with workspace login and authentication requests. The impact includes:
Current Status: We are actively investigating by engaging additional teams to determine the root cause for mitigation. The next update will be provided within 2 hours or as events warrant. 
This message was last updated at 07:02 UTC on 19 April 2024

April 19, 2024 07:04 UTC

WARN

44 minutes

Active - Azure Databricks issues in West US, West US2, and South Central US

See more
Start Time

April 19, 2024 07:04 UTC

Type WARN
Affected Components

South Central US - Azure Database for MySQL

West US 2 - Azure Database for MySQL

Message

Active - Azure Databricks issues in West US, West US2, and South Central US

Details

Impact Statement: Starting at 04:26 UTC on April 19, 2024, customer using Azure Database for My SQL in West US, and Azure Databricks in West US, West US2, and South Central US may experience failures and timeouts with workspace login and authentication requests. The impact includes:
Current Status: We are actively investigating by engaging additional teams to determine the root cause for mitigation. The next update will be provided within 2 hours or as events warrant. 
This message was last updated at 07:02 UTC on 19 April 2024

April 19, 2024 06:58 UTC

WARN

less than a minute

Active - Azure Databricks issues in West US, West US2, and South Central US

See more
Start Time

April 19, 2024 06:58 UTC

Type WARN
Affected Components

South Central US - Azure Database for MySQL

West US - Azure Database for MySQL

West US 2 - Azure Database for MySQL

Message

Active - Azure Databricks issues in West US, West US2, and South Central US

Details

Impact Statement: Starting at 04:26 UTC on April 19, 2024, customer using Azure Databricks in West US, West US2, and South Central US may experience failures and timeouts with workspace login and authentication requests. The impact includes:
Current Status: We are actively investigating by engaging additional teams to determine the root cause for mitigation. The next update will be provided within 2 hours or as events warrant. 
This message was last updated at 06:54 UTC on 19 April 2024

2024-07-19 09:50:26 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 09:50:26 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 09:50:26 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 09:50:26 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-07-19 09:50:26 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Azure Database for MySQL History

StatusGator has over 9 years of Azure Database for MySQL status history.

2 status changes in the last 24 hours

Azure Database for MySQL status, last 24 hours:

10:00 AM
4:00 PM
10:00 PM
4:00 AM
10:00 AM
10:00 AM
10:00 PM
10:00 AM
  • Up: 15 hours

  • Warn: 9 hours

  • Down: 0 minutes

Azure Database for MySQL Outage and Status History

We've been monitoring Azure Database for MySQL outages since March 22, 2015.
Here's the history of service outages we've observed from the Azure Database for MySQL Status Page:

June 2024

May 2024

  • Up

  • Warn

  • Down

Instant enriched data from
3,960 status pages

About Our Azure Database for MySQL Status Page Integration

Azure Database for MySQL is a Cloud Infrastructure and Microsoft solution that StatusGator has been monitoring since March 2015. Over the past over 9 years, we have collected data on on more than 1,804 outages that affected Azure Database for MySQL users. When Azure Database for MySQL publishes downtime on their status page, they do so across 5,887 components and 65 groups using 3 different statuses: up, warn, and down which we use to provide granular uptime metrics and notifications.

More than 2,400 StatusGator users monitor Azure Database for MySQL to get notified when it's down or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 169,900 notifications to our users about Azure Database for MySQL incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Azure Database for MySQL is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Azure Database for MySQL is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Azure Database for MySQL does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need Azure Database for MySQL maintenance notifications, please email us.

Azure Database for MySQL does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Azure Database for MySQL maintenance events into your unified calendar.

When Azure Database for MySQL posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Azure Database for MySQL has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Azure Database for MySQL has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Azure Database for MySQL Down?

Are you experiencing issues with Azure Database for MySQL? Sign up to receive notifications when Azure Database for MySQL publishes outages.

Azure Database for MySQL Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,960 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Azure Database for MySQL?

Sign up for StatusGator and see all historical information about Azure Database for MySQL outages and performance issues. Get free, instant notifications when Azure Database for MySQL goes down.

No outages or status changes in the last 24 hours

Azure Database for MySQL status, last 24 hours:

6:00 AM
12:00 PM
6:00 PM
12:00 AM
6:00 AM
6:00 AM
6:00 PM
6:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

Azure Database for MySQL Outage and Status History

We've been monitoring Azure Database for MySQL outages since March 22, 2015.
Here's the history of service outages we've observed from the Azure Database for MySQL Status Page:

June 2024

May 2024

  • Up

  • Warn

  • Down