История сбоев Hiver

1. 3 августа 2026 г. в 09:38 UTCidentified

   В настоящее время мы расследуем вопрос, влияющий на синхронизацию электронной почты и назначение электронной почты. Наша инженерная команда активно работает над выявлением первопричины. Мы внимательно следим за ситуацией и предоставим обновленную информацию в течение следующих 30 минут.

2. 3 августа 2026 г. в 09:46 UTCmonitoring

   Мы внедрили исправление и внимательно следим за системой, чтобы все восстановилось, как и ожидалось. Наш главный приоритет - полностью восстановить функциональность, чтобы вы могли продолжать использовать Hiver без сбоев. Мы поделимся нашим следующим обновлением, как только появится больше информации.

3. 3 августа 2026 г. в 09:52 UTCresolved

   Проблема, затрагивающая синхронизацию электронной почты и назначение электронной почты, была решена. Сейчас все сервисы работают в штатном режиме.

Автоматический перевод официального обновления инцидента.

1. 24 июля 2026 г. в 12:01 UTCmonitoring

   В настоящее время мы испытываем сбои в обслуживании, влияющие на Hiver из-за продолжающегося сбоя с Amazon Web Services (AWS), одним из наших поставщиков инфраструктуры. В результате у некоторых пользователей могут возникнуть проблемы с сервисами Hiver. Наша команда активно следит за ситуацией и работает над минимизацией воздействия. Мы предоставим дополнительные обновления по мере поступления дополнительной информации.

2. 24 июля 2026 г. в 12:11 UTCmonitoring

   Мы видим первые признаки восстановления, поскольку сервисы AWS начинают стабилизироваться. Сервисы Hiver также постепенно восстанавливаются. Наша команда продолжает внимательно следить за ситуацией и будет предоставлять дальнейшие обновления, поскольку мы работаем над полным восстановлением сервиса.

3. 24 июля 2026 г. в 13:16 UTCresolved

   Сбои в работе сервиса AWS были устранены, а сервисы Hiver полностью восстановлены. Спасибо за ваше терпение и понимание.

Автоматический перевод официального обновления инцидента.

1. 13 мая 2026 г. в 08:08 UTCinvestigating

   We are currently investigating an issue where some users are unable to change email statuses and assign emails in Hiver for Gmail. Our engineering team is actively working to identify the root cause and restore normal functionality as quickly as possible. We apologize for the inconvenience and will continue to share updates here as we make progress.

2. 13 мая 2026 г. в 08:13 UTCidentified

   We have identified the cause of the issue affecting the ability to change email statuses and assign emails in Hiver for Gmail. Our engineering team is currently working on implementing a fix and restoring full functionality as quickly as possible.

3. 13 мая 2026 г. в 08:16 UTCresolved

   The 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.

1. 4 мая 2026 г. в 15:55 UTCidentified

   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. 4 мая 2026 г. в 16:22 UTCidentified

   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.

3. 4 мая 2026 г. в 17:03 UTCidentified

   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.

4. 4 мая 2026 г. в 17:48 UTCidentified

   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.

5. 4 мая 2026 г. в 17:48 UTCidentified

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

6. 4 мая 2026 г. в 18:39 UTCidentified

   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.

7. 4 мая 2026 г. в 20:47 UTCidentified

   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.

8. 4 мая 2026 г. в 22:05 UTCidentified

   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.

9. 4 мая 2026 г. в 22:47 UTCmonitoring

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

10. 4 мая 2026 г. в 23:51 UTCmonitoring

    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.

11. 5 мая 2026 г. в 01:42 UTCresolved

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

12. 6 мая 2026 г. в 15:49 UTCpostmortem

    # **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.

1. 29 апреля 2026 г. в 15:39 UTCresolved

   On 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.

1. 31 марта 2026 г. в 15:34 UTCinvestigating

   Due to an ongoing Google authorization issue, creating new Shared Mailboxes and reauthorizing Google user or group inboxes is currently unavailable. Our team is actively working with Google to resolve this at the earliest. If you need any assistance, please reach out to [email protected].

2. 1 апреля 2026 г. в 08:02 UTCresolved

   This incident has been resolved.

1. 27 марта 2026 г. в 11:53 UTCidentified

   We’re currently experiencing an issue with email sync in Hiver. Our engineering team is actively investigating and working to resolve this. We’ll share the next update within the next 30 minutes.

2. 27 марта 2026 г. в 12:40 UTCresolved

   We're back! All our Hiver services are up and running now. We thank you for your patience.

1. 18 ноября 2025 г. в 17:12 UTCresolved

   On 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.

1. 6 октября 2025 г. в 16:49 UTCinvestigating

   We are currently investigating issues affecting the performance of Hiver's Activity Panel. Our engineering team is actively working on diagnosing and resolving the problem. We will provide an update within the next 30 minutes.

2. 6 октября 2025 г. в 17:26 UTCinvestigating

   Our engineering team continues to investigate the cause of the degraded performance affecting Hiver’s Activity Panel. We are actively working to identify the root cause and will share the next update within 30 minutes.

