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-10-19 17:24 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.

Checks passingchecked 5 minutes ago

Our checks of Brex pass from all 10 regions we check.

As of Oct 19, 2026, 5:20 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 Oct 19, 2026, 5:20 PM UTC
US-East1303 msChecks passing
US-West903 msChecks passing
Europe1217 msChecks passing
Asia-Pacific708 msChecks passing
US-Central189 msChecks passing
Canada509 msChecks passing
UK548 msChecks passing
Southeast Asia820 msChecks passing
Australia1320 msChecks passing
South America634 msChecks passing
their status pagetheir claim, not our reading

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

from Brex's own status page, checked Oct 19, 2026, 5:23 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.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 728ms2026-09-21 UTC: p95 530ms2026-09-22 UTC: p95 505ms2026-09-23 UTC: p95 655ms2026-09-24 UTC: p95 786ms2026-09-25 UTC: p95 795ms2026-09-26 UTC: p95 720ms2026-09-27 UTC: p95 684ms2026-09-28 UTC: p95 664ms2026-09-29 UTC: p95 660ms2026-09-30 UTC: p95 703ms2026-10-01 UTC: p95 750ms2026-10-02 UTC: p95 627ms2026-10-03 UTC: p95 673ms2026-10-04 UTC: p95 791ms2026-10-05 UTC: p95 714ms2026-10-06 UTC: p95 794ms2026-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.4s
Sep 20Oct 4Oct 19
US-West
1.2sp95 · 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-09-20 UTC: p95 359ms2026-09-21 UTC: p95 404ms2026-09-22 UTC: p95 346ms2026-09-23 UTC: p95 448ms2026-09-24 UTC: p95 413ms2026-09-25 UTC: p95 475ms2026-09-26 UTC: p95 497ms2026-09-27 UTC: p95 433ms2026-09-28 UTC: p95 452ms2026-09-29 UTC: p95 553ms2026-09-30 UTC: p95 576ms2026-10-01 UTC: p95 367ms2026-10-02 UTC: p95 278ms2026-10-03 UTC: p95 343ms2026-10-04 UTC: p95 379ms2026-10-05 UTC: p95 369ms2026-10-06 UTC: p95 393ms2026-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.2s
Sep 20Oct 4Oct 19
Europe
1.4sp95 · 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-09-20 UTC: p95 577ms2026-09-21 UTC: p95 627ms2026-09-22 UTC: p95 647ms2026-09-23 UTC: p95 627ms2026-09-24 UTC: p95 693ms2026-09-25 UTC: p95 668ms2026-09-26 UTC: p95 655ms2026-09-27 UTC: p95 637ms2026-09-28 UTC: p95 719ms2026-09-29 UTC: p95 686ms2026-09-30 UTC: p95 698ms2026-10-01 UTC: p95 602ms2026-10-02 UTC: p95 693ms2026-10-03 UTC: p95 813ms2026-10-04 UTC: p95 652ms2026-10-05 UTC: p95 636ms2026-10-06 UTC: p95 724ms2026-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.4s
Sep 20Oct 4Oct 19
Asia-Pacific
837msp95 · 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-09-20 UTC: p95 801ms2026-09-21 UTC: p95 891ms2026-09-22 UTC: p95 943ms2026-09-23 UTC: p95 884ms2026-09-24 UTC: p95 883ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 978ms2026-09-27 UTC: p95 834ms2026-09-28 UTC: p95 789ms2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 828ms2026-10-02 UTC: p95 927ms2026-10-03 UTC: p95 865ms2026-10-04 UTC: p95 886ms2026-10-05 UTC: p95 659ms2026-10-06 UTC: p95 883ms2026-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 837ms
Sep 20Oct 4Oct 19
US-Central
293msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 608ms2026-09-21 UTC: p95 471ms2026-09-22 UTC: p95 646ms2026-09-23 UTC: p95 714ms2026-09-24 UTC: p95 574ms2026-09-25 UTC: p95 423ms2026-09-26 UTC: p95 505ms2026-09-27 UTC: p95 555ms2026-09-28 UTC: p95 505ms2026-09-29 UTC: p95 472ms2026-09-30 UTC: p95 614ms2026-10-01 UTC: p95 588ms2026-10-02 UTC: p95 559ms2026-10-03 UTC: p95 478ms2026-10-04 UTC: p95 592ms2026-10-05 UTC: p95 534ms2026-10-06 UTC: p95 361ms2026-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 293ms
Sep 20Oct 4Oct 19
Canada
546msp95 · 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-09-20 UTC: p95 901ms2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 741ms2026-09-23 UTC: p95 860ms2026-09-24 UTC: p95 966ms2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 761ms2026-09-27 UTC: p95 351ms2026-09-28 UTC: p95 448ms2026-09-29 UTC: p95 475ms2026-09-30 UTC: p95 670ms2026-10-01 UTC: p95 741ms2026-10-02 UTC: p95 638ms2026-10-03 UTC: p95 601ms2026-10-04 UTC: p95 548ms2026-10-05 UTC: p95 439ms2026-10-06 UTC: p95 380ms2026-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 546ms
Sep 20Oct 4Oct 19
UK
687msp95 · 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-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 747ms2026-09-26 UTC: p95 721ms2026-09-27 UTC: p95 797ms2026-09-28 UTC: p95 771ms2026-09-29 UTC: p95 559ms2026-09-30 UTC: p95 642ms2026-10-01 UTC: p95 649ms2026-10-02 UTC: p95 664ms2026-10-03 UTC: p95 656ms2026-10-04 UTC: p95 643ms2026-10-05 UTC: p95 709ms2026-10-06 UTC: p95 705ms2026-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 687ms
Sep 20Oct 4Oct 19
Southeast Asia
1.3sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.0s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 2.1s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.3s2026-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.3s
Sep 20Oct 4Oct 19
Australia
2.3sp95 · 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-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 897ms2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 958ms2026-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.3s
Sep 20Oct 4Oct 19
South America
993msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 910ms2026-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 993ms
Sep 20Oct 4Oct 19

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: Checks passingSoutheast 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: 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: 1303msstatus code: 401checked: Oct 19, 2026, 5:13 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: 903msstatus code: 401checked: Oct 19, 2026, 5:20 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: 189msstatus code: 401checked: Oct 19, 2026, 4:58 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: 509msstatus code: 401checked: Oct 19, 2026, 4:50 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: 634msstatus code: 401checked: Oct 19, 2026, 5:01 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1217msstatus code: 401checked: Oct 19, 2026, 5:19 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
      Checks passinglatency: 548msstatus code: 401checked: Oct 19, 2026, 5:01 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: 708msstatus code: 401checked: Oct 19, 2026, 5:20 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: 820msstatus code: 401checked: Oct 19, 2026, 5:02 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: 1320msstatus code: 401checked: Oct 19, 2026, 5:08 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

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
Errors Affecting Brex API Requests, 4h 33mdeclared on their status page2026-08-04

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

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>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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