outages.live
Live
DynatraceIncident ·

Information regarding the global Microsoft 365 outage

DegradedOfficial update
0

Parts of the Dynatrace Product and Dynatrace ecosystem services do not work, including email notifications, authentication/SSO, and Microsoft integrations, across the Analyze, Automate, AWS, Azure, and GCP regions. Dynatrace reports that it is investigating. The support portal works. Use the support portal for support cases and updates.

State

Investigating

Started

Ongoing for

32 min

Worst impact

Degraded

Timeline

1 update
10:1710:2510:3310:4110:49
DegradedUpdate postedTimes in UTC

Investigating

32 min 100%

Updates

Times in UTC

As posted by Dynatrace

Investigating

The current global Microsoft outage may affect parts of the Dynatrace product and related services that rely on Microsoft, such as email notifications, authentication/SSO, and Microsoft integrations. Email notifications for support case updates may also be delayed. The support portal is working as expected. Please use it for support cases and updates. You can see the latest Microsoft status at: https://status.cloud.microsoft/m365

Affected components

21
Dynatrace ProductDynatrace ecosystem servicesAnalyze-AWS-americasAnalyze-AWS-emeaAnalyze-AWS-asia-pacificAnalyze-Azure-americasAnalyze-Azure-asia-pacificAnalyze-Azure-emea

Dynatrace in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

Not enough data

This incident

Not comparable

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