Hivebrite 장애 기록

1. 2026년 10월 13일 오전 6:42 UTCinvestigating

   우리는 현재 사건을 조사하고 있습니다. 우리의 팀은 원인을 확인하고 영향을 평가하기 위해 노력하고 있습니다. 업데이트는 더 많은 정보를 수집합니다. 감사합니다.

2. 2026년 10월 13일 오전 6:43 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 10월 13일 오전 7:03 UTCmonitoring

   우리는 사건에서 회복했습니다. 우리는 상황을 완전히 해결하기 위해 밀접하게 감시를 지킵니다. 업데이트가 따릅니다. 감사합니다.

4. 2026년 10월 13일 오전 10:38 UTCresolved

   사건이 해결되었습니다. 수정은 미래 발생을 방지하기 위해 구현되었습니다. 지원 및 이해에 감사드립니다. 추가 질문이 있으시면 지원 팀에 문의하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 24일 오전 7:05 UTCresolved

   Our platform briefly experienced technical issues between 8:38am CEST and 8:50am CEST. The incident prevented access to our platform during the period of time. There were no impact on your data. We apologize for the inconvenience and thank you for your understanding.

1. 2026년 6월 10일 오후 3:38 UTCidentified

   We have identified an incident impacting the computation of Engagement Scoring on our European platform. Information displayed in the platform, pertaining to Engagement Scoring, may not be up to date, a delay can be observed before it is refreshed. Our team is working on identifying the cause and assessing the impact. Updates will follow as we gather more information. Thank you for your patience.

2. 2026년 6월 11일 오후 3:15 UTCmonitoring

   A fix has been implemented and deployed. We're catching up on the computation of Engagement Scoring events. Delay can still be observed on Engagement Scoring value for users. Updates will follow as we process Engagement Scoring events. Thank you for your patience.

3. 2026년 6월 11일 오후 4:52 UTCresolved

   The incident has been resolved. Engagement Scoring are now live and synchronized.

