Skip to content

Outage tracker / Brex

Is Brex down?

I'm having a problem

Vendor reports no incidentWhat Brex reports

Brex reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:13 UTC.

Brex's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedchecked 1 minute ago

Brex is answering our probes, but its web surface is running at least 4.8x its 7-day median from UK and its API is running at least 4.6x its 7-day median from UK. Everything else we check answered at its usual speed.

As of Nov 5, 2026, 2:15 PM UTC, RealUptime's checks of Brex passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:15 PM UTC
US-East1229 msChecks passing
US-West1861 msChecks passing
Europe779 msChecks passing
Asia-Pacific2261 msChecks passing
US-Central815 msChecks passing
Canada687 msChecks passing
UK2123 msDegraded
Southeast Asia1841 msChecks passing
Australia1656 msChecks passing
South America2087 msChecks passing
their status pagetheir claim, not our reading

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

from Brex's own status page, checked Nov 5, 2026, 1:08 PM UTC
Brex's own status page shows no incident, and our checks of Brex pass 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
  • Customer SupportOperational

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
1.8sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 680ms2026-10-08 UTC: p95 725ms2026-10-09 UTC: p95 680ms2026-10-10 UTC: p95 754ms2026-10-11 UTC: p95 760ms2026-10-12 UTC: p95 736ms2026-10-13 UTC: p95 764ms2026-10-14 UTC: p95 669ms2026-10-15 UTC: p95 609ms2026-10-16 UTC: p95 769ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 598ms2026-10-22 UTC: p95 504ms2026-10-23 UTC: p95 925ms2026-10-24 UTC: p95 499ms2026-10-25 UTC: p95 439ms2026-10-26 UTC: p95 2.9s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
US-West
1.8sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 282ms2026-10-08 UTC: p95 405ms2026-10-09 UTC: p95 457ms2026-10-10 UTC: p95 556ms2026-10-11 UTC: p95 440ms2026-10-12 UTC: p95 393ms2026-10-13 UTC: p95 533ms2026-10-14 UTC: p95 447ms2026-10-15 UTC: p95 410ms2026-10-16 UTC: p95 462ms2026-10-17 UTC: p95 994ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 937ms2026-10-22 UTC: p95 871ms2026-10-23 UTC: p95 838ms2026-10-24 UTC: p95 984ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
Europe
1.7sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 754ms2026-10-08 UTC: p95 711ms2026-10-09 UTC: p95 827ms2026-10-10 UTC: p95 716ms2026-10-11 UTC: p95 738ms2026-10-12 UTC: p95 689ms2026-10-13 UTC: p95 755ms2026-10-14 UTC: p95 612ms2026-10-15 UTC: p95 825ms2026-10-16 UTC: p95 611ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 610ms2026-10-22 UTC: p95 954ms2026-10-23 UTC: p95 990ms2026-10-24 UTC: p95 628ms2026-10-25 UTC: p95 556ms2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 709ms2026-10-29 UTC: p95 732ms2026-10-30 UTC: p95 1.1s2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Asia-Pacific
2.2sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 884ms2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 998ms2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 889ms2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 977ms2026-10-19 UTC: p95 844ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
US-Central
894msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 475ms2026-10-08 UTC: p95 375ms2026-10-09 UTC: p95 382ms2026-10-10 UTC: p95 433ms2026-10-11 UTC: p95 630ms2026-10-12 UTC: p95 569ms2026-10-13 UTC: p95 494ms2026-10-14 UTC: p95 502ms2026-10-15 UTC: p95 644ms2026-10-16 UTC: p95 470ms2026-10-17 UTC: p95 608ms2026-10-18 UTC: p95 287ms2026-10-19 UTC: p95 300ms2026-10-20 UTC: p95 318ms2026-10-21 UTC: p95 296ms2026-10-22 UTC: p95 321ms2026-10-23 UTC: p95 365ms2026-10-24 UTC: p95 310ms2026-10-25 UTC: p95 291ms2026-10-26 UTC: p95 408ms2026-10-27 UTC: p95 468ms2026-10-28 UTC: p95 878ms2026-10-29 UTC: p95 315ms2026-10-30 UTC: p95 333ms2026-10-31 UTC: p95 602ms2026-11-01 UTC: p95 514ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 978ms2026-11-05 UTC: p95 894ms
Oct 7Oct 21Nov 5
Canada
1.1sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 518ms2026-10-08 UTC: p95 575ms2026-10-09 UTC: p95 633ms2026-10-10 UTC: p95 849ms2026-10-11 UTC: p95 784ms2026-10-12 UTC: p95 858ms2026-10-13 UTC: p95 731ms2026-10-14 UTC: p95 592ms2026-10-15 UTC: p95 509ms2026-10-16 UTC: p95 666ms2026-10-17 UTC: p95 535ms2026-10-18 UTC: p95 608ms2026-10-19 UTC: p95 570ms2026-10-20 UTC: p95 541ms2026-10-21 UTC: p95 533ms2026-10-22 UTC: p95 380ms2026-10-23 UTC: p95 386ms2026-10-24 UTC: p95 365ms2026-10-25 UTC: p95 532ms2026-10-26 UTC: p95 550ms2026-10-27 UTC: p95 519ms2026-10-28 UTC: p95 448ms2026-10-29 UTC: p95 934ms2026-10-30 UTC: p95 438ms2026-10-31 UTC: p95 421ms2026-11-01 UTC: p95 366ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
1.9sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 645ms2026-10-08 UTC: p95 708ms2026-10-09 UTC: p95 771ms2026-10-10 UTC: p95 697ms2026-10-11 UTC: p95 624ms2026-10-12 UTC: p95 644ms2026-10-13 UTC: p95 625ms2026-10-14 UTC: p95 472ms2026-10-15 UTC: p95 475ms2026-10-16 UTC: p95 466ms2026-10-17 UTC: p95 720ms2026-10-18 UTC: p95 915ms2026-10-19 UTC: p95 684ms2026-10-20 UTC: p95 739ms2026-10-21 UTC: p95 523ms2026-10-22 UTC: p95 739ms2026-10-23 UTC: p95 542ms2026-10-24 UTC: p95 643ms2026-10-25 UTC: p95 572ms2026-10-26 UTC: p95 709ms2026-10-27 UTC: p95 790ms2026-10-28 UTC: p95 894ms2026-10-29 UTC: p95 522ms2026-10-30 UTC: p95 514ms2026-10-31 UTC: p95 527ms2026-11-01 UTC: p95 887ms2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 689ms2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Southeast Asia
2.6sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.7s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.6s
Oct 7Oct 21Nov 5
Australia
2.0sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.7s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 908ms2026-10-23 UTC: p95 959ms2026-10-24 UTC: p95 922ms2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 998ms2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.2s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 2.6s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
South America
3.0sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 994ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 5.8s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 2.6s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.5s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5

Check your own site while you wait on Brex

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Degraded Answering, but 4.8x slower than its 7-day median.Southeast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Degraded Answering, but 4.6x slower than its 7-day median.Southeast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DashboardUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Developer docsUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Brex reports an incident on its status page, and again when it reports it resolved.

Get an email when Brex reports an incident

Email me when Brex reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Brex's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1229msstatus code: 401checked: Nov 5, 2026, 1:56 PM 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
      Checks passinglatency: 1861msstatus code: 401checked: Nov 5, 2026, 1:40 PM 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.
    • US-Central
      Checks passinglatency: 815msstatus code: 401checked: Nov 5, 2026, 2:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Brex normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 687msstatus code: 401checked: Nov 5, 2026, 2:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Brex normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2087msstatus code: 401checked: Nov 5, 2026, 1:26 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Brex normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    DegradedEurope, UK
    • Europe
      Checks passinglatency: 779msstatus code: 401checked: Nov 5, 2026, 2:08 PM 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.
    • UK
      Degradedlatency: 2123msstatus code: 401checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Brex normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2261msstatus code: 401checked: Nov 5, 2026, 1:57 PM 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.
    • Southeast Asia
      Checks passinglatency: 1841msstatus code: 401checked: Nov 5, 2026, 1:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Brex normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1656msstatus code: 401checked: Nov 5, 2026, 2:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Brex normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

Unable to deliver SMS to Orange in France, 240h 56mdeclared on their status page2026-10-20
Notifications Partial Outage, 1mdeclared on their status page2026-10-02
Admin home page load error spike, 34mdeclared on their status page2026-09-30
Unexpected invalidation of some Developer API Tokens, 1mdeclared on their status page2026-09-21
Transaction statuses on your Accounting pages may be out of date, causing some transactions to appear in the wrong tab., 3h 8mdeclared on their status page2026-09-15
Trust Portal (trust-portal.brex.com) is down, 8h 8mdeclared on their status page2026-09-01
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

check 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 check readings and Brex's own claim at the time, side by side.

Full check history for Brex: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Brex uptime by RealUptime's checksLive, from this page's own readings.
[![Brex uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Brex down?", https://realuptime.io/outages/brex. The readings change with every check, so give the date you read them.

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
secondary
https://dashboard.brex.com/
secondary
https://developer.brex.com/
RealUptime is not affiliated with Brex; the name identifies what we checked, and nothing here speaks for Brex's own team. We send a single web request to Brex from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.