3. 6 октября 2025 г. в 17:47 UTCresolved

   We’ve deployed a fix, and all Hiver services are now fully operational. Thank you for your patience while we worked to resolve this issue.

1. 24 сентября 2025 г. в 11:14 UTCidentified

   We’ve received reports from customers in the European region that the Hiver extension isn’t loading. Our engineering team is actively looking into it, and we’ll provide an update within the next 30 minutes.

2. 24 сентября 2025 г. в 11:53 UTCidentified

   The issue with the Hiver extension in the European region has been fully resolved. Services are operating normally, and we truly appreciate your patience and understanding.

3. 24 сентября 2025 г. в 12:53 UTCresolved

   This incident has been resolved.

1. 1 апреля 2025 г. в 14:31 UTCresolved

   On April 1, 2025, at approximately 08:15 AM UTC, Hiver encountered delays in email synchronization, lasting about 45 minutes. Our engineers identified the root cause and fully resolved the issue by 09:00 AM UTC.

1. 25 марта 2025 г. в 09:35 UTCidentified

   We are currently investigating issues with the Hiver extension. Our engineering team is actively working to identify the root cause. The next update will be provided within 30 minutes.

2. 25 марта 2025 г. в 09:52 UTCidentified

   We are actively deploying a fix for the issue with the Hiver extension. Our engineering team is working to resolve this as quickly as possible. We appreciate your patience.

3. 25 марта 2025 г. в 09:53 UTCresolved

   All Hiver services are now fully operational. We thank you for your patience and understanding.

1. 27 января 2025 г. в 10:35 UTCidentified

   We are currently facing issues with Hiver's Chat services. Our top engineers are actively working to diagnose and resolve the problem. We will provide the next update within 30 minutes.

2. 27 января 2025 г. в 10:44 UTCresolved

   The engineering team has successfully resolved the issue. All Hiver services are fully operational. We appreciate your patience and understanding.

1. 7 января 2025 г. в 22:06 UTCinvestigating

   Hiver services are currently experiencing degraded performance. Our engineers are actively working on resolving the issue, and we'll provide an update within the next 30 minutes.

2. 7 января 2025 г. в 22:37 UTCidentified

   We are actively deploying a fix and our engineering team is working diligently to resolve the issue as quickly as possible. We appreciate your patience and will provide further updates shortly.

3. 7 января 2025 г. в 22:56 UTCmonitoring

   We’ve deployed the fix and are actively monitoring the system to ensure there is no further degradation in Hiver’s performance. Our priority is to maintain smooth and uninterrupted service. We’ll provide the next update as soon as it’s available.

4. 7 января 2025 г. в 23:08 UTCresolved

   We’re back! All Hiver services are now fully operational. Thank you for your patience and understanding.

1. 2 января 2025 г. в 13:51 UTCidentified

   We're currently encountering an issue with the Hiver extension. Our top engineers are actively diagnosing the problem, and we will provide the next update within 30 minutes.

2. 2 января 2025 г. в 14:21 UTCresolved

   The issue has been resolved, and all Hiver services are back online. Thank you for your patience.

1. 5 декабря 2024 г. в 15:50 UTCresolved

   The sync process was delayed due to Gmail API failure, impacting operations from 10:30 AM to 11:30 AM GMT. The issue has now been fully resolved, and services are back to normal.

1. 5 декабря 2024 г. в 15:56 UTCresolved

   Hiver's Activity Panel services experienced downtime. The issue is now resolved and services are fully operational.

1. 13 сентября 2024 г. в 16:12 UTCinvestigating

   We are aware of the "Gmail API error" impacting a subset of users and our team is actively investigating it. We will provide the next update in 30 minutes. Thank you for your patience as we work to resolve this matter.

2. 13 сентября 2024 г. в 17:15 UTCresolved

   Hiver services are now fully operational. The issue was caused by Gmail API failures. Thank you for your patience.

1. 1 августа 2024 г. в 11:06 UTCresolved

   Hiver's services are currently experiencing performance degradation. Few users reported delay in loading of Hiver's Activity Panel. This incident occurred between 2:18 PM UTC and 2:41 PM UTC on August 31st. Our engineering team investigated the root cause and a fix has been rolled out.

1. 23 июля 2024 г. в 15:35 UTCidentified

   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. 23 июля 2024 г. в 16:12 UTCidentified

   Our engineers are continuing to investigate the delay in email synchronization. We are actively working on this and are committed to resolving it as quickly as possible. Rest assured, we will provide an update within 30 minutes.

3. 23 июля 2024 г. в 17:03 UTCidentified

   Our engineers are diligently working to resolve the email synchronization issue. Rest assured, we are committed to restoring full functionality as swiftly as possible. We will share another update within the next 30 minutes.

4. 23 июля 2024 г. в 18:09 UTCresolved

   We have deployed the fix and are monitoring the system. All Hiver services are up and running again. We are grateful for your patience and understanding.