Hub360 Outage History
3 incidents recorded over the last 365 days, 1 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 Hub360 Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Hub360 MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Sep 25, 2026 | Hub360 Upstream Unhealthy IssueHub360 and all associated services are fully operational. A comprehensive Root Cause Analysis (RCA) is currently being conducted. Once completed, the RCA will be available upon request through our Support team. | 1h 57m | Resolved |
| Sep 23, 2026 | Hub360 Planned MaintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 Hub360 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 Hub360 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 Hub360 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 Hub360 outage in this window ran 1h 57m, against a mean recovery of 1h 19m. If you depend on Hub360 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.