Transport service high CPU usage causing mail flow delays

Mason Mcgrath 40 Reputation points
2025-11-07T08:13:34.61+00:00

Has anyone dealt with Exchange 2019 randomly chewing up CPU and slowing down mail flow? On my server, MSExchangeTransport/EdgeTransport.exe keeps spiking to high CPU (70–90%), and mail queues start building up shortly after. A quick Transport service restart fixes it for a bit, but the issue always comes back. Server is fully patched, no config changes recently, and I’m only seeing occasional Event Viewer warnings (15006 and 7012) about transport performance.

Exchange | Exchange Server | Development
0 comments No comments
{count} votes

Answer accepted by question author
  1. Steven-N 15,075 Reputation points Microsoft External Staff Moderator
    2025-11-07T09:23:50.4333333+00:00

    Hi Mason Mcgrath

    Thank you for reaching out to Microsoft Q&A

    Based on my research, this typically occurs due to Transport back pressure or a stalled Transport agent. Back pressure throttles mail flow when disk space or memory on Transport paths crosses thresholds (Event 15006). Event 7012 often relates to log scanning overhead. High CPU can also result from anti-malware scanning or RMS/IRM decryption processes within EdgeTransport.exe.

    Link reference: https://v4.hkg1.meaqua.org/exchange/mail-flow/back-pressure

    Therefore, you can consider follow some options below to see if they can mitigate your issue:

    1.Check Back Pressure metrics

    Use Get-ExchangeDiagnosticInfo -Process EdgeTransport -Component ResourceThrottling yo confirm if disk or memory thresholds are triggering back pressure. Free space on %ExchangeInstallPath%\TransportRoles\data\Queue\ and ...\data\ should exceed Microsoft’s recommended limits. If needed, move the queue database and content conversion directories to a larger, faster volume via EdgeTransport.exe.config. As stated in https://v4.hkg1.meaqua.org/en-us/powershell/module/exchangepowershell/get-exchangediagnosticinfo?view=exchange-ps

    2.Validate receive connector bindings:

    Ensure only FrontendTransport connectors listen on TCP/25. As stated in https://v4.hkg1.meaqua.org/en-us/exchange/mail-flow/connectors/receive-connectors

    Hope my answer will help you

    Best regards.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

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