Roomote Outage History

9 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Roomote Incident

Roomote incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jun 3, 2026Intermittent errors starting tasksThis incident has been resolved.52 minResolved
May 26, 2026Authentication service outageThis incident has been resolved.53 minResolved
Apr 27, 2026Tasks failing to startThis incident has been resolved.6h 14mResolved
Apr 16, 2026Tasks failing to startThis incident has been resolved.5h 3mResolved
Feb 24, 2026Authentication issues with Roo Code RouterThis incident has been resolved.18 minResolved
Feb 19, 2026Authentication service outage on Roo Code CloudThis incident has been resolved.2h 2mResolved
Feb 12, 2026Database outageThis incident has been resolved.4h 34mResolved
Feb 3, 2026Cloud jobs failing to startThe upstream provider has resolved their issue and cloud jobs are starting normally.3h 5mResolved
Jan 6, 2026Cloud jobs failing to startThis incident has been resolved.9h 10mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Roomote incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Roomote Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Roomote acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Roomote outage in this window ran 9h 10m, against a mean recovery of 3h 35m. If you depend on Roomote in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.