Hive Outage History
9 incidents recorded over the last 365 days, 9 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 Hive Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 22, 2026 | Slow performance across HiveWe are investigating reports of slow performance across Hive starting at about 9:20 AM ET. Pages, actions and updates may load slowly, and some requests may time out. Notifications, webhooks and automations may also be… | 1 min | Resolved |
| Oct 22, 2026 | Application performance bottleneck due to database issuesThis issue has been resolved and Hive is performing normally. Thank you for your patience. | 1h 31m | Resolved |
| Oct 10, 2026 | Weekend maintenance performance degradationThis incident has been resolved. | 1h 14m | Resolved |
| Aug 26, 2026 | Home Page widget loading issuesThis incident has been resolved. | 20 min | Resolved |
| Aug 26, 2026 | Home page and action loading issuesGantt actions loading issue has been resolved. We will be opening a separate incident to track the Home Page loading issue. | 15 min | Resolved |
| Aug 4, 2026 | Degraded Performance across Hive ServicesThis incident has been resolved. | 1h 3m | Resolved |
| Jun 4, 2026 | Delayed transactional emails due to third-party provider issueOn June 2, 2026, some Hive transactional emails were delayed due to an error by our third-party email provider. The provider incorrectly interrupted normal delivery, and limited communication from them slowed… | -2345 min | Resolved |
| Feb 4, 2026 | Infrastructure issuesThis incident has been resolved. | 26 min | Resolved |
| Dec 8, 2025 | DNS issues for UK regionThe incident has been resolved. Availability in known & affected regions is confirmed to be resumed. If you continue to experience issues with loading any hive.com domains, please immediately reach out to help@hive.com… | 6h 23m | 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 Hive 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 Hive 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 Hive 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 Hive outage in this window ran 6h 23m, against a mean recovery of 1h 24m. If you depend on Hive 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.