Skip to content

Outage tracker / Brex

Is Brex down?

I'm having a problem

Operationalchecked moments ago

We reached Brex from all 10 regions we check.

As of Oct 6, 2026, 9:59 PM UTC, Brex answered RealUptime's probes in all 10 regions that returned a reading.

Brex's last published incident: "Notifications Partial Outage", Oct 2, 2026, 0 min. their claim, not our reading

Functional endpoints verified

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

our independent probeslive · checked Oct 6, 2026, 9:59 PM UTC
US-East474 msOperational
US-West157 msOperational
Europe503 msOperational
Asia-Pacific730 msOperational
US-Central411 msOperational
Canada273 msOperational
UK650 msOperational
Southeast Asia841 msOperational
Australia934 msOperational
South America923 msOperational
their status pagetheir claim, not our reading

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

from Brex's own status page, checked Oct 6, 2026, 9:58 PM 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
  • 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 published 4 incidents in the last 30 days. Our probes recorded 0 outages seen from more than one region in that time.

Brex response time, by region

US-East
799msp95 · 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-09-07 UTC: p95 666ms2026-09-08 UTC: p95 630ms2026-09-09 UTC: p95 632ms2026-09-10 UTC: p95 653ms2026-09-11 UTC: p95 727ms2026-09-12 UTC: p95 563ms2026-09-13 UTC: p95 564ms2026-09-14 UTC: p95 564ms2026-09-15 UTC: p95 534ms2026-09-16 UTC: p95 697ms2026-09-17 UTC: p95 712ms2026-09-18 UTC: p95 674ms2026-09-19 UTC: p95 664ms2026-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 799ms
Sep 7Sep 21Oct 6
US-West
414msp95 · 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-09-07 UTC: p95 459ms2026-09-08 UTC: p95 434ms2026-09-09 UTC: p95 283ms2026-09-10 UTC: p95 209ms2026-09-11 UTC: p95 261ms2026-09-12 UTC: p95 412ms2026-09-13 UTC: p95 404ms2026-09-14 UTC: p95 417ms2026-09-15 UTC: p95 450ms2026-09-16 UTC: p95 283ms2026-09-17 UTC: p95 347ms2026-09-18 UTC: p95 419ms2026-09-19 UTC: p95 319ms2026-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 414ms
Sep 7Sep 21Oct 6
Europe
692msp95 · 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-09-07 UTC: p95 621ms2026-09-08 UTC: p95 604ms2026-09-09 UTC: p95 626ms2026-09-10 UTC: p95 969ms2026-09-11 UTC: p95 826ms2026-09-12 UTC: p95 671ms2026-09-13 UTC: p95 688ms2026-09-14 UTC: p95 680ms2026-09-15 UTC: p95 619ms2026-09-16 UTC: p95 594ms2026-09-17 UTC: p95 581ms2026-09-18 UTC: p95 594ms2026-09-19 UTC: p95 586ms2026-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 692ms
Sep 7Sep 21Oct 6
Asia-Pacific
889msp95 · 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-07 UTC: p95 887ms2026-09-08 UTC: p95 768ms2026-09-09 UTC: p95 921ms2026-09-10 UTC: p95 944ms2026-09-11 UTC: p95 943ms2026-09-12 UTC: p95 869ms2026-09-13 UTC: p95 770ms2026-09-14 UTC: p95 831ms2026-09-15 UTC: p95 682ms2026-09-16 UTC: p95 916ms2026-09-17 UTC: p95 862ms2026-09-18 UTC: p95 863ms2026-09-19 UTC: p95 814ms2026-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 889ms
Sep 7Sep 21Oct 6
US-Central
341msp95 · 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-07 UTC: p95 697ms2026-09-08 UTC: p95 588ms2026-09-09 UTC: p95 554ms2026-09-10 UTC: p95 472ms2026-09-11 UTC: p95 549ms2026-09-12 UTC: p95 601ms2026-09-13 UTC: p95 488ms2026-09-14 UTC: p95 544ms2026-09-15 UTC: p95 552ms2026-09-16 UTC: p95 622ms2026-09-17 UTC: p95 596ms2026-09-18 UTC: p95 548ms2026-09-19 UTC: p95 675ms2026-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 341ms
Sep 7Sep 21Oct 6
Canada
383msp95 · 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-07 UTC: p95 602ms2026-09-08 UTC: p95 539ms2026-09-09 UTC: p95 529ms2026-09-10 UTC: p95 561ms2026-09-11 UTC: p95 664ms2026-09-12 UTC: p95 630ms2026-09-13 UTC: p95 646ms2026-09-14 UTC: p95 632ms2026-09-15 UTC: p95 584ms2026-09-16 UTC: p95 670ms2026-09-17 UTC: p95 635ms2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.1s2026-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 383ms
Sep 7Sep 21Oct 6
UK
710msp95 · 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-07 UTC: p95 630ms2026-09-08 UTC: p95 590ms2026-09-09 UTC: p95 573ms2026-09-10 UTC: p95 579ms2026-09-11 UTC: p95 575ms2026-09-12 UTC: p95 629ms2026-09-13 UTC: p95 659ms2026-09-14 UTC: p95 674ms2026-09-15 UTC: p95 644ms2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 866ms2026-09-18 UTC: p95 895ms2026-09-19 UTC: p95 993ms2026-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 710ms
Sep 7Sep 21Oct 6
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-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.0s2026-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.3s
Sep 7Sep 21Oct 6
Australia
962msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 938ms2026-09-08 UTC: p95 976ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 944ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.0s2026-09-19 UTC: p95 1.2s2026-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 962ms
Sep 7Sep 21Oct 6
South America
835msp95 · 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-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 976ms2026-09-19 UTC: p95 1.2s2026-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 835ms
Sep 7Sep 21Oct 6

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: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Brex go down, and when it is back

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.

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

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 474msstatus code: 401checked: Oct 6, 2026, 9:37 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
      Operationallatency: 157msstatus code: 401checked: Oct 6, 2026, 9:54 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
      Operationallatency: 411msstatus code: 401checked: Oct 6, 2026, 9:53 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
      Operationallatency: 273msstatus code: 401checked: Oct 6, 2026, 9: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
    Operationallatency: 923msstatus code: 401checked: Oct 6, 2026, 9:48 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 503msstatus code: 401checked: Oct 6, 2026, 9:55 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
      Operationallatency: 650msstatus code: 401checked: Oct 6, 2026, 9:53 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 730msstatus code: 401checked: Oct 6, 2026, 9:59 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
      Operationallatency: 841msstatus code: 401checked: Oct 6, 2026, 9:54 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
      Operationallatency: 934msstatus code: 401checked: Oct 6, 2026, 9:56 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 outages

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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.