Brex had 45 outages in the last 2 years totaling 61h 24m of downtime — averaging 1.8 incidents per month.
There were 45 Brex outages since July 2, 2025 totaling 61h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We have identified the issue and are working on a fix.
We have identified the issue and have a fix in place.
We have resolved the issue.
Customers may experience delays receiving notifications, as well as delays or errors when loading the Tasks page. Our team is investigating and working to restore normal service.
We have identified the issue and are working on a fix.
We’ve resolved the issue affecting notifications and the Tasks page. All services are operating normally.
We'll be performing scheduled maintenance on July 18 from 11:30 PM–2:00 AM (PT). During this time, you may experience brief interruptions with the dashboard. New signups, banking transactions, and card creation will be unavailable.
Scheduled Maintenance has been completed.
We're investigating reports of errors when trying to view new spend limit or spend limit increase requests in the Tasks page of the Brex dashboard.
We have identified the root cause and resolved the issue.
Dashboard and External APIs are down for temporary maintenance.
Maintenance is complete, Dashboard and External APIs are available.
We are currently investigating this issue.
We have identified the issue and are working on a fix.
We have identified the issue and have a fix in place.
We have resolved the issue.
We have identified the issue and are working on a fix.
We have identified the issue and have a fix in place.
We have identified the issue and have a fix in place.
We have resolved the issue.
We have received reports of missing transactions in transaction feeds affecting integrations with Quickbooks, Expensify and other partners. We are currently investigating this issue.
We have resolved the issue and transactions are now being synced correctly. In the vast majority of cases, previously missing transactions will show up automatically in the next 24 hours. In a few rare cases, additional action may be required and we will reach out directly. If you do not see expected transactions please monitor your inbox, or reach out to our support team for further assistance.
Awaiting dispute results. Expected date 30 June 2026 Dispute - disp_cmn3bqdl70020018092dadoez (est. $58461.89) Dispute - disp_cmn3b4ckq000q0169ughrby7g (est. $137842.02) Dispute - disp_cmnhg55sp009k0178zo9cw1fb (est. $169943.32)
Between 8:00 PM - 8:30 PM PT and 9:35 PM - 9:50 PM PT, a subset of requests to our API returned HTTP 500 errors due to database maintenance. During this window, some card and transaction operations were temporarily unavailable, which may have prevented the Dashboard from loading for some users.
The maintenance has been confirmed to be complete. Any failed API calls can be successfully retried and users should now be able to transact and see their cards and transactions.
Between 7:00 AM and 7:08 AM PT, a subset of requests to the Team API returned HTTP 500 errors due to unplanned database maintenance. During this window, some user information was temporarily unavailable, which may have prevented the Dashboard from loading for some users.
The maintenance has been confirmed to be complete. Any failed API calls can be successfully retried and users should now be able to load the Brex Dashboard successfully.
We are currently investigating an issue preventing trip booking and management.
We have resolved the issue affecting the ability to book and manage trips. Users can now continue using Brex Travel.
Users may experience slow load times or timeouts when viewing activity on expenses, bills, users, cards in addition to their account audit trail. Other parts of the product remain unaffected. We'll share an update as soon as we have more information.
We have identified the issue and have a fix in place.
We have resolved the issue.
Some Dashboard requests were blocked with a misleading error message, the issue is resolved.
An incident at Slack is causing issues with our Brex for Slack application. Expect a degraded experience receiving notifications and interacting with our Brex application in Slack. The Slack team has acknowledged the incident and we will continue to monitor. Slack Status: https://slack-status.com/2026-05/fe557ca05fdb64fa
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are investigating an issue around unavailability of bank feeds connected by Pro Access firms to Quickbooks for their clients.
We've identified a fix to restore bank feeds in Quickbooks for clients that have had their Pro Access firm connect the bank feed on their behalf. This change will be rolling out in a few minutes.
The fix has been rolled out and we are monitoring traffic from Quickbooks.
We see Quickbooks successfully syncing bank feeds initiated by Pro Access firms for their client's accounts.
The dashboard is currently unavailable and we are investigating this issue.
We have identified the issue and have a fix in place.
We have resolved the issue.
We are currently investigating an issue with our two factor authentication taking a long time to load.
We are seeing latency stabilize and are continuing to monitor
We have seen latency stabilize.
Duplicate bill payments are showing up in the bills page
We've identified the issue and this is now resolved. We are continuing to monitor.
We have resolved the issue.
We are currently investigating this issue.
The issue was resolved
We are currently investigating this issue.
We have identified the issue and have a fix in place.
We have resolved the issue.
We are currently investigating this issue.
We have identified the issue and are working on a fix.
We have resolved the issue.
We are currently investigating this issue.
We have identified the issue.
We have the identified the issue and have made a fix.
This is now resolved.
We have identified the issue and are working on a fix.
We have identified the issue and are working on a fix.
We have identified the issue and have a fix in place.
We have resolved the issue.
We are currently investigating this issue.
We have identified the issue and a fix has been deployed. Errors seem to be recovering and we are continuing to monitor the situation.
We have resolved the issue.