Support Portal Access Disruption
Dynatrace reports that the Dynatrace Support Portal does not work. This affects Dynatrace ecosystem services, including education and community resources, for a limited number of customers. Dynatrace is investigating the issue. Customers who need help can call Dynatrace Support at 1-844-900-DYNA (3962).
State
Investigating
Started
Ongoing for
1 h 14 min
Worst impact
Major outage
Timeline
1 updateInvestigating
1 h 14 min 100%
Updates
Times in UTCAs posted by Dynatrace
We are investigating an issue affecting access to the Dynatrace Support Portal, including education and community resources, for a limited number of customers. Affected users may be unable to sign in. Customers who need help can call Dynatrace Support at 1-844-900-DYNA (3962) We will provide our next update within two hours, or sooner as meaningful progress is made.
Affected components
2Dynatrace in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
1
Median duration
Not enough data
This incident
Not comparable
Other Dynatrace incidents
All incidentsFollow 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.
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.
https://outages.live/feed.xml?providers=dynatrace/feed subscribe https://outages.live/feed.xml?providers=dynatraceFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane