Live

Dynatrace Developer Portal is currently unavailable

0

The Dynatrace Developer Portal was unavailable and affected Dynatrace ecosystem services and the Dynatrace Website. Dynatrace reports that the issue is resolved. The outage lasted 2 hours and 38 minutes.

State

Resolved

Started

Lasted

2 h 38 min

Worst impact

Partial outage

Timeline

4 updates
08:0708:4709:2610:0510:45
Partial outageDegradedUpdate postedTimes in UTC

Investigating

2 h 38 min 100%

Updates

Times in UTC

As posted by Dynatrace

Resolved
Investigating

The Dynatrace Developer Portal is currently accessible. Service was restored at 09:14 UTC and we are monitoring availability to confirm continued stability. We will provide our next update within four hours, or sooner if further information becomes available. We apologize for the inconvenience.

Investigating

The Dynatrace Developer Portal (developer.dynatrace.com) is currently unavailable, preventing access to documentation and resources for Dynatrace app development. We are investigating the issue and working to restore availability. We will provide our next update within four hours, or sooner if further information becomes available. We apologize for the inconvenience.

Investigating

The Dynatrace Developer Portal (developer.dynatrace.com) is currently unavailable, preventing access to documentation and resources for Dynatrace app development. We are investigating the issue and working to restore availability. Please monitor Dynatrace Status for further updates. We apologize for the inconvenience.

Affected components

2
Dynatrace ecosystem servicesDynatrace Website

Dynatrace in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

6

Median duration

4 h 53 min

This incident

46% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

40 h 50 min
median 4 h 53 min
90 days agoToday

Other Dynatrace incidents

All incidents

Follow Dynatrace

Your coding agent knows when Dynatrace is down, and tells you when a failure is theirs, not yours. You can also get Dynatrace incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dynatrace" and tell me if Dynatrace has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=dynatrace
Slack
/feed subscribe https://outages.live/feed.xml?providers=dynatrace

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane