Dynatrace logo

Is Dynatrace Down?

Developer ToolsLive status, outages, and incident history

No. Dynatrace is up right now.

Every monitored Dynatrace system is operational as of August 24, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive, rechecked every 60s
How we know: the official Dynatrace status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Dynatrace Component Status

The main Dynatrace systems on this page. All 44 are operational right now.

44operational
Dynatrace ecosystem services [Dynatrace Account Management]
Operational
Dynatrace ecosystem services [Dynatrace Community]
Operational
Dynatrace ecosystem services [Dynatrace Hub]
Operational

41 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Dynatrace ecosystem services [Dynatrace Managed], Dynatrace ecosystem services [Dynatrace Search], Dynatrace ecosystem services [Dynatrace Support Portal], Dynatrace ecosystem services [Dynatrace University], Dynatrace ecosystem services [Dynatrace Website], Dynatrace Product [Analyze-AWS-americas], Dynatrace Product [Analyze-AWS-asia-pacific], Dynatrace Product [Analyze-AWS-emea], Dynatrace Product [Analyze-Azure-americas], Dynatrace Product [Analyze-Azure-asia-pacific], Dynatrace Product [Analyze-Azure-emea], Dynatrace Product [Analyze-GCP-americas], and 29 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Dynatrace Outages & Incidents

Incident history from the official Dynatrace status page, including resolution updates.

Planned Maintenance affecting Authentication and Identity Management ServicesScheduled for Aug 29, 2026 · 1h 0mScheduled

Scheduled Maintenance

Monitoring Visibility Impacted for AWS Lambda Layers on Node.js 22Resolved Aug 20, 2026 · 84h 45mResolved

We are aware of an issue resulting in a loss of monitoring visibility for Lambda functions on Node.js version 22. Our team is actively investigating this issue and are working towards mitigation. We understand the importance of reliable monitoring and will provide the next update within the next four hours, or sooner if additional information becomes available. Thank you for your patience and understanding. --- [2026-08-20T23:05:57.200Z] (400) We are actively investigating an issue causing a loss of monitoring visibility for Lambda functions running on Node.js version 22. We recommend that customers avoid running nodejs:22.version 95 while our teams continue to assess scope, impact, and the path to mitigation. As an interim mitigation, customers may roll back to their previously working Node.js 22 runtime version. If assistance is needed to perform the rollback, please engage AWS Support. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience --- [2026-08-21T00:01:20.802Z] (400) We have identified the issue causing a loss of monitoring visibility for Lambda functions running on Node.js version 22. Classic Lambda layers do not work correctly with the newest AWS-provided Node.js 22 runtime version (nodejs:22.mainline.v95), causing affected Lambda functions to time out and lose OneAgent monitoring. To avoid this impact, we recommend that customers do not update to nodejs:22.mainline.v95. If you have already updated and are affected, you can roll back to the previously working Node.js 22 runtime (for example, v91). If assistance is needed to perform the rollback, customers should engage AWS Support. Our teams are working on a permanent fix and will continue to share updates as more information becomes available. We apologize for the inconvenience and appreciate your patience. --- [2026-08-21T08:04:57.292Z] (400) We continue to work on the identified issue affecting Lambda functions running on the AWS-provided Node.js 22 runtime version (nodejs:22.mainline.v95), causing affected Lambda functions to time out and lose OneAgent monitoring. We are actively working with AWS towards a permanent fix. In parallel, our teams are investigating additional mitigation options to help reduce customer impact. As a precaution, we continue to recommend that customers do not update to nodejs:22.mainline.v95. If you have already updated and are experiencing issues, you may roll back to a previously working Node.js 22 runtime version (for example, v91). Customers requiring assistance with a rollback should engage AWS Support. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience. --- [2026-08-21T20:05:51.279Z] (400) We have identified the root cause of the issue affecting monitoring visibility for Lambda functions running on the AWS-provided Node.js 22 runtime (nodejs:22.mainline.v95), and mitigations have been applied. A fix has been released in OneAgent 1.343 for SaaS environments. Investigation into fixes for additional supported versions is ongoing. We will provide updates as they become available. As an interim workaround, customers can continue to pin their Lambda runtime to a previously working Node.js 22 version (e.g., v91). Customers requiring assistance with a rollback should engage AWS Support. We will continue to monitor the situation closely over the weekend and provide a further update once more information is available. We appreciate your patience as we work to fully resolve this issue.

Access to Dynatrace services is currently impacted in AWS US EastResolved Aug 13, 2026 · 1h 51mResolved

We have identified an issue affecting Dynatrace services hosted in AWS US East. Users may experience errors in the Dynatrace UI, slower-than-normal performance, and missing or delayed alerts. We are working to mitigate the impact and restore normal service. Please continue to monitor Dynatrace Status for updates. We apologize for the inconvenience and will provide an update within the next two hours or sooner if we have more information to share. --- [2026-08-13T15:16:09.185Z] (100) We have identified the issue affecting Dynatrace services hosted in AWS US East. Mitigation efforts have been implemented, and customers should begin to see service improvement. We are actively monitoring recovery to validate the effectiveness of these mitigations and confirm continued stabilization. We apologize for the inconvenience and thank you for your patience. The next update will be provided within two hours, or sooner if meaningful progress is confirmed.

Dynatrace Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Dynatrace incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
May 2689.85% average · 19 days with incidentsAug 24

Going further back: Dynatrace uptime by month and every recorded Dynatrace outage.

Live Dynatrace Outage Reports

Problems reported by engineers using Dynatrace. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Dynatrace problems reported yet.

Something wrong with Dynatrace on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Dynatrace

Dynatrace is an enterprise AI-powered observability platform providing full-stack monitoring, distributed tracing, and AIOps for complex hybrid cloud environments. Track Dynatrace status and outages here.

Over the past 30 days, PulsAPI has measured Dynatrace uptime at 98.81%. Response times, incident history, and SLA tracking for Dynatrace are available on the PulsAPI dashboard.

Dynatrace Status FAQ

Is Dynatrace down right now?

PulsAPI checks Dynatrace every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Dynatrace status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Dynatrace is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Dynatrace recovers.

How do I check Dynatrace uptime history?

PulsAPI tracks Dynatrace uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 98.81%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Dynatrace.

How fast does PulsAPI detect Dynatrace outages?

PulsAPI polls the official Dynatrace status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Dynatrace components?

Yes. PulsAPI monitors 44 individual Dynatrace components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Dynatrace goes down?

Yes. Create a PulsAPI account and subscribe to Dynatrace. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Dynatrace status changes.

How do I report an issue with Dynatrace to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Dynatrace problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Dynatrace?

Yes. PulsAPI's Starter plan includes up to 25 monitored services with Slack and email alerts, and the 30-day free trial requires no credit card. You can monitor Dynatrace alongside up to 24 other services at pulsapi.com/signup.

Track Dynatrace with the rest of your stack

Monitor 2463+ cloud services from one dashboard and get alerts when Dynatrace status changes.

Start free trial