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

1. 24 августа 2026 г. в 22:52 UTCinvestigating

   В настоящее время мы работаем над решением вопросов с панельными коммуникациями. События и команды панели могут не обрабатываться нормально.

2. 24 августа 2026 г. в 23:08 UTCidentified

   В настоящее время мы работаем над решением вопросов с панельными коммуникациями. События и команды панели могут не обрабатываться нормально.

3. 24 августа 2026 г. в 23:10 UTCresolved

   Это был короткий перерыв, который с тех пор восстановился. Сервис работает нормально.

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

1. 24 августа 2026 г. в 15:44 UTCinvestigating

   В настоящее время мы работаем над решением вопросов с панельными коммуникациями. События и команды панели могут не обрабатываться нормально.

2. 24 августа 2026 г. в 16:28 UTCresolved

   Этот инцидент был урегулирован.

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

1. 22 августа 2026 г. в 13:56 UTCinvestigating

   В настоящее время мы работаем над решением вопросов с панельными коммуникациями. События и команды панели могут не обрабатываться нормально.

2. 22 августа 2026 г. в 16:03 UTCresolved

   Этот инцидент был урегулирован.

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

1. 16 июля 2026 г. в 17:13 UTCresolved

   Для API Brivo были восстановлены обычные операции. Недавно было сделано обновление, которое заставило API вернуть 400 ошибок Bad Request для запросов, содержащих дополнительные, неподдерживаемые параметры запроса. Мы отступили, чтобы ваши ранее успешные запросы продолжали работать, как ожидалось. Инцидент произошел с 3:30 утра до 5:20 вечера по восточному времени.

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

1. 1 июня 2026 г. в 18:24 UTCinvestigating

   We are currently investigating issues logging into Brivo applications.

2. 1 июня 2026 г. в 19:00 UTCidentified

   Brivo Login is currently affected by an outage at one of our service providers. Brivo operations is monitoring the situation and coordinating with our partner to restore service as soon as possible. The issue has been identified and a fix is being implemented.

3. 1 июня 2026 г. в 19:19 UTCmonitoring

   A fix has been implemented by the service provider, and we are monitoring the results.

4. 1 июня 2026 г. в 19:41 UTCresolved

   This incident has been resolved.

1. 29 мая 2026 г. в 15:37 UTCidentified

   Assigning new mobile passes is currently affected by an outage at one of our service providers. Brivo operations is monitoring the situation and coordinating with our partner to restore service as soon as possible.

2. 29 мая 2026 г. в 23:17 UTCresolved

   This incident has been resolved.

1. 21 мая 2026 г. в 15:10 UTCidentified

   We are currently working on resolving issues with panel communications. Events and panel commands may not be processing normally.

2. 21 мая 2026 г. в 15:22 UTCmonitoring

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

3. 21 мая 2026 г. в 15:25 UTCresolved

   This incident has been resolved.

1. 14 мая 2026 г. в 16:38 UTCidentified

   We are currently working on resolving issues with panel communications. Events and panel commands may not be processing normally.

2. 14 мая 2026 г. в 16:42 UTCmonitoring

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

3. 14 мая 2026 г. в 18:03 UTCresolved

   This incident has been resolved.

1. 13 мая 2026 г. в 20:54 UTCinvestigating

   We are currently investigating tenant synchronization issues with some Entrata properties.

2. 13 мая 2026 г. в 21:08 UTCresolved

   This is a configuration issue

1. 1 мая 2026 г. в 17:28 UTCidentified

   We are currently working to resolve issues with Brivo Smart Home email communications. Customers may experience delays in receiving emails from Brivo Smart Home. This incident does not impact Brivo Access or Eagle Eye video.

2. 1 мая 2026 г. в 22:40 UTCresolved

   This incident has been resolved.

1. 24 апреля 2026 г. в 00:04 UTCinvestigating

   We are currently investigating issues with our API. Integrations and our Mobile Applications may not be performing normally.

2. 24 апреля 2026 г. в 00:25 UTCresolved

   This incident has been resolved.

