Brex

1. investigating 2026-10-20 15:55 UTC

   We are currently investigating an issue with our SMS deliverability in France. We are currently unable to send SMS to phone numbers registered with the cell carrier Orange. We are actively working with our partners at Twilio to resolve the issue. In the meantime, affected users...

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-02 22:36 UTC

   A transient issue caused some notifications to not be sent between 18:18–18:54 UTC. This includes MFA and 3DS challenges. The issue has been resolved and we are now sending notifications correctly.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Home Page

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-30 16:38 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-30 16:55 UTC

   We have identified the issue and have a fix in place. We are monitoring the page for further issues.

3. resolved 2026-09-30 17:12 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Partner API, Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-21 17:54 UTC

   We are aware of reports of developer API tokens getting unexpectedly invalidated. We are currently investigating this issue. Customers who are affected will need to generate new tokens in developer settings as the affected tokens cannot be re-used.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Spend Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-15 20:12 UTC

   Your changes are still being saved, and we're working on a fix.

2. resolved 2026-09-15 23:20 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-01 17:48 UTC

   The Brex trust portal is currently unavailable, we are investigating the issue.

2. monitoring 2026-09-01 19:20 UTC

   The site has been restored.

3. resolved 2026-09-02 01:56 UTC

   The Brex Trust Portal has been up and running again since 12:00pm PT.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Money movement: card authorization

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-15 04:49 UTC

   We have identified that transactions may be declined incorrectly due to a Mastercard Network outage.

2. resolved 2026-08-15 05:53 UTC

   Mastercard Network Outage has been resolved, and transactions should now be correctly processed.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-11 17:16 UTC

   Customers may experience intermittent issues accessing the Brex dashboard. Our team is investigating and working to restore normal service.

2. identified 2026-08-11 17:51 UTC

   Our team has identified the issue and are working to restore normal service.

3. identified 2026-08-11 18:17 UTC

   We have identified the issue and have a fix in place

4. monitoring 2026-08-11 18:17 UTC

   We have identified the issue and have a fix in place

5. resolved 2026-08-11 19:12 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-04 16:01 UTC

   We are currently investigating this issue.

2. identified 2026-08-04 16:02 UTC

   We have identified the issue and are working on a fix.

3. monitoring 2026-08-04 17:50 UTC

   We have identified the issue and have a fix in place.

4. resolved 2026-08-04 20:34 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Money movement: card authorization, Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-30 17:04 UTC

   Customers may experience delays receiving notifications, as well as delays or errors when loading the Tasks page or resetting authentication methods such as passwords or 2FA. Our team is investigating and working to restore normal service.

2. identified 2026-07-30 17:34 UTC

   We have identified the issue and are working on a fix.

3. resolved 2026-07-30 18:11 UTC

   We’ve resolved the issue affecting notifications and the Tasks page. All services are operating normally.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: The text does not say enough to tell. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-19 06:32 UTC

   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.

2. resolved 2026-07-19 07:45 UTC

   Scheduled Maintenance has been completed.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-18 07:01 UTC

   We'll be performing scheduled maintenance on July 18 from 12:00 AM–3:00 AM (PT). During this time, you may experience brief interruptions accessing your Brex account on the dashboard or mobile app. Adding your Brex card to a digital wallet, such as Apple Pay or Google Pay, may...

2. resolved 2026-07-18 09:32 UTC

   Scheduled Maintenance has been completed

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Spend Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-17 14:51 UTC

   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.

2. resolved 2026-07-17 15:32 UTC

   We have identified the root cause and resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-12 07:08 UTC

   Dashboard and External APIs are down for temporary maintenance.

2. resolved 2026-07-12 07:17 UTC

   Maintenance is complete, Dashboard and External APIs are available.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-03 16:28 UTC

   We are currently investigating this issue.

2. identified 2026-07-03 16:31 UTC

   We have identified the issue and are working on a fix.

3. monitoring 2026-07-03 16:37 UTC

   We have identified the issue and have a fix in place.

4. resolved 2026-07-03 17:02 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Banking

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-07-03 00:25 UTC

   We have identified the issue and are working on a fix.

2. monitoring 2026-07-03 00:26 UTC

   We have identified the issue and are working on a fix.

3. identified 2026-07-03 00:27 UTC

   We have identified the issue and are working on a fix.

4. resolved 2026-07-03 05:03 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Partner API, Partner Integrations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 18:59 UTC

   We have received reports of missing transactions in transaction feeds affecting integrations with Quickbooks, Expensify and other partners. We are currently investigating this issue.

2. resolved 2026-06-26 03:28 UTC

   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...

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Partner API, Dashboard, Partner Integrations

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-06-14 05:11 UTC

   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...

2. resolved 2026-06-14 05:29 UTC

   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.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Partner API, Dashboard, Partner Integrations

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-13 15:10 UTC

   Between 7:00 AM and 7:08 AM PT, a subset of requests to the Team API returned HTTP 500 errors due to database maintenance. During this window, some user information was temporarily unavailable, which may have prevented the Dashboard from loading for some users.

