Historial de interrupciones de Brivo

1. August 24, 2026 at 10:52 PM UTCinvestigating

   Actualmente estamos trabajando en resolver problemas con las comunicaciones de grupos especiales. Los eventos y comandos de panel pueden no ser procesados normalmente.

2. August 24, 2026 at 11:08 PM UTCidentified

   Actualmente estamos trabajando en resolver problemas con las comunicaciones de grupos especiales. Los eventos y comandos de panel pueden no ser procesados normalmente.

3. August 24, 2026 at 11:10 PM UTCresolved

   Esta fue una breve interrupción que se ha recuperado desde entonces. El servicio funciona normalmente.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 24, 2026 at 3:44 PM UTCinvestigating

   Actualmente estamos trabajando en resolver problemas con las comunicaciones de grupos especiales. Los eventos y comandos de panel pueden no ser procesados normalmente.

2. August 24, 2026 at 4:28 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 22, 2026 at 1:56 PM UTCinvestigating

   Actualmente estamos trabajando en resolver problemas con las comunicaciones de grupos especiales. Los eventos y comandos de panel pueden no ser procesados normalmente.

2. August 22, 2026 at 4:03 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 16, 2026 at 5:13 PM UTCresolved

   Se han restaurado operaciones normales para la API de Brivo. Recientemente, se hizo una actualización que causó que la API devolviera 400 errores de Bad Request para solicitudes que contenían parámetros de consulta extra y sin soporte. Hemos regresado para asegurar que sus solicitudes de éxito anteriores continúen trabajando como se esperaba. El incidente ocurrió de 3:30AM ET a 5:20PM ET.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 1, 2026 at 6:24 PM UTCinvestigating

   We are currently investigating issues logging into Brivo applications.

2. June 1, 2026 at 7:00 PM 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. June 1, 2026 at 7:19 PM UTCmonitoring

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

4. June 1, 2026 at 7:41 PM UTCresolved

   This incident has been resolved.

1. May 29, 2026 at 3:37 PM 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. May 29, 2026 at 11:17 PM UTCresolved

   This incident has been resolved.

1. May 21, 2026 at 3:10 PM UTCidentified

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

2. May 21, 2026 at 3:22 PM UTCmonitoring

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

3. May 21, 2026 at 3:25 PM UTCresolved

   This incident has been resolved.

1. May 14, 2026 at 4:38 PM UTCidentified

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

2. May 14, 2026 at 4:42 PM UTCmonitoring

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

3. May 14, 2026 at 6:03 PM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 8:54 PM UTCinvestigating

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

2. May 13, 2026 at 9:08 PM UTCresolved

   This is a configuration issue

1. May 1, 2026 at 5:28 PM 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. May 1, 2026 at 10:40 PM UTCresolved

   This incident has been resolved.

1. April 24, 2026 at 12:04 AM UTCinvestigating

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

2. April 24, 2026 at 12:25 AM UTCresolved

   This incident has been resolved.

1. April 17, 2026 at 5:35 AM 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. April 17, 2026 at 6:05 AM 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. April 17, 2026 at 6:09 AM UTCmonitoring

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

4. April 17, 2026 at 6:11 AM UTCresolved

   This incident has been resolved.

1. April 14, 2026 at 5:42 PM UTCinvestigating

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

2. April 14, 2026 at 6:21 PM UTCidentified

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

3. April 14, 2026 at 6:33 PM UTCmonitoring

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

4. April 14, 2026 at 6:37 PM UTCresolved

   This incident has been resolved.

1. March 23, 2026 at 1:24 PM UTCidentified

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

2. March 23, 2026 at 2:21 PM UTCmonitoring

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

3. March 23, 2026 at 2:47 PM UTCresolved

   This incident has been resolved

1. March 11, 2026 at 9:29 AM 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. March 11, 2026 at 9:55 AM UTCidentified

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

3. March 11, 2026 at 10:04 AM 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. March 11, 2026 at 11:18 AM UTCresolved

   This incident has been resolved.

1. March 9, 2026 at 6:09 PM 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. March 9, 2026 at 9:05 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results

3. March 9, 2026 at 11:26 PM UTCresolved

   This incident has been resolved

1. March 5, 2026 at 8:27 PM UTCresolved

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

1. March 3, 2026 at 7:39 PM 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. March 3, 2026 at 10:22 PM UTCresolved

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

1. February 18, 2026 at 12:20 PM 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. February 18, 2026 at 1:46 PM UTCmonitoring

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

3. February 18, 2026 at 2:26 PM UTCresolved

   This incident has been resolved.

1. January 21, 2026 at 7:44 AM UTCinvestigating

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

2. January 21, 2026 at 7:45 AM UTCidentified

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

3. January 21, 2026 at 9:36 AM UTCidentified

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

4. January 21, 2026 at 9:49 AM UTCinvestigating

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

5. January 21, 2026 at 2:06 PM UTCresolved

   This incident has been resolved.