Brivo experienced a minor incident on October 20, 2025 affecting Brivo Access United States Region and Brivo Access Europe Region and 1 more component, lasting 23h 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2025, 09:53 AM UTC
We are currently working on resolving issues with Brivo Access, related to an overall AWS outage. Users may experience latency or difficulty using Brivo Access at this time. We are taking mitigating actions and will continue to provide updates. Please refer to refer to AWS's status page at https://health.aws.amazon.com/ for additional details.
- identified Oct 20, 2025, 11:57 AM UTC
We are seeing improved performance with Brivo Access. Users may still experience slowness with device status, notifications, and other pages. We continue to take mitigating actions and will provide periodic updates.
- identified Oct 20, 2025, 12:42 PM UTC
We are having continued system delays impacting overall system latency. Users may still experience slowness with device status, notifications, and other pages. We continue to take mitigating actions and will provide periodic updates.
- identified Oct 20, 2025, 01:17 PM UTC
We are still experiencing system delays which leads to dashboard statistics not populating with data. Users may still experience slowness with device status, notifications, and other pages. We continue to take mitigating actions and will provide periodic updates.
- identified Oct 20, 2025, 02:03 PM UTC
Dashboard metrics are recovering and we are seeing improved responsiveness from our 3rd party systems. Users may still experience slowness with device status, notifications, and other pages. We continue to take mitigating actions and will provide periodic updates.
- identified Oct 20, 2025, 02:59 PM UTC
Brivo Access is still experiencing latency in regards to some of our 3rd party service providers. Users may still experience slowness with device status, notifications, and other pages. We continue to take mitigating actions and will provide periodic updates.
- identified Oct 20, 2025, 04:04 PM UTC
We are experiencing some additional intermittent service outages in core AWS services that underpin our access platforms. Users may still experience slowness with device status, notifications, and other pages. We continue to take mitigating actions and will provide periodic updates. Please refer to refer to AWS's status page at https://health.aws.amazon.com/ for additional details.
- identified Oct 20, 2025, 05:21 PM UTC
We are aware that users are not able to load some Access pages and our engineering team is investigating. We continue to take mitigating actions and will provide periodic updates. Please refer to refer to AWS's status page at https://health.aws.amazon.com/ for additional details.
- identified Oct 20, 2025, 06:32 PM UTC
We are seeing continued issues with our public cloud provider. Resolving this issue is our top priority and we are monitoring AWS health continuously. We continue to take mitigating actions and will provide periodic updates. Please refer to refer to AWS's status page at https://health.aws.amazon.com/ for additional details.
- identified Oct 20, 2025, 08:19 PM UTC
Our cloud provider, AWS, is resolving their issue and we are seeing their services recover. As a result, we are seeing Brivo Access latencies coming down and our team is monitoring the situation closely. We will provide another update once full functionality is restored.
- identified Oct 20, 2025, 11:29 PM UTC
AWS has resolved the outage, and we are continuing to see services recover. One of our service providers is experiencing downstream effects from the outage, which may impact Brivo Access latency. We will provide another update when full functionality is restored.
- identified Oct 21, 2025, 12:47 AM UTC
Most Access functionality is back to being fully operational, but we are still seeing issues with live events, browser notifications and recorded video. We are closely monitoring our cloud providers for full resolution.
- monitoring Oct 21, 2025, 04:18 AM UTC
A fix has been implemented by our service provider, and we are monitoring the results.
- resolved Oct 21, 2025, 09:22 AM UTC
All systems are fully operational and latencies are back to normal.