Robin Outage History

14 incidents recorded over the last 365 days, 11 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.

Live Robin status100.00% uptime history

Every Recorded Robin Incident

Robin incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 1, 2026Dashboard loading issueThe Robin Dashboard is now loading17 minResolved
Sep 16, 2026Dashboard Login FailuresThis incident has been resolved.34 minResolved
Jul 14, 2026Dashboard loading issueThis incident has been resolved.2h 51mResolved
Jun 12, 2026Robin dashboard and map loading issuesThis incident has been resolved.1h 7mResolved
Jun 1, 2026Dashboard Loading IssueWe've pushed out a fix for the dashboard issue and the platform is working as expected.38 minResolved
Mar 21, 2026US Datacenter MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Mar 17, 2026Dashboard Login FailuresThis incident has been resolved.2h 57mResolved
Mar 12, 2026Dashboard login issueThis incident has been resolved.1h 30mResolved
Mar 10, 2026Dashboard login issueThis incident has been resolved.3h 7mResolved
Mar 3, 2026Slow loading in US Data CenterThis incident has been resolved.2h 20mResolved
Feb 26, 2026Unable to book desksThis incident has been resolved.1h 4mResolved
Feb 19, 2026SAML Login IssueThis incident has been resolved.24 minResolved
Dec 20, 2025US Data Center MaintenanceThe scheduled maintenance has been completed.10h 0mScheduled
Dec 4, 2025EU Datacenter maintenanceThe scheduled maintenance has been completed.8h 0mScheduled

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 Robin 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 Robin 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 Robin 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 Robin outage in this window ran 10h, against a mean recovery of 2h 46m. If you depend on Robin 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.