Analytics Ingestion Delays
This incident has been resolved.
The latest update from LogRocket.
State
Resolved
Started
8 d ago
2026-10-24 16:12 UTC
Lasted
3 h 40 min
until 2026-10-24 19:51 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 55 min 53%
Monitoring
1 h 44 min 47%
Updates
Times in UTCAs posted by LogRocket
This incident has been resolved.
We have cleared the bottleneck and our queues are draining.
We are investigating an elevated queue backlog in our analytics ingestion system.
Affected components
3LogRocket in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
3 h 40 min
This incident
About the median
Follow LogRocket
Your coding agent knows when LogRocket is down, and tells you when a failure is theirs, not yours. You can also get LogRocket incidents in a feed reader or in Slack.
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.cc/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 "logrocket" and tell me if LogRocket 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.
https://outages.cc/feed.xml?providers=logrocket/feed subscribe https://outages.cc/feed.xml?providers=logrocketFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane