Skip to content

Outage tracker / Brex

Is Brex down?

I'm having a problem

Operationalchecked 9 minutes ago

We reached Brex from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 10 days we have measured Brex (since Aug 22, 2026).

our independent probeslive · checked Sep 1, 2026, 4:36 AM UTC
US-East575 msOperational
US-West466 msOperational
Europe504 msOperational
Asia-Pacific722 msOperational
their status pagetheir claim, not our reading

Brex reports: All systems operational (“All Systems Operational”)

from Brex's own status page, checked Sep 1, 2026, 4:25 AM UTC
Our probes and Brex's own status page agree: both show Brex as reachable right now.

Brex's own component breakdown, as they publish it

  • Money movement: card authorizationOperational
  • Partner APIOperational
  • DashboardOperational
  • MobileOperational
  • AuthenticationOperational
  • Partner IntegrationsOperational
  • Spend ManagementOperational
  • Brex TravelOperational
  • Bill PayOperational
  • Home PageOperational
  • BankingOperational

These are Brex's components, named and scored by Brex. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Brex's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Brex response time, by region

US-East
625msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 536ms2026-08-23 UTC: p95 578ms2026-08-24 UTC: p95 778ms2026-08-25 UTC: p95 803ms2026-08-26 UTC: p95 634ms2026-08-27 UTC: p95 803ms2026-08-28 UTC: p95 718ms2026-08-29 UTC: p95 736ms2026-08-30 UTC: p95 715ms2026-08-31 UTC: p95 645ms2026-09-01 UTC: p95 625ms
Aug 3Aug 17Sep 1
US-West
644msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 340ms2026-08-23 UTC: p95 400ms2026-08-24 UTC: p95 451ms2026-08-25 UTC: p95 309ms2026-08-26 UTC: p95 354ms2026-08-27 UTC: p95 506ms2026-08-28 UTC: p95 606ms2026-08-29 UTC: p95 494ms2026-08-30 UTC: p95 649ms2026-08-31 UTC: p95 380ms2026-09-01 UTC: p95 644ms
Aug 3Aug 17Sep 1
Europe
782msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 582ms2026-08-23 UTC: p95 753ms2026-08-24 UTC: p95 788ms2026-08-25 UTC: p95 849ms2026-08-26 UTC: p95 928ms2026-08-27 UTC: p95 722ms2026-08-28 UTC: p95 790ms2026-08-29 UTC: p95 746ms2026-08-30 UTC: p95 646ms2026-08-31 UTC: p95 733ms2026-09-01 UTC: p95 782ms
Aug 3Aug 17Sep 1
Asia-Pacific
873msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 696ms2026-08-23 UTC: p95 1.1s2026-08-24 UTC: p95 954ms2026-08-25 UTC: p95 1.4s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 983ms2026-08-29 UTC: p95 1.0s2026-08-30 UTC: p95 947ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 873ms
Aug 3Aug 17Sep 1

Is it Brex, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Brex -- it cannot diagnose Brex's own systems.

What we measured, function by function

Brex answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 575msstatus code: 401checked: Sep 1, 2026, 4:36 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Brex normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 466msstatus code: 401checked: Sep 1, 2026, 4:34 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Brex normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 504msstatus code: 401checked: Sep 1, 2026, 4:23 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Brex normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 722msstatus code: 401checked: Sep 1, 2026, 4:27 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Brex normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionBrex is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionBrex is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionBrex is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionBrex is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionBrex is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionBrex is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Brex, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Brex yet, which is not evidence that nothing is wrong.

Recent outages

Mastercard Network Outage, 1h 4mdeclared on their status page2026-08-15
Intermittent errors on the Brex dashboard, 1h 57mdeclared on their status page2026-08-11
Errors Affecting Brex API Requests, 4h 33mdeclared on their status page2026-08-04
Notification delays, 1h 8mdeclared on their status page2026-07-30
Scheduled Maintenance has been completed, 1h 14mdeclared on their status page2026-07-19
Scheduled Maintenance has been completed, 2h 32mdeclared on their status page2026-07-18
Users are experiencing errors when viewing spend limit requests, 40mdeclared on their status page2026-07-17
Maintenance is complete, Dashboard and External APIs are available., 10mdeclared on their status page2026-07-12

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Brex since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Brex covering any window you pick, with our measurements and Brex's own claim at the time, side by side.

Full availability history for Brex: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Brex, and again when they can reach it again. That is our own measurement from ten regions, not Brex's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Brex uptime measured by RealUptimeLive, from this page's own readings.
[![Brex uptime measured by RealUptime](https://realuptime.io/outages/brex/badge.svg?days=30)](https://realuptime.io/outages/brex)
<a href="https://realuptime.io/outages/brex"><img src="https://realuptime.io/outages/brex/badge.svg?days=30" alt="Brex uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Brex's SLA implies, from our measurement

At or above your target

We measured none of downtime for Brex over the 244h 45m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 14 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Brex's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://platform.brexapis.com/v2/accounts/cash
secondary
https://www.brex.com/
secondary
https://status.brex.com/api/v2/status.json
RealUptime is not affiliated with Brex; the name identifies what we measured, and nothing here speaks for Brex's own team. We send a single web request to Brex from 4 regions on our own schedule and time the response. We do not see inside Brex's systems, do not use an account or real transaction, and are not the same signal Brex's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Brex is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Brex operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on August 22, 2026 (10 of 14 days so far, 5087 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.