Skip to main content
LogRocket

Ingestion outage

Partial outage Lasted 2h 2m · started · LogRocket's page

Level
confirmed
Worst impact
Partial outage
Components
Session Collection, Alerts
Down Index
32of 100

What to do

  • Check whether you use LogRocket Session Collection, Alerts. 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 2h 2m it lasted.

    Anything that failed between 2022-03-04 18:42 UTC and 2022-03-04 20:44 UTC may need a replay.
  • Subscribe to LogRocket's feed to hear about the next one first. RSS feed

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

Updates from LogRocket 5

  1. investigating

    We are working with our vendor to investigate an issue with our primary database. Ingestion of new data is currently delayed.

    provider

  2. monitoring

    Ingestion of new data has recovered. We are continuing to work with our vendor to better understand the failure and monitor for continued success throughout the day.

    provider

  3. monitoring

    We are continuing to monitor for any further issues.

    provider

  4. monitoring

    We are continuing to monitor for any further issues- alerting is impacted while we work towards a resolution

    provider

  5. resolved

    We are continuing to monitor but systems have returned to normal at this time.

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

Is LogRocket still down?

No, this incident was resolved 2022-03-04 20:44 UTC. For LogRocket's live state, see https://down.guide/logrocket.

How long did it last?

2h 2m, from 2022-03-04 18:42 UTC to 2022-03-04 20:44 UTC, by the times LogRocket posted.

What was affected?

LogRocket named Session Collection, Alerts.

What caused it?

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

Where does this come from?

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