1. 17 апреля 2026 г. в 05:35 UTCinvestigating

   We are currently working on resolving issues with Brivo Smart Home. Users may experience latency or difficulty accessing Brivo Smart Home at this time.

2. 17 апреля 2026 г. в 06:05 UTCidentified

   We are currently working on resolving issues with Brivo Smart Home. Users may experience latency or difficulty accessing Brivo Smart Home at this time.

3. 17 апреля 2026 г. в 06:09 UTCmonitoring

   We have taken steps to resolve this issue and we are continuing to monitor the results.

4. 17 апреля 2026 г. в 06:11 UTCresolved

   This incident has been resolved.

1. 14 апреля 2026 г. в 17:42 UTCinvestigating

   We are currently investigating reports of increased errors with Brivo Security Suite and other Brivo services.

2. 14 апреля 2026 г. в 18:21 UTCidentified

   The issue has been identified, and we are implementing a fix.

3. 14 апреля 2026 г. в 18:33 UTCmonitoring

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

4. 14 апреля 2026 г. в 18:37 UTCresolved

   This incident has been resolved.

1. 23 марта 2026 г. в 13:24 UTCidentified

   We are currently working on resolving issues with panel communications. Events and panel commands may not be processing normally.

2. 23 марта 2026 г. в 14:21 UTCmonitoring

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

3. 23 марта 2026 г. в 14:47 UTCresolved

   This incident has been resolved

1. 11 марта 2026 г. в 09:29 UTCinvestigating

   We are currently working on resolving issues with Brivo Smart Home. Users may experience latency or difficulty accessing Brivo Smart Home at this time.

2. 11 марта 2026 г. в 09:55 UTCidentified

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

3. 11 марта 2026 г. в 10:04 UTCmonitoring

   We have taken steps to resolve this issue and we are continuing to monitor the results. Some degradation of performance on Brivo Smart Home may be experienced at this time.

4. 11 марта 2026 г. в 11:18 UTCresolved

   This incident has been resolved.

1. 9 марта 2026 г. в 18:09 UTCidentified

   We are aware that some panels are not following Daylight Savings Time. The issue has been identified, and a fix is being implemented.

2. 9 марта 2026 г. в 21:05 UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. 9 марта 2026 г. в 23:26 UTCresolved

   This incident has been resolved

1. 5 марта 2026 г. в 20:27 UTCresolved

   From 11:03AM to 12:57PM, Administrators with custom roles were unable to use Brivo Access.

1. 3 марта 2026 г. в 19:39 UTCinvestigating

   We are currently experiencing issues with our toll-free numbers. Brivo Customer Care is still available through our interactive chat or by calling 855-500-0027. We apologize for the inconvenience.

2. 3 марта 2026 г. в 22:22 UTCresolved

   All toll-free numbers have been restored and are once again available to customers and resellers. Thank you for your patience.

1. 18 февраля 2026 г. в 12:20 UTCidentified

   We are currently addressing an issue preventing new users from redeeming their Brivo Mobile Pass in the EU region. Other Brivo Mobile Pass functionality, including unlocking doors in the EU region or redeeming new Passes in the US region, is unaffected at this time.

2. 18 февраля 2026 г. в 13:46 UTCmonitoring

   We have taken steps to resolve this issue and we are continuing to monitor the results.

3. 18 февраля 2026 г. в 14:26 UTCresolved

   This incident has been resolved.

1. 21 января 2026 г. в 07:44 UTCinvestigating

   We are currently working on resolving issues with Brivo Access. Users may experience latency or difficulty accessing Brivo Access at this time.

2. 21 января 2026 г. в 07:45 UTCidentified

   We are currently working on resolving issues with Brivo Access. Users may experience latency or difficulty accessing Brivo Access at this time.

3. 21 января 2026 г. в 09:36 UTCidentified

   We continue to work on resolving issues with Brivo Access. Users may experience latency or difficulty accessing Brivo Access at this time.

4. 21 января 2026 г. в 09:49 UTCinvestigating

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

5. 21 января 2026 г. в 14:06 UTCresolved

   This incident has been resolved.