Live

Metric Ingest Freshness Issue on AWS EU-WEST1 (Ireland)

0

Metric ingestion had delays for Dynatrace Product and Process-AWS-emea in the AWS EU-WEST1 (Ireland) region. Dynatrace reports that the incident is resolved. The incident lasted about 7 hours and 8 minutes.

State

Resolved

Started

Lasted

7 h 8 min

Worst impact

Degraded

Timeline

4 updates
11:4313:3015:1717:0418:51
DegradedUpdate postedTimes in UTC

Investigating

7 h 8 min 100%

Updates

Times in UTC

As posted by Dynatrace

Resolved
Investigating

Metrics ingestion is currently operating normally in the AWS EU-WEST1 (Ireland) region. We continue to monitor service stability and investigate the incident. We apologize for the inconvenience and will provide further updates as information becomes available.

Investigating

We are investigating an issue affecting environments on AWS in the EU-WEST1 (Ireland) region. Customers may currently experience delays in metrics ingestion. We are working to restore normal processing as quickly as possible. We will provide another update by 1:30 PM UTC, or sooner if further information becomes available.

Investigating

We are investigating an issue affecting environments on AWS in the EU-WEST1 region. Customers may currently experience delays in metrics ingestion. We are working to restore normal processing as quickly as possible. We will provide another update by 1:30 PM UTC, or sooner if further information becomes available.

Affected components

2
Dynatrace ProductProcess-AWS-emea

Dynatrace in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

7 h 8 min

This incident

About the median

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

31 h 7 min
median 7 h 8 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