Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Outage in Firezone Production

Client connections degraded

Resolved Major
July 21, 2025 - Started 9 months ago - Lasted about 18 hours
Official incident page

Incident Report

On July 21, at around 5:30a pacific time, database maintenance was performed to remove stale policy authorization records. Due to a bug in the event processing handler for each connected client, this resulted in large numbers of policy updates to be sent to some Firezone clients that were connected at the time. Depending on the level of resource availability on the host machine at the time of occurrence, some Firezone clients were unable to process this burst of events, and subsequently started dropping them. In some cases, this could have led to one or more Resource(s) being unavailable in the client that the user would normally have access to. Once the client reconnected, either through a client restart or re-authentication, the list of Resources would be reset, resolving the issue. A fix for the event processing filter was deployed later this day at around 5:00 pm pacific time, mitigating the potential for similar issues to occur in the future.

Trusted by 1,000+ teams

Never miss outages in third-party dependencies

Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.

IsDown status aggregator dashboard
Latest Updates ( sorted recent to last )
RESOLVED 9 months ago - at 07/22/2025 06:54AM

On July 21, at around 5:30a pacific time, database maintenance was performed to remove stale policy authorization records. Due to a bug in the event processing handler for each connected client, this resulted in large numbers of policy updates to be sent to some Firezone clients that were connected at the time.

Depending on the level of resource availability on the host machine at the time of occurrence, some Firezone clients were unable to process this burst of events, and subsequently started dropping them. In some cases, this could have led to one or more Resource(s) being unavailable in the client that the user would normally have access to.

Once the client reconnected, either through a client restart or re-authentication, the list of Resources would be reset, resolving the issue.

A fix for the event processing filter was deployed later this day at around 5:00 pm pacific time, mitigating the potential for similar issues to occur in the future.

Never miss outages in third-party dependencies

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 6320 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook