Campus Labs Outage History

10 incidents recorded over the last 365 days, 10 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 Campus Labs Incident

Campus Labs incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 10, 2026Unable to act on Event or Registration SubmissionsThis incident has been resolved.19h 44mResolved
Aug 14, 2026ECIA Application unable to locate EventsThis incident has been resolved.651h 37mResolved
Jul 29, 2026Timeouts when connecting to SFTP serverThe issue with {issue} in {area/product} was resolved as of approximately {time} and no further incidents have been reported.381h 44mResolved
Jul 23, 2026Site Performance and Navigation IssuesThis incident has been resolved.22h 58mResolved
Jul 6, 2026Baseline Performance IssuesThis incident has been resolved.19h 36mResolved
Jun 16, 2026Site Performance and Navigation IssuesSome users are experiencing intermittent connectivity issues following a recent domain registrar transfer. During a brief window in the transfer process, we believe some DNS resolvers cached incorrect nameserver…1h 12mResolved
Jun 16, 2026Site Performance and Navigation IssuesThis incident has been resolved.3h 11mResolved
May 14, 2026Investigating IssueThis incident has been resolved.93h 19mResolved
Feb 16, 2026Error message when viewing some standardsThe Accreditation standards and Credentials Rosters are now loading as expected.43h 35mResolved
Nov 18, 2025Investigating IssueThe issue with Engage access has been resolved and no further incidents have been reported.341h 54mResolved

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 Campus Labs 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 Campus Labs 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 Campus Labs 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 Campus Labs outage in this window ran 27d 3h, against a mean recovery of 6d 13h. If you depend on Campus Labs 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.