2. resolved 2026-06-13 15:17 UTC

   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.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Brex Travel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-13 05:21 UTC

   We are currently investigating an issue preventing trip booking and management.

2. resolved 2026-06-13 07:53 UTC

   We have resolved the issue affecting the ability to book and manage trips. Users can now continue using Brex Travel.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 21:23 UTC

   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.

2. monitoring 2026-06-04 21:37 UTC

   We have identified the issue and have a fix in place.

3. resolved 2026-06-04 22:01 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-19 00:15 UTC

   Some Dashboard requests were blocked with a misleading error message, the issue is resolved.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-14 15:00 UTC

   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:...

2. identified 2026-05-14 15:00 UTC

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

3. resolved 2026-05-14 17:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Partner API, Partner Integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-02 02:02 UTC

   We are investigating an issue around unavailability of bank feeds connected by Pro Access firms to Quickbooks for their clients.

2. identified 2026-05-02 02:06 UTC

   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.

3. monitoring 2026-05-02 02:15 UTC

   The fix has been rolled out and we are monitoring traffic from Quickbooks.

4. resolved 2026-05-02 04:09 UTC

   We see Quickbooks successfully syncing bank feeds initiated by Pro Access firms for their client's accounts.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-21 04:24 UTC

   Users may experience slow load times or timeouts when viewing activity on expenses, bills, users, cards in addition to the account audit trail. Other parts of the product remain unaffected. We'll share an update as soon as we have more information.

2. monitoring 2026-04-21 04:56 UTC

   Activity logs and audit trail pages are loading normally again

3. resolved 2026-04-21 14:22 UTC

   Activity logs and audit trail pages are stable.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-03 10:50 UTC

   The dashboard is currently unavailable and we are investigating this issue.

2. monitoring 2026-04-03 11:08 UTC

   We have identified the issue and have a fix in place.

3. resolved 2026-04-03 11:20 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-02 17:43 UTC

   We are currently investigating an issue with our two factor authentication taking a long time to load.

2. monitoring 2026-04-02 17:52 UTC

   We are seeing latency stabilize and are continuing to monitor

3. resolved 2026-04-02 18:24 UTC

   We have seen latency stabilize.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-02 15:17 UTC

   We are currently investigating this issue.

2. monitoring 2026-04-02 15:18 UTC

   Dashboard availability has recovered and we are continuing to monitor resolution.

3. resolved 2026-04-02 16:02 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Bill Pay

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-26 14:45 UTC

   Duplicate bill payments are showing up in the bills page

2. monitoring 2026-03-26 15:13 UTC

   We've identified the issue and this is now resolved. We are continuing to monitor.

3. resolved 2026-03-27 14:32 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-18 12:24 UTC

   We are currently investigating this issue.

2. resolved 2026-03-18 13:40 UTC

   The issue was resolved

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Bill Pay, Banking

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 02:42 UTC

   We are currently investigating this issue.

2. monitoring 2026-03-12 03:08 UTC

   We have identified the issue and have a fix in place.

3. resolved 2026-03-12 03:09 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-08 14:48 UTC

   We are currently investigating this issue.

2. identified 2026-03-08 15:22 UTC

   We have identified the issue and are working on a fix.

3. resolved 2026-03-08 15:42 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard, Mobile

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-04 19:38 UTC

   We are currently investigating this issue.

2. identified 2026-03-04 19:47 UTC

   We have identified the issue.

3. monitoring 2026-03-04 19:48 UTC

   We have the identified the issue and have made a fix.

4. resolved 2026-03-04 19:48 UTC

   This is now resolved.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-03 22:14 UTC

   We have identified the issue and are working on a fix.

2. identified 2026-03-03 22:20 UTC

   We have identified the issue and are working on a fix.

3. monitoring 2026-03-03 23:19 UTC

   We have identified the issue and have a fix in place.

4. resolved 2026-03-04 00:35 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-24 20:21 UTC

   We are currently investigating this issue.

2. monitoring 2026-02-24 20:25 UTC

   We have identified the issue and a fix has been deployed. Errors seem to be recovering and we are continuing to monitor the situation.

3. resolved 2026-02-24 21:16 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Banking

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-01-27 17:10 UTC

   Users are experiencing issues with loading banking transactions for review. The team has identified the issue and is working on a fix.

2. resolved 2026-01-27 17:18 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-01-22 22:36 UTC

   Emails going to Microsoft-based addresses are currently seeing a delay in delivery. Our email vendor is currently investigating.

2. resolved 2026-01-23 16:13 UTC

   Emails going to Microsoft-based addresses should now be received in a timely mannner

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Spend Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-09 19:43 UTC

   We are currently investigating this issue.

2. identified 2026-01-09 20:11 UTC

   We have identified the issue and are working on a fix.

