Skip to main content
Brex logo

Is Brex Down?

No — Brex is up

Reachable from all 8 checked regions

Average response time: 203ms

Last checked · checks run every 6 hours

Official status page: https://status.brex.com

Brex uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
320ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak
Sep 12: no data
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: 100.00% uptime, 16 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
242ms
DNS 139ms TCP 1ms TLS 18ms TTFB 224ms
fra
106ms
DNS 37ms TCP 1ms TLS 8ms TTFB 99ms
gru
228ms
DNS 141ms TCP 2ms TLS 9ms TTFB 216ms
iad
190ms
DNS 113ms TCP 2ms TLS 7ms TTFB 167ms
jnb
287ms
DNS 64ms TCP 0ms TLS 65ms TTFB 224ms
lax
162ms
DNS 23ms TCP 1ms TLS 25ms TTFB 140ms
lhr
122ms
DNS 45ms TCP 2ms TLS 7ms TTFB 111ms
nrt
289ms
DNS 217ms TCP 1ms TLS 10ms TTFB 273ms

What Brex does

Brex is a finance platform for companies that combines corporate cards, expense management, bill pay, business banking and travel booking. Employees spend on Brex cards and submit receipts in the app, while finance teams approve spending, pay vendors and connect Brex to other tools through partner integrations. Because card authorisation runs through Brex, an incident can stop employees paying for things, not only the paperwork.

What an outage looks like

Brex cards are declined at the point of sale even with budget available, and the dashboard or mobile app will not load, so receipts and expenses cannot be submitted. Bill payments may not send and banking pages fail to show balances. Integrations with accounting and HR tools stop syncing, and Brex Travel bookings can fail while card spending continues to work.

What to do about it

Check status.brex.com, where Money movement: card authorization is its own row, separate from the Dashboard, Mobile, Spend Management, Bill Pay, Banking, Brex Travel and Partner Integrations. If card authorisation is affected, employees should use another approved payment method and keep receipts. Do not resend a bill payment that looks stuck until Bill Pay recovers and you have checked whether the first one went out.

Is it down for everyone, or just you?

If this page says Brex is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Brex outage FAQ

Why was my Brex card declined?
Check the Money movement: card authorization row on status.brex.com. If it shows an incident, declines are coming from Brex rather than from your budget or the merchant, and retrying will not help until it recovers. If it is green, the decline is more likely a spending limit, a blocked merchant category or a policy on your card, which your admin can see.
Will a bill payment be sent twice if I retry?
It can be, so check first. Bill Pay is a separate row on the status page. Once it recovers, find the payment in Brex and confirm whether it was sent before trying again. Sending a second payment on a guess risks paying the vendor twice and then having to recover the money.
Why is my accounting software not syncing with Brex?
Look at the Partner Integrations and Partner API rows. They are separate from card spending and the dashboard, so syncing can stop while everything else works. Once the rows recover, check that recent transactions appear in the connected tool before you close or reconcile the period.
Is Brex down for everyone or just me?
Compare the status page with this page's measurements from several regions. If both show Brex healthy, the likely causes are local: a stale session in the app, a blocked sign-in, or your own network. Failures seen from several regions at once point to Brex itself.

How we measure this

  • We request Brex's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Brex publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Brex goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required