Outage in Dynatrace

OneAgent becomes offline after upgrading to version 1.307 on certain Windows hosts

Resolved Minor
February 24, 2025 - Started 16 days ago - Lasted about 18 hours

Need to monitor Dynatrace outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Dynatrace, and never miss an outage again.
Start Free Trial

Outage Details

We have identified an issue on Windows hosts where the OneAgent has gone offline after the upgrade to version 1.307. For customer being impacted by this issue we recommend manually installing previous working version 1.305 as a workaround. We are actively addressing this issue and will provide updates as progress is made.
Components affected
Dynatrace AWS - Cluster 48 in US East Virginia Dynatrace AWS - Cluster 36 in US East Virginia Dynatrace AWS - Cluster 76 in EU West London Dynatrace AWS - Cluster 35 in US East Virginia Dynatrace AWS - Cluster 25 in US East Virginia Dynatrace AWS - Cluster 44 in US East Virginia Dynatrace AWS - Cluster 45 in US East Virginia Dynatrace AWS - Cluster 29 in EU West Ireland Dynatrace AWS - Cluster 49 in EU Central Frankfurt Dynatrace AWS - Cluster 40 in APAC Southeast Sydney Dynatrace AWS - Cluster 78 in APAC Southeast Singapore Dynatrace AWS - Cluster 31 in US East Virginia Dynatrace AWS - Cluster 33 in EU West Ireland Dynatrace AWS - Cluster 83 in US West Oregon Dynatrace AWS - Cluster 11 in US East Virginia Dynatrace AWS - Cluster 14 in US East Virginia Dynatrace AWS - Cluster 79 in EU Central Frankfurt Dynatrace AWS - Cluster 82 in US East Virginia Dynatrace Azure - Cluster 3 in West Europe Netherlands Dynatrace AWS - Cluster 75 in US East Virginia Dynatrace AWS - Cluster 34 in EU West Ireland Dynatrace AWS - Cluster 39 in US East Virginia Dynatrace AWS - Cluster 60 in US East Virginia Dynatrace AWS - Cluster 41 in EU West Ireland Dynatrace AWS - Cluster 30 in EU West Ireland Dynatrace AWS - Cluster 70 in US East Virginia Dynatrace AWS - Cluster 28 in US East Virginia Dynatrace AWS - Cluster 26 in US East Virginia Dynatrace AWS - Cluster 27 in APAC Southeast Sydney Dynatrace AWS - Cluster 71 in US East Virginia Dynatrace AWS - Cluster 72 in US East Virginia Dynatrace AWS - Cluster 73 in US East Virginia Dynatrace AWS - Cluster 74 in SA East São Paulo Dynatrace AWS - Cluster 84 in US East Virginia Dynatrace AWS - Cluster 85 in AP South Mumbai Dynatrace AWS - Cluster 86 in CA Central Canada Dynatrace Azure - Cluster 0 in US East Virginia Dynatrace AWS - Cluster 80 in APAC Southeast Sydney Dynatrace AWS - Cluster 4 in EU West Ireland Dynatrace AWS - Cluster 7 in EU West Ireland Dynatrace AWS - Cluster 10 in US East Virginia Dynatrace Azure - Cluster 6 in UAE North Dynatrace Azure - Cluster 7 in Switzerland North Dynatrace Azure - Cluster 8 in US East Virginia Dynatrace AWS - Cluster 1 in US East Virginia Dynatrace AWS - Cluster 2 in US West Oregon Dynatrace AWS - Cluster 50 in US East Virginia Dynatrace Azure - Cluster 1 in US East Virginia Dynatrace AWS - Cluster 61 in US East Virginia Dynatrace AWS - Cluster 32 in US East Virginia Dynatrace AWS - Cluster 42 in US East Virginia Dynatrace AWS - Cluster 87 in AP Northeast Tokyo Dynatrace AWS - Cluster 12 in APAC Southeast Sydney Dynatrace Azure - Cluster 2 in US East Virginia Dynatrace Azure - Cluster 4 in US West 3 Arizona Dynatrace AWS - Cluster 77 in EU West London Dynatrace AWS - Cluster 81 in US East Virginia Dynatrace AWS - Cluster 47 in EU West London Dynatrace Azure - Cluster 5 in Canada Central Dynatrace AWS - Cluster 37 in US West Oregon Dynatrace AWS - Cluster 38 in EU West Ireland Dynatrace AWS - Cluster 43 in EU West Ireland Dynatrace AWS - Cluster 46 in EU Central Frankfurt Dynatrace AWS - Cluster 13 in EU West Ireland Dynatrace AWS - Cluster 3 in US East Virginia Dynatrace AWS - Cluster 6 in US East Virginia Dynatrace AWS - Cluster 8 in US East Virginia Dynatrace AWS - Cluster 9 in EU West Ireland Dynatrace AWS - Cluster 5 in APAC Southeast Sydney Dynatrace AWS - Cluster 15 in US East Virginia Dynatrace AWS - Cluster 16 in US West Oregon Dynatrace AWS - Cluster 17 in US East Virginia Dynatrace AWS - Cluster 18 in US West Oregon Dynatrace AWS - Cluster 19 in EU West Ireland Dynatrace AWS - Cluster 20 in EU West Ireland Dynatrace AWS - Cluster 21 in US East Virginia Dynatrace AWS - Cluster 22 in US East Virginia Dynatrace AWS - Cluster 23 in EU West Ireland Dynatrace AWS - Cluster 24 in US West Oregon Dynatrace AWS - Cluster 51 in US East Virginia Dynatrace AWS - Cluster 52 in APAC Southeast Sydney Dynatrace AWS - Cluster 53 in US East Virginia Dynatrace AWS - Cluster 54 in US East Virginia Dynatrace AWS - Cluster 56 in US East Virginia Dynatrace AWS - Cluster 57 in US East Virginia Dynatrace AWS - Cluster 58 in EU West Ireland Dynatrace AWS - Cluster 59 in US West Oregon Dynatrace AWS - Cluster 62 in US East Virginia Dynatrace AWS - Cluster 63 in US East Virginia Dynatrace AWS - Cluster 64 in US East Virginia Dynatrace AWS - Cluster 65 in EU West Ireland Dynatrace AWS - Cluster 66 in CA Central Canada Dynatrace AWS - Cluster 67 in US East Virginia Dynatrace AWS - Cluster 68 in US East Virginia Dynatrace AWS - Cluster 69 in CA Central Canada Dynatrace Azure - Cluster 9 in US East Virginia Dynatrace GCP - Cluster 1 in US East4 Virginia Dynatrace GCP - Cluster 2 in EUROPE West3 Frankfurt Dynatrace GCP - Cluster 3 in US East4 Virginia Dynatrace GCP - Cluster 4 in US East4 Virginia
Latest Updates ( sorted recent to last )
16 days ago - at 02/24/2025 04:49AM

We have identified an issue on Windows hosts where the OneAgent has gone offline after the upgrade to version 1.307. For customer being impacted by this issue we recommend manually installing previous working version 1.305 as a workaround. We are actively addressing this issue and will provide updates as progress is made.

16 days ago - at 02/24/2025 10:04AM

We have identified an issue with the latest OneAgent release that is affecting only Windows servers having Carbon Black EDR installed. Affected customers can use the following workaround: Disable the option in Settings -> Processes and containers -> Built-in detection rules -> Automatically detect security software. After disabling it, either wait for the OneAgent to restart on its own (which happens every hour) or restart it manually. We are currently working on a permanent fix. We appreciate your patience and apologise for any inconvenience caused.

15 days ago - at 02/24/2025 04:41PM

We are still working on a permanent fix.

In the meantime, affected customers can still use the following workaround:
Disable the option in Settings -> Processes and containers -> Built-in detection rules -> Automatically detect security software. After disabling it, either wait for the OneAgent to restart on its own (which happens every hour) or restart it manually.

15 days ago - at 02/24/2025 10:53PM

An updated version 1.307.58.20250224-131615 has been deployed to all tenants. You can now safely re-enable the option in Settings -> Processes and containers -> Built-in detection rules -> Automatically detect security software, and restart the Oneagent. We apologize for any inconvenience caused. Please reach out to us via chat or ticket if you need assistance.

Stop chasing third-party outages across multiple status pages

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3845 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook