Historia awarii Brivo

1. 24 sierpnia 2026 22:52 UTCinvestigating

   Obecnie pracujemy nad rozwiązaniem problemów z komunikacją panelową. Zdarzenia i komendy panelowe mogą nie być normalnie przetwarzane.

2. 24 sierpnia 2026 23:08 UTCidentified

   Obecnie pracujemy nad rozwiązaniem problemów z komunikacją panelową. Zdarzenia i komendy panelowe mogą nie być normalnie przetwarzane.

3. 24 sierpnia 2026 23:10 UTCresolved

   To była krótka przerwa, która od tego czasu wyzdrowiała. Usługa działa normalnie.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 24 sierpnia 2026 15:44 UTCinvestigating

   Obecnie pracujemy nad rozwiązaniem problemów z komunikacją panelową. Zdarzenia i komendy panelowe mogą nie być normalnie przetwarzane.

2. 24 sierpnia 2026 16:28 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 22 sierpnia 2026 13:56 UTCinvestigating

   Obecnie pracujemy nad rozwiązaniem problemów z komunikacją panelową. Zdarzenia i komendy panelowe mogą nie być normalnie przetwarzane.

2. 22 sierpnia 2026 16:03 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 16 lipca 2026 17:13 UTCresolved

   Normalne operacje zostały przywrócone dla Brivo API. Ostatnio dokonano aktualizacji, która spowodowała, że API zwrócił 400 błędów Bad Request dla wniosków zawierających dodatkowe, nieobsługiwane parametry zapytania. Cofnęliśmy się, aby upewnić się, że wcześniej udane wnioski nadal działają zgodnie z oczekiwaniami. Incydent zdarzył się od 3: 30 ET do 5: 20 PM ET.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 1 czerwca 2026 18:24 UTCinvestigating

   We are currently investigating issues logging into Brivo applications.

2. 1 czerwca 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 czerwca 2026 19:19 UTCmonitoring

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

4. 1 czerwca 2026 19:41 UTCresolved

   This incident has been resolved.

1. 29 maja 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 maja 2026 23:17 UTCresolved

   This incident has been resolved.

1. 21 maja 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 maja 2026 15:22 UTCmonitoring

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

3. 21 maja 2026 15:25 UTCresolved

   This incident has been resolved.

1. 14 maja 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 maja 2026 16:42 UTCmonitoring

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

3. 14 maja 2026 18:03 UTCresolved

   This incident has been resolved.

1. 13 maja 2026 20:54 UTCinvestigating

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

2. 13 maja 2026 21:08 UTCresolved

   This is a configuration issue

1. 1 maja 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 maja 2026 22:40 UTCresolved

   This incident has been resolved.

1. 24 kwietnia 2026 00:04 UTCinvestigating

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

2. 24 kwietnia 2026 00:25 UTCresolved

   This incident has been resolved.

1. 17 kwietnia 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 kwietnia 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 kwietnia 2026 06:09 UTCmonitoring

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

4. 17 kwietnia 2026 06:11 UTCresolved

   This incident has been resolved.

1. 14 kwietnia 2026 17:42 UTCinvestigating

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

2. 14 kwietnia 2026 18:21 UTCidentified

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

3. 14 kwietnia 2026 18:33 UTCmonitoring

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

4. 14 kwietnia 2026 18:37 UTCresolved

   This incident has been resolved.

1. 23 marca 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 marca 2026 14:21 UTCmonitoring

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

3. 23 marca 2026 14:47 UTCresolved

   This incident has been resolved

1. 11 marca 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 marca 2026 09:55 UTCidentified

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

3. 11 marca 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 marca 2026 11:18 UTCresolved

   This incident has been resolved.

1. 9 marca 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 marca 2026 21:05 UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. 9 marca 2026 23:26 UTCresolved

   This incident has been resolved

1. 5 marca 2026 20:27 UTCresolved

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

1. 3 marca 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 marca 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 lutego 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 lutego 2026 13:46 UTCmonitoring

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

3. 18 lutego 2026 14:26 UTCresolved

   This incident has been resolved.

1. 21 stycznia 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 stycznia 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 stycznia 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 stycznia 2026 09:49 UTCinvestigating

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

5. 21 stycznia 2026 14:06 UTCresolved

   This incident has been resolved.