Skip to main content
Honeycomb

PagerDuty outage prevented Trigger and SLO notifications

Degraded Lasted 0m · started · Honeycomb's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on Honeycomb. 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 0m it lasted.

    Anything that failed between 2025-08-28 16:40 UTC and 2025-08-28 04:30 UTC may need a replay.
  • Subscribe to Honeycomb's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=honeycomb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Honeycomb 1

  1. resolved

    A PagerDuty outage prevented some Trigger and SLO notifications from reaching your workspaces. The issue has since been resolved, and notification systems are now operating normally. Impact Window: 21:54 PT – 23:27 PT

    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-5f83961019

Is Honeycomb still down?

No, this incident was resolved 2025-08-28 04:30 UTC. For Honeycomb's live state, see https://down.guide/honeycomb.

How long did it last?

0m, from 2025-08-28 16:40 UTC to 2025-08-28 04:30 UTC, by the times Honeycomb posted.

What caused it?

Honeycomb hasn't published a root cause. If it does, it shows here.

Where does this come from?

Honeycomb's official status page, https://status.honeycomb.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.