1. 2026년 5월 22일 오후 3:48 UTCidentified

   We are currently aware of an incident preventing our customers from configuring, setting or updating their Custom Domain. There is no impact to access the platform or the security of the data. This is linked to the incident from one of our vendor (https://www.cloudflarestatus.com/incidents/znll7lfnd35h). We will update this incident once we have more information from our vendor. Thank you for your patience.

2. 2026년 5월 22일 오후 8:07 UTCresolved

   The incident has been resolved. Please reach out to our support team if you have additional questions.

1. 2026년 4월 3일 오후 2:24 UTCidentified

   We have identified a latency issue affecting a part of our services. We are actively working on resolving it. Updates will be provided as progress is made. Thank you for your understanding

2. 2026년 4월 3일 오후 4:05 UTCidentified

   We are actively working on resolving the latency issue. Updates will be provided as progress is made. Thank you for your understanding.

3. 2026년 4월 3일 오후 6:28 UTCmonitoring

   Optimizations have been implemented to minimize impact. The latency issue is being closely monitored. Updates will follow as we track the situation. Thank you for your patience and support.

4. 2026년 4월 3일 오후 6:37 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026년 4월 3일 오후 8:45 UTCinvestigating

   The latency issue has been resolved. Thank you for your understanding and cooperation. If you encounter further issues, please contact our support team.

6. 2026년 4월 4일 오전 5:02 UTCresolved

   This incident has been resolved.

1. 2026년 3월 30일 오전 7:21 UTCidentified

   We have identified a latency issue affecting our services. We are actively working on resolving it. Updates will be provided as progress is made. Thank you for your understanding.

2. 2026년 3월 30일 오전 10:31 UTCresolved

   The latency issue has been resolved. Thank you for your understanding and cooperation. If you encounter further issues, please contact our support team.

1. 2026년 2월 19일 오후 5:25 UTCresolved

   Our platform experienced technical issues, preventing most of our users and admins from accessing the platform, starting 11:02 CET today. We detected the incident shortly after. We identified the cause of the incident and successfully implemented mitigation measures at 11:35 CET. The platform was back online shortly after, all systems were fully working at 11:36 CET. Thank you for your support and understanding. Please reach out to our support team if you have additional questions.

1. 2026년 1월 22일 오후 5:03 UTCinvestigating

   We are experiencing an issue with our third-party handling our support tickets. We are currently investigating the issue. If you have any urgent tickets to create for now, please contact your CSM.

2. 2026년 1월 22일 오후 5:58 UTCresolved

   This incident has been resolved. You can submit tickets to our support team as usual. Thank you for your understanding.

1. 2025년 11월 27일 오후 2:06 UTCmonitoring

   Our platform is currently experiencing technical issues that are preventing users and admins from accessing the platform. There is no impact to existing customer data. The incident started at 14:40 CET. We have already identified the cause of the incident and are working on the resolution. We apologize for the inconvenience. Updates will be provided as progress is made. Thank you for your understanding.

2. 2025년 11월 27일 오후 2:09 UTCmonitoring

   We have recovered from the incident. We keep monitoring closely to make sure the situation is fully resolved. Updates will follow. Thank you for your cooperation.

3. 2025년 11월 27일 오후 2:21 UTCresolved

   The incident has been resolved. Thank you for your support and understanding. Please reach out to our support team if you have additional questions.

1. 2025년 11월 18일 오전 11:52 UTCidentified

   Our platform is currently experiencing technical issues that can prevent users and admins from accessing the platform. There is no impact to existing customer data. We have identified the root cause of the issue, linked to one of our third-party (https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). We apologize for the inconvenience and are working to resolve this as soon as possible.

2. 2025년 11월 18일 오후 2:54 UTCmonitoring

   Our third-party is recovering from their outage. Our platforms are coming back up online as well since 3:36pm CET. We keep monitoring closely to make sure the situation is fully resolved. Updates will follow. Thank you for your cooperation.

3. 2025년 11월 18일 오후 8:39 UTCresolved

   The incident has been resolved. Thank you for your support and understanding. Please reach out to our support team if you have additional questions.

1. 2025년 11월 17일 오후 4:40 UTCinvestigating

   Our platform is currently experiencing technical issues that are preventing users and admins from accessing our US sandbox. There is no impact to existing customer data. We apologize for the inconvenience and are working to resolve this as soon as possible.

2. 2025년 11월 17일 오후 5:20 UTCidentified

   We have identified the cause of the incident and are working on the resolution. Updates will be provided as progress is made. Thank you for your understanding.

3. 2025년 11월 17일 오후 5:42 UTCidentified

   The synchronization between our search engine and the database is stopped. A fix will be implemented tomorrow morning (before 12:00PM CET).

4. 2025년 11월 18일 오전 10:33 UTCmonitoring

   We have recovered from the incident. We keep monitoring closely to make sure the situation is fully resolved. Updates will follow. Thank you for your cooperation.

5. 2025년 11월 18일 오후 8:39 UTCresolved

   The incident has been resolved. Fixes have been implemented to prevent future occurrences. Thank you for your support and understanding. Please reach out to our support team if you have additional questions.

1. 2025년 10월 28일 오전 9:58 UTCinvestigating

   We are currently investigating a latency issue affecting our services. Updates will follow as we work to identify the cause and assess the impact. Thank you for your patience.

2. 2025년 10월 28일 오전 10:52 UTCmonitoring

   Optimizations have been implemented to minimize impact. The latency issue is being closely monitored. Updates will follow as we track the situation. Thank you for your patience and support.

3. 2025년 10월 28일 오후 2:54 UTCinvestigating

   The latency issue has been resolved. Thank you for your understanding and cooperation. If you encounter further issues, please contact our support team.

4. 2025년 10월 28일 오후 4:38 UTCresolved

   The incident has been resolved. Fixes have been implemented to prevent future occurrences. Thank you for your support and understanding. Please reach out to your CSM if you have additional questions.

1. 2025년 10월 20일 오후 1:01 UTCinvestigating

   Our platform is currently experiencing technical issues on multiple features (delays and errors in dispatching emails, embedding content) following a third-party outage, since 9.11am Oct 20. There is no impact to existing customer data. We apologize for the inconvenience and are working to resolve this as soon as possible.

2. 2025년 10월 21일 오전 8:31 UTCresolved

   The incident has been resolved. Our third-party has mitigated their outage issue. Thank you for your support and understanding. Please reach out to your CSM if you have additional questions.

1. 2025년 10월 15일 오전 10:07 UTCidentified

   Our platform has suffered technical issues that prevented a portion of our users and admins from accessing the platform. There is no impact to existing customer data. Users and admins may have been unsuccesful in using the platform between: - October 14th, 10:30pm CEST and 11:00pm CEST; - October 15th, 1:35am CEST and 2:20am CEST. We have identified the cause of the incident, have already deployed mitigation measures and are still working on the resolution of the incident. Updates will be provided as progress is made. Thank you for your understanding. We apologize for the inconvenience and are working to resolve this as soon as possible.

2. 2025년 10월 15일 오후 12:18 UTCmonitoring

   We have recovered from the incident. We keep monitoring closely to make sure the situation is fully resolved. Updates will follow. Thank you for your cooperation.

3. 2025년 10월 16일 오전 8:04 UTCresolved

   The incident has been resolved. Fixes have been implemented to prevent future occurrences. Thank you for your support and understanding. Please reach out to your CSM if you have additional questions.

1. 2025년 6월 12일 오전 9:48 UTCinvestigating

   Our platform is currently experiencing technical issues that are preventing users and admins from accessing the platform. There is no impact to existing customer data. We apologize for the inconvenience and are working to resolve this as soon as possible.

2. 2025년 6월 12일 오전 9:53 UTCidentified

   We have identified the cause of the incident and are working on the resolution. Updates will be provided as progress is made. Thank you for your understanding.

3. 2025년 6월 12일 오전 10:10 UTCmonitoring

   We have recovered from the incident. We keep monitoring closely to make sure the situation is fully resolved. Updates will follow. Thank you for your cooperation.

4. 2025년 6월 12일 오후 12:52 UTCresolved

   The incident has been resolved. Fixes have been implemented to prevent future occurrences. Thank you for your support and understanding. Please reach out to your CSM if you have additional questions.

1. 2025년 6월 3일 오전 9:49 UTCidentified

   Our platform is currently experiencing technical issues that are preventing users and admins from accessing the platform. There is no impact to existing customer data. We have identified the cause of the incident and are working on the resolution. We apologize for the inconvenience.

2. 2025년 6월 3일 오전 10:53 UTCmonitoring

   We have recovered from the incident. We keep monitoring closely to make sure the situation is fully resolved. Updates will follow. Thank you for your cooperation.

3. 2025년 6월 3일 오후 1:01 UTCresolved

   The incident has been resolved. Fixes have been implemented to prevent future occurrences. Thank you for your support and understanding. Please reach out to your CSM if you have additional questions.

1. 2025년 5월 27일 오후 3:37 UTCinvestigating

   We are currently investigating the incident. Our team is working on identifying the cause and assessing the impact. Updates will follow as we gather more information. Thank you for your patience.

2. 2025년 5월 27일 오후 4:33 UTCidentified

   We have identified the cause of the incident and are working on the resolution. Updates will be provided as progress is made. Thank you for your understanding.

3. 2025년 5월 27일 오후 4:43 UTCmonitoring

   We have recovered from the incident. We keep monitoring closely to make sure the situation is fully resolved. Updates will follow. Thank you for your cooperation.

4. 2025년 5월 27일 오후 5:07 UTCresolved

   The incident has been resolved. Thank you for your support and understanding. Please reach out to your CSM if you have additional questions.

1. 2025년 2월 28일 오후 5:49 UTCidentified

   You might have noticed a lower quality in your header logo image. We have identified the root cause. The situation should be solved on Monday. There is no loss of data. Workaround meanwhile: you can reupload a logo if it is not ok to wait for Monday. Thank you for your understanding.

2. 2025년 3월 3일 오후 8:01 UTCidentified

   Fix was uploaded on sandboxes. We will rollout it to production environments tomorrow. The workaround is still valid while waiting for it: you can reupload a logo with a higher quality. Thank you for your patience.

3. 2025년 3월 5일 오후 5:30 UTCresolved

   This incident has been resolved.

1. 2025년 1월 24일 오후 10:52 UTCresolved

   Between 17:45 and 18:06 Jan 22 (in French time), there was a significant occurrence of 500 errors affected all US production customers, causing service disruptions.

2. 2025년 1월 24일 오후 10:53 UTCpostmortem

   Dear customer, You recently faced an incident on our services. We understand the impact this may have had on your experience and thus want to explain what happened. ## Incident Overview | INCIDENT PROPERTIES | | | --- | --- | | Started | Jan 22, 2025 04:45 pm UTC | | Impact Ended | Jan 22, 2025 05:06 pm UTC | | Impact Duration | 1 minutes | | Environment | Usprod | ## What Happened Between 2025-01-22T16:40:00 and 2025-01-22T17:06:00, customers on the US production platform experienced a large number of 500 errors. This was due to two simultaneous overloads of activity at the same time. 1. A large campaign led to security bot scanning flooding the platform. This is a known issue that occurs regularly and leads to repetitive micro outages \(<1minute\). 2. A big event in a wide community led to an additonnal surge of traffic. In usual times, this would not have been an issue but added to the first event, it led to such a long service disruption. ## Preventive Measures We have identified the security bot scanning issue 2 months ago and have our teams working on a long-term fix targeted for Q1 2025. We also are working to improve our autoscaling, our app bootime and our caching of public pages. This will allow our platform to reach better performance, scalability and more particularly reliability. We sincerely appreciate your understanding and are committed to continually improving our services to deliver a more resilient and reliable experience. If you have any lingering questions, do not hesitate to reach out to your CSM or our support team. Sincerely, Hivebrite

1. 2024년 12월 23일 오후 8:42 UTCinvestigating

   Our platform is currently experiencing technical issues that are preventing users and admins from accessing the platform. There is no impact to existing customer data. We apologize for the inconvenience and are working to resolve this as soon as possible.

2. 2024년 12월 23일 오후 8:45 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 12월 23일 오후 8:46 UTCidentified

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

4. 2024년 12월 23일 오후 8:49 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2024년 12월 24일 오전 10:30 UTCresolved

   The incident has been resolved. Please reach out to your CSM if you have any questions.

6. 2024년 12월 24일 오후 2:43 UTCpostmortem

   Dear customer, ## Incident Overview Our platform experienced an unexpected incident that prevented you from accessing Hivebrite for several minutes. We sincerely apologize for the inconvenience and here are more details on the incident. | INCIDENT PROPERTIES | | | --- | --- | | **Started** | Dec 23, 2024 08:26 pm UTC | | **Impact Ended** | Dec 23, 2024 08:49 pm UTC | | **Impact Duration** | 23 minutes | | **Environment** | prod | ## What Happened Our traffic handler that manages redirection to our marketing website URLs was not configured properly. Because of that, in case of worldwide high traffic, it loses the connection with our server. We had identified the issue a few weeks ago and were planning a maintenance window in January to correct it. Everything was ready for the resolution. We thought there would be no issue to wait as much as this configuration existed for one year and a half and it had never led to any issue until now. However, the probabilities went against us. ## Impact on You There was no data loss and there is no long lasting impact after this incident. ## What was done Thanks to everything being already ready, the team could react and correct the behaviour straightaway. The infrastructure has been corrected during the incident. It will not reoccur. We sincerely appreciate your patience and understanding during this time. We are committed to continually improving our services to deliver a more resilient and reliable experience. If you have any lingering concerns or questions, please do not hesitate to reach out to your CSM or our support team. Sincerely, Hivebrite