Hiver Outage History
11 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 Hiver Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | Hiver service disruption due to AWS outageAll our Hiver services are up and running now. We thank you for your patience. | 7 min | Resolved |
| Aug 3, 2026 | Hiver email synchronisation and email assignment are currently impactedThe issue affecting email synchronisation and email assignment has been resolved. All services are now operating normally. | 14 min | Resolved |
| Aug 2, 2026 | Hiver Scheduled MaintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 24, 2026 | Hiver service disruption due to AWS outageThe AWS service disruption has been resolved, and Hiver services have fully recovered. Thank you for your patience and understanding. | 1h 15m | Resolved |
| May 13, 2026 | Unable to Change Status and Assign Emails in Hiver for GmailThe issue affecting the ability to change email statuses and assign emails in Hiver for Gmail has now been resolved. Our engineering team has implemented the fix, and services are operating normally again. | 8 min | Resolved |
| May 4, 2026 | Hiver email synchronization is experiencing a downtime.# **Incident postmortem: Email Sync Delay in Shared Inboxes** > Total downtime > > **6.5 hrs** > > Uptime in May 2026 > > **98.95%** > > Prior 12-month avg uptime of Hiver Services > > **≈ 99.98%** **What… | 7h 53m | Resolved |
| Apr 28, 2026 | Hiver's Chat services downtimeOn April 28th at 3:05 PM UTC, Hiver faced an issue with Chat services, which lasted for about 43 minutes. Our engineers quickly identified the cause and the issue was fully resolved by 3:48 PM UTC. | 0 min | Resolved |
| Mar 31, 2026 | Shared Mailbox Creation Temporarily UnavailableThis incident has been resolved. | 16h 27m | Resolved |
| Mar 27, 2026 | Hiver sync services are experiencing a downtime.We're back! All our Hiver services are up and running now. We thank you for your patience. | 46 min | Resolved |
| Feb 22, 2026 | Hiver Scheduled MaintenanceThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Nov 18, 2025 | Hiver's Automation services downtimeOn November 18th at 6:30 AM UTC, Hiver faced an issue with Automation services, which lasted for about 1 hour 30 minutes. Our engineers quickly identified the cause and the issue was fully resolved by 8:00 AM UTC. | -642 min | 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 Hiver 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 Hiver 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 Hiver 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 Hiver outage in this window ran 16h 27m, against a mean recovery of 3h 2m. If you depend on Hiver 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.