- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 100
What to do
Check whether your product depends on Elastic Observability. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 22m it lasted.
Anything that failed between 2026-08-27 17:11 UTC and 2026-08-27 18:33 UTC may need a replay.Subscribe to Elastic Observability's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=elastic-apm works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Elastic Observability 2
- monitoring
On August 26, at around 00:00 UTC we deployed a change in Managed Inputs that affected some rules in our internal DNS provider, removing the .apm endpoints some of our Serverless customers. The service was restored around 9AM UTC on the same day. During this time, some customers would have experienced unavailability of the .apm endpoint, for a period in the 9 hour window. We are putting some checks and alerts in place to ensure this does not happen again.
provider
- resolved
This is now resolved
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-a39f02cd4a
Is Elastic Observability still down?
No, this incident was resolved 2026-08-27 18:33 UTC. For Elastic Observability's live state, see https://down.guide/elastic-apm.
How long did it last?
1h 22m, from 2026-08-27 17:11 UTC to 2026-08-27 18:33 UTC, by the times Elastic Observability posted.
What caused it?
Elastic Observability hasn't published a root cause. If it does, it shows here.
Where does this come from?
Elastic Observability's official status page, https://status.elastic.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.