Planned Maintenance affecting Dynatrace Platform Subscription (DPS) cost and consumption data
From November 14 through November 16, 2026, we will perform scheduled maintenance on the Dynatrace service that calculates cost for paid DPS subscriptions. During the maintenance window, cost and consumption data processing will be paused. Your usage will continue to be metered, and the related costs will appear after maintenance is complete. This applies to SaaS and Managed deployments licensed via the Dynatrace Platform Subscription and will affect cost and consumption data accessed via the Account Management Portal, Account Management API, Cost and Budget Notifications, Cost Intelligence and Cost Allocation. Dynatrace environments, monitoring and data ingestion are not affected. For full details please see the Heads-Up post on the Dynatrace Community - https://community.dynatrace.com/t/57571
The latest update from Dynatrace.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Dynatrace
From November 14 through November 16, 2026, we will perform scheduled maintenance on the Dynatrace service that calculates cost for paid DPS subscriptions. During the maintenance window, cost and consumption data processing will be paused. Your usage will continue to be metered, and the related costs will appear after maintenance is complete. This applies to SaaS and Managed deployments licensed via the Dynatrace Platform Subscription and will affect cost and consumption data accessed via the Account Management Portal, Account Management API, Cost and Budget Notifications, Cost Intelligence and Cost Allocation. Dynatrace environments, monitoring and data ingestion are not affected. For full details please see the Heads-Up post on the Dynatrace Community - https://community.dynatrace.com/t/57571
Affected components
12Dynatrace in the last 90 days
Full historyIncidents in 90 days
0
Days with an incident
0
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.
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