Is LogRocket Down?
- LogRocket's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 7 of 7 regions · 146 ms
Right now
The verdict is the worse of these two. How we decide
LogRocket's status page
status.logrocket.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Session Collection | Operational |
| Dashboard | Operational |
| MCP | Operational |
| Timeline | Operational |
| Issues | Operational |
| Metrics | Operational |
| Alerts | Operational |
| Streaming Data Export | Operational |
| Auth0 User Authentication | Operational |
| Auth0 Multi-factor Authentication | Operational |
| Slack Integration | Operational |
| GitHub Integration | Operational |
1 more, all operational · show all 13
| Component | Status |
|---|---|
| Session Collection | Operational |
| Dashboard | Operational |
| MCP | Operational |
| Timeline | Operational |
| Issues | Operational |
| Metrics | Operational |
| Alerts | Operational |
| Streaming Data Export | Operational |
| Auth0 User Authentication | Operational |
| Auth0 Multi-factor Authentication | Operational |
| Integrations | |
| Slack Integration | Operational |
| GitHub Integration | Operational |
| Intercom Integration | Operational |
FlareWarden checks
logrocket.com from 7 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 7 of 7
- Response
- 146 ms
- Checked
By region
- Dallas reachable, 171 ms
- Frankfurt reachable, 166 ms
- Newark reachable, 166 ms
- Paris reachable, 156 ms
- Stockholm reachable, 100 ms
- Sydney reachable, 105 ms
- Toronto reachable, 163 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Dallas | 76 ms | 1 ms | 8 ms | 168 ms |
| Frankfurt | 28 ms | 2 ms | 9 ms | 162 ms |
| Newark | 84 ms | 2 ms | 11 ms | 160 ms |
| Paris | 18 ms | 2 ms | 9 ms | 151 ms |
| Stockholm | 12 ms | 1 ms | 9 ms | 96 ms |
| Sydney | 8 ms | 1 ms | 8 ms | 101 ms |
| Toronto | 59 ms | 1 ms | 7 ms | 159 ms |
History
Incidents LogRocket reported
Since Oct 22, 16 days · from status.logrocket.com
- Incidents
- 1
- Major or critical
- 0
- Median to resolve
- 3h 39m
- lasted 3h 39m
minor ·
LogRocket website availability
Measured by FlareWarden · logrocket.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 205ms
Last 30 days
80-day clean streakMeasured by FlareWarden's own checks of logrocket.com from multiple regions every 6 hours. LogRocket's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 80 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What LogRocket does
LogRocket records what users actually did in a web or mobile application: session replay paired with console logs, network requests and errors, plus product analytics and alerting. Engineering and support teams use it to reproduce a bug from the user's side rather than from a stack trace alone, and to see where people abandon a flow.
What an outage looks like
The dashboard fails to load, or sessions stop appearing so recent activity looks like a drop in traffic. Session collection problems mean recordings for that window never arrive and cannot be recovered later. Timeline and Issues views fail to open replays. Alerts stop firing, and the Slack, GitHub and Intercom integrations stop posting. Login through the authentication provider may fail.
What to do about it
status.logrocket.com separates Session Collection from the Dashboard, Timeline, Issues, Metrics, Alerts, Streaming Data Export, the integrations and authentication. Collection is the one that matters most: sessions missed during an incident are gone, so note the window and avoid drawing conclusions from it afterwards. If Alerts is degraded, watch your other error monitoring rather than reading quiet as healthy.
Is it down for everyone, or just you?
If this page says LogRocket is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
LogRocket outage FAQ
Our session count dropped. Did traffic fall?
Can we recover sessions from the outage window?
Alerts went quiet. Is our application healthy?
Is LogRocket down or is our snippet broken?
How we measure this
- We request LogRocket's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 7 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where LogRocket publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of LogRocket itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when LogRocket goes down
We check LogRocket every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring