Hiver email synchronization is experiencing a downtime.

Update timeline

1. identified May 04, 2026, 03:55 PM UTC

   We are experiencing issues with email synchronization. Our best engineers are continuing to diagnose the issue. We will share the next update within 30 minutes.

2. identified May 04, 2026, 04:04 PM UTC

   We are continuing to work on a fix for this issue.

3. identified May 04, 2026, 04:22 PM UTC

   We’re currently investigating an issue affecting email synchronization. Our engineering team is actively working to identify the root cause and resolve it at the earliest. We’re closely monitoring the situation and will share the next update as soon as possible.

4. identified May 04, 2026, 05:03 PM UTC

   Our engineering team continues to investigate the email synchronization issue. We are making progress in narrowing down the root cause and will share a more detailed update within the next 60 minutes. Thank you for your patience.

5. identified May 04, 2026, 05:48 PM UTC

   We sincerely apologize for the continued disruption. Our engineering team is still actively investigating the email synchronization issue and working with urgency to resolve it. We will continue to share updates here as soon as possible.

6. identified May 04, 2026, 05:48 PM UTC

   We are continuing to work on a fix for this issue.

7. identified May 04, 2026, 06:39 PM UTC

   We recognize the inconvenience this has caused and sincerely regret the disruption. The team is investigating the issue with high priority and working to restore normal service as quickly as possible. Thank you for your continued understanding.

8. identified May 04, 2026, 08:47 PM UTC

   We understand the inconvenience this may have caused and sincerely apologize for the disruption. Our team is actively investigating the issue as a top priority and is working to restore full service at the earliest. We appreciate your patience and understanding.

9. identified May 04, 2026, 10:05 PM UTC

   We recognize the impact this email synchronization issue is having and sincerely apologize for the inconvenience caused. Our engineering team is investigating this as a top priority and remains fully engaged in restoring normal service. We will share the next update as soon as more information becomes available.

10. monitoring May 04, 2026, 10:47 PM UTC

    Email synchronization is currently recovering, and our team is closely monitoring progress to ensure full restoration of functionality.

11. monitoring May 04, 2026, 11:51 PM UTC

    Hiver’s email synchronization is still recovering, and our team continues to monitor progress closely. We will share another update once it is fully restored.

12. resolved May 05, 2026, 01:42 AM UTC

    Hiver’s email synchronization has been fully recovered. All services are up and running.

13. postmortem May 06, 2026, 03:49 PM UTC

    # **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 happened** On May 4, 2026, new incoming emails stopped appearing in Hiver shared inboxes for approximately 6.5 hours. The root cause was an unexpected and severe surge in message queue volume that overwhelmed a core infrastructure component — the Sync Engine — responsible for pulling emails from Gmail into Hiver in real time. Hiver's infrastructure is designed to handle up to 2× our peak traffic at all times. This is one reason we have maintained near-perfect uptime over the past two years. On this occasion, the surge exceeded even that ceiling, bringing the Sync Engine to a near-complete halt. **What we've done immediately** Our engineers have done a deep analysis of this incident. As a remediation step, we have added more elasticity to the message queues infrastructure so that it has more headroom for future surges. We are also committed to migrate additional queues incrementally and completely to the elastic queue infrastructure over the coming weeks. **What we're doing next** Beyond the immediate fixes, we are evaluating several longer-term improvements including faster detection-to-recovery workflows and more granular controls during abnormal volume conditions. We will keep sharing further details on this page as we make progress.