{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreien543dqrjgcm3lkuwg3s52wrrv7z44j4umqrzloduq75cewyrwlm",
    "uri": "at://did:plc:tgi77rwbcyuiaxc7eirgiqdn/app.bsky.feed.post/3mlcoy4sodd42"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiblq3wqbt5gewbqpvfd2dcif7lthr4xh6bn4ijrioze7qdcyvadm4"
    },
    "mimeType": "image/png",
    "size": 3910
  },
  "path": "/incidents/wjrkhvg9ydc1",
  "publishedAt": "2026-05-08T02:16:54.000Z",
  "site": "https://status.datadoghq.com",
  "textContent": "May  7, 22:16 EDT\n**Update** - We have identified due to upstream provider issues, we are continuing to see unavailability of telemetry data coming from AWS into Datadog. We are continuing to work on a fix.\n\nhttps://health.aws.amazon.com/health/status\n\nMay  7, 22:02 EDT\n**Update** - We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are working on a fix.\n\nhttps://health.aws.amazon.com/health/status\n\nMay  7, 21:20 EDT\n**Identified** - We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are working on a fix.\n\nhttps://health.aws.amazon.com/health/status\n\nMay  7, 20:47 EDT\n**Update** - Due to upstream provider issues, we are also continuing to see unavailability of telemetry data coming from AWS into Datadog.\n\nhttps://health.aws.amazon.com/health/status\n\nMay  7, 20:24 EDT\n**Update** - We are investigating increased latency across multiple products which began at 23:39 UTC. As a result of this issue, some users may see delays in data across the platform.\n\nMay  7, 20:06 EDT\n**Investigating** - We are investigating delays in Monitors Notifications, which began at 23:39 UTC.",
  "title": "Delayed Monitors Notifications",
  "updatedAt": "2026-05-08T02:16:54.000Z"
}