Regents University London Outage History

6 incidents recorded over the last 365 days, 6 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 Regents University London Incident

Regents University London incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 10, 2026Upcoming system downtime: SITS live environment24h 0mResolved
Oct 20, 2026Open Athens5h 43mResolved
Sep 21, 2026Global Protect (VPN) is rejecting logins1077h 22mResolved
Jul 27, 2026Guest Access Solution - New requests unavailable1571h 38mResolved
Jun 24, 2026SEATS not showing timetables1643h 59mResolved
Jun 2, 2026Emergency Maintenance to Campus Network1h 0mResolved

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 Regents University London 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 Regents University London 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 Regents University London 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 Regents University London outage in this window ran 68d 11h, against a mean recovery of 30d. If you depend on Regents University London 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.