3. monitoring 2026-01-09 20:20 UTC

   We have identified the issue and have a fix in place.

4. resolved 2026-01-09 20:48 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-11-23 09:35 UTC

   We have begun the scheduled maintenance of our systems. Expected downtime is ~3 mins.

2. resolved 2025-11-23 10:18 UTC

   Maintenance is now complete, and all systems are back online.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard, Mobile, Home Page

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. monitoring 2025-11-18 16:17 UTC

   Chat support may not be accessible for some users, but phone support is available. This was caused by an ongoing Cloudflare outage, and our team is monitoring as service is being restored.

2. resolved 2025-11-18 17:53 UTC

   We experienced an outage affecting chat support, receipt processing and address verification due to an outage by one of our partners, Cloudflare. This has now been resolved.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard, Mobile, Spend Management, Bill Pay, Home Page

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 13:17 UTC

   Our ability to provide support via chat, text or phone is impacted. Our team is aware of the issue and is actively working to correct it.

2. identified 2025-11-18 13:24 UTC

   Our ability to provide support via chat is impacted, but you can continue to receive support via phone. Our team is aware of the issue and is actively working to correct it.

3. identified 2025-11-18 13:34 UTC

   Our ability to provide support via chat is impacted, but you can continue to receive support via phone. This is due to an outage by one of our partners, Cloudflare. Our team is actively monitoring the issue for resolution.

4. identified 2025-11-18 14:12 UTC

   We are unable to provide support via chat, but phone support is available. Other functionality, including receipt processing and address verification are also impacted due to an outage by one of our partners, Cloudflare. Our team is monitoring the issue.

5. monitoring 2025-11-18 14:50 UTC

   We experienced an outage affecting chat support, receipt processing and address verification due to an outage by one of our partners, Cloudflare. This is now resolved, and our team is monitoring to ensure normal operations.

6. resolved 2025-11-18 16:30 UTC

   We experienced an outage affecting chat support, receipt processing and address verification due to an outage by one of our partners, Cloudflare. This is now resolved, and our team is monitoring to ensure normal operations.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Bill Pay, Banking

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-01 20:06 UTC

   Sending money via international wire in non-USD currencies is unavailable

2. identified 2025-11-01 20:59 UTC

   Sending money via international wire in non-USD currencies is unavailable

3. resolved 2025-11-01 22:03 UTC

   The issue when sending money or paying a bill via international wire in non-USD currencies has been resolved.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Brex Travel

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-07 23:12 UTC

   We are experiencing a service disruption impacting Travel. Our team is actively working to resolve the issue as soon as possible.

2. resolved 2025-10-07 23:39 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Bill Pay

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-03 14:52 UTC

   We are currently investigating an issue causing delays in treasury and wire transfers.

2. investigating 2025-10-03 15:05 UTC

   We are currently investigating an issue causing delays in treasury and wire transfers.

3. monitoring 2025-10-03 16:58 UTC

   We’ve mitigated the issue causing delays in treasury and wire transfers and will continue monitoring

4. resolved 2025-10-03 20:38 UTC

   This issue is now fully resolved

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-29 11:47 UTC

   We are currently investigating this issue.

2. monitoring 2025-09-29 11:50 UTC

   We have identified the issue and have a fix in place.

3. resolved 2025-09-29 11:55 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-26 13:48 UTC

   We are currently investigating reports of intermittent connectivity.

2. monitoring 2025-09-26 14:01 UTC

   We have identified the issue, have put a fix in place and are monitoring for recovery.

3. resolved 2025-09-26 14:23 UTC

   We have resolved the issue. We will continue monitoring for stability.

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-09-18 20:30 UTC

   Transactions retrieved by calling the list expenses API endpoint (https://developer.brex.com/openapi/expenses_api/#operation/listExpenses) between 1:30pm PT on September 18 and 5:30pm PT on September 22 may have contained incorrect expense data. This issue caused certain...

Excerpts are shortened. Read the full incident on Brex's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-09-18 15:55 UTC

   We have received reports of an outage affecting Google. You may experience login issues if you use Google SSO.

2. resolved 2025-09-18 16:08 UTC

   Google has resolved the issue: https://www.google.com/appsstatus/dashboard/incidents/7Bgq1PUK83NuVZHMZXWd

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Spend Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-16 17:03 UTC

   We are currently investigating this issue.

2. identified 2025-09-16 17:51 UTC

   We have identified the issue and are working on a fix.

3. monitoring 2025-09-16 21:24 UTC

   We have identified the issue and have a fix in place.

4. resolved 2025-09-16 23:20 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.

Affected: Home Page

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-03 22:36 UTC

   We are investigating an issue preventing completion of the ID verification process as part of account verification.

2. monitoring 2025-09-03 23:26 UTC

   We have resolved the issue and are monitoring.

3. resolved 2025-09-04 06:08 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Brex's status page.