Breathe 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 Breathe Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Learn Emergency MaintenanceEssential maintenance on the Breathe Learn platform has completed successfully. | 3h 27m | Resolved |
| Oct 21, 2026 | Rota Emergency MaintenanceBreathe Rota, Time & Attendance essential maintenance has now been completed and access has been restored. | 4h 6m | Resolved |
| Aug 5, 2026 | Breathe Login IssuesThis incident has been resolved. | 16h 42m | Resolved |
| Jul 28, 2026 | Service disruption: Login unavailableResolved — This incident has been resolved. The fix applied to our login services has been verified, and all users can now log into Breathe normally. Thank you for your patience while we addressed this issue. | 1h 27m | Resolved |
| Feb 5, 2026 | Issue accessing expenses documentsThis incident has been resolved. | 25h 31m | Resolved |
| Jan 19, 2026 | RTA and Mobile app affected by slow loading times and "something went wrong" errorStatus: Fully Resolved Resolution Time: 13:41 GMT We have confirmed that all systems are functioning normally and the earlier issues affecting Rota, Time, and Attendance and the Mobile App have been fully… | 2h 8m | Resolved |
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 Breathe 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 Breathe 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 Breathe 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 Breathe outage in this window ran 1d 1h, against a mean recovery of 8h 54m. If you depend on Breathe 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.