Aborted connections spike and service disruption on Azure MySQL Flexible Server

Saeed C 0 Reputation points
2025-08-01T11:55:40.3666667+00:00

We experienced a major service disruption on our Azure Database for MySQL – Flexible Server instance (ecco-db2) around 2:00 AM BST on 8 June 2025. We are seeking a Root Cause Analysis (RCA) for the following incident:

Summary of Observations:

  • Aborted Connections: Over 30,000 aborted connections were recorded during a short time span, and is still on going till today (1st Aug 2025).
  • Host CPU Usage: Spiked to 99–100%, indicating potential saturation or runaway queries.
  • Memory Usage: Dropped significantly during the same window, implying a possible server restart, crash or failover.

Can you provide a Root Cause Analysis (RCA) for the aborted connection on 8 June and advise why aborted connections are still ongoing as of 1 August 2025?

Thanks in advance.

Azure Database for MySQL
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.