Live
L

LogRocket

LogRocket is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

3 h 40 min

Longest incident

3 h 40 min

Components

13
Session Collection Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
MCP Operational
90 days agoNo incidentsToday
Timeline Operational
90 days agoNo incidentsToday
Issues Operational
90 days ago1 day with an incidentToday
Metrics Operational
90 days ago1 day with an incidentToday
Alerts Operational
90 days ago1 day with an incidentToday
Streaming Data Export Operational
90 days agoNo incidentsToday
Auth0 User Authentication Operational
90 days agoNo incidentsToday
Auth0 Multi-factor Authentication Operational
90 days agoNo incidentsToday

Integrations

Slack Integration Operational
90 days agoNo incidentsToday
GitHub Integration Operational
90 days agoNo incidentsToday
Intercom Integration Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=logrocket
Slack
/feed subscribe https://outages.cc/feed.xml?providers=logrocket

Go from tracking outages to fixing production issues with Polylane.

Try Polylane