Is Brex Down? How to Check Brex Status Right Now

Brex powers the financial stack for thousands of startups and growth-stage companies — corporate cards, expense management, business banking, and vendor payments. When Brex is working, spend happens invisibly and finance teams close their books on time. When Brex goes down, card transactions decline at critical moments, expense reimbursements stall, and ACH payouts don't land.

Here's how to quickly determine whether Brex is down, which component is failing, and how to protect your team's financial operations when it is.

Is Brex Down Right Now?

Check these sources in order:

1. Statusfield — Brex status — real-time monitoring across Brex's card network, dashboard, ACH, API, and expense management.
2. Twitter/X — search Brex down or Brex card declined sorted by Latest. Finance teams and founders notice transaction failures within minutes of an outage.
3. Downdetector — useful for confirming a user-reported spike, though it lacks component-level detail for financial infrastructure.

What Actually Breaks During a Brex Outage

Brex is composed of independent subsystems. A degradation in one does not automatically affect the others.

Component	What it does	Impact when down
Card transactions	Processes Brex card authorizations and purchases	Cards decline at point of sale, online checkouts fail, in-flight purchases may timeout
Dashboard	Web app for account management, spend tracking, and controls	Finance team loses visibility into spend; card limits and controls cannot be updated
Mobile app	iOS and Android access to Brex cards and expenses	Mobile card management, virtual card creation, and expense capture unavailable
Expense management	Receipt capture, expense categorization, and approval workflows	Expense submissions stall; finance workflows cannot close or reimburse
ACH / Bank transfers	Wire transfers, ACH payouts, and bill payments	Scheduled payouts miss settlement windows; vendor payments are delayed
Reimbursements	Out-of-pocket expense reimbursements to employees	Reimbursements are not processed; employees waiting on payments are blocked
API	Programmatic access to cards, transactions, and spend data	ERP integrations (NetSuite, QuickBooks, Xero) fail to sync; custom spend dashboards break
Notifications	Transaction alerts, spend limit warnings, and approval requests	Real-time spend visibility breaks; over-limit spend may go undetected
Authentication / SSO	Login via Brex credentials or SSO provider	Users cannot log in to the dashboard or mobile app

Common Brex Error Symptoms

What you see	What it usually means
Card declined with "Do Not Honor"	Authorization request failed; may be Brex network issue or card limit
Dashboard returns 503 or blank screen	Web application is degraded
"Transaction pending" stuck for hours	Card network or settlement service is degraded
ACH transfer shows "processing" past expected settlement	ACH origination or banking rail is delayed
API calls return 500 or time out	Brex API layer is degraded
Expense submission fails to save	Expense management service is degraded
SSO redirect fails or loops	Authentication service or your IdP connection is degraded

Key distinction: A declined card does not automatically mean Brex is down. Card declines have many causes: insufficient credit, a frozen card, a merchant category block, or a spend limit set by your finance admin. Confirm at Statusfield that a platform-wide issue exists before assuming infrastructure failure.

How Brex's Architecture Affects Outage Scope

Card transaction processing is separate from the dashboard. Brex's card authorization network operates independently of the web application. A dashboard outage does not necessarily mean cards are declining, and vice versa. If cards are working but the dashboard is inaccessible, finance teams lose visibility but spend continues. If cards are declining but the dashboard is accessible, the issue is in the card network layer.

ACH and banking rails have independent settlement windows. ACH transfers depend on Federal Reserve settlement cutoffs (typically 5 PM ET for same-day ACH). A Brex ACH degradation during a settlement window means the transfer misses the cutoff and settles the next business day. A degradation after the cutoff window has less immediate impact.

API access is separate from transaction processing. A Brex API outage breaks ERP integrations and programmatic card management, but may not affect card spending. If your accounting system stops syncing transaction data but cards are processing normally, isolate the issue to the API layer before treating it as a broad financial failure.

Reimbursements run on a different processing path than card transactions. Employee expense reimbursements are routed separately from card purchases and ACH payouts. A reimbursement processing outage does not affect card authorization.

Is It Brex or Your Configuration?

Before escalating to an infrastructure outage, rule out common configuration issues:

Card limit reached. Brex corporate cards have per-transaction, daily, and monthly spend limits set by your finance admin. A card that declines consistently without a Brex-wide issue is usually a limit configuration problem. Check the Brex dashboard under card settings.

Merchant category block. Finance admins can restrict spending to specific merchant categories. A card declined at a specific vendor type (e.g., entertainment, travel) while other purchases succeed typically means a category restriction, not a Brex outage.

SSO misconfiguration. If your organization uses Okta or Azure AD SSO with Brex and login is failing, verify your IdP is passing the correct attributes and that your Brex SSO configuration hasn't drifted. Test with a direct Brex login (email/password) to isolate the IdP from the Brex login service.

API key scope. Brex API keys are scoped to specific permissions (read transactions, manage cards, initiate transfers). If an API integration is returning 403 errors, the key may lack the required scope — this is not a Brex outage.

ACH cutoff missed. If an ACH transfer shows "processing" past the expected settlement time, check whether the transfer was initiated before or after the same-day ACH cutoff (5 PM ET). Transfers initiated after the cutoff settle the following business day by design.

When these are ruled out and failures persist across users or functions, the evidence points to a Brex infrastructure issue. Confirm at Statusfield.

Hardening Your Financial Operations Against Brex Outages

1. Maintain a backup card for critical vendor payments

For SaaS subscriptions and vendor payments that would cause immediate service disruption if declined (cloud hosting, key SaaS tools, payroll providers), maintain a secondary payment method. A single-card dependency on Brex for infrastructure spend creates a single point of failure.

2. Build retry logic into Brex API integrations

ERP and accounting integrations that sync Brex transaction data should queue failed sync attempts rather than drop them. Most Brex API degradations are transient. An integration that drops failed requests without queuing them for retry creates silent gaps in your financial data.

3. Monitor ACH settlement timing for time-sensitive payouts

If your payroll, vendor payment, or reimbursement cycle depends on same-day ACH via Brex, monitor the settlement window actively. A Brex ACH degradation near the settlement cutoff can push payouts to the next business day. Build in a buffer and alert on transfers that haven't settled by expected time.

4. Set spend notifications for early anomaly detection

Brex's notification system can alert on card declines, large transactions, and budget breaches in real time. During an outage, these notifications may stop — which is itself a signal. If your team normally gets real-time spend alerts and they've stopped, treat that silence as a potential indicator of notification service degradation.

5. Monitor Brex like a critical financial infrastructure dependency

When Brex goes down during a vendor payment cycle or at month close, the financial impact is immediate. Statusfield monitors Brex's card network, dashboard, ACH, and API continuously, alerting you the moment status changes — through Slack, Discord, email, or webhook.

How to Stay Ahead of Brex Outages

The goal is to know Brex is degraded before your finance team does — before the "my card just declined" messages hit your Slack.

Statusfield monitors Brex continuously and delivers alerts the moment a degradation is detected. On the free plan you get 3 monitors and 10 alerts/month, no credit card required.

→ Monitor Brex on Statusfield — free, no credit card required

FAQ

Why did my Brex card get declined if there's no outage?

Card declines have many causes beyond a platform outage: insufficient available credit, a per-transaction spend limit set by your finance admin, a merchant category block, or a geographic restriction. Check the Brex dashboard for the decline reason on the specific transaction. If the dashboard shows no issue with the card and other cardholders are reporting the same decline pattern, check Statusfield for a card network degradation.

Is Brex down for everyone or just our company?

Check Statusfield first. If Statusfield shows Brex as operational, the issue is likely scoped to your account — card limits, merchant restrictions, SSO configuration, or API key scope. If Statusfield shows a degradation, confirm which component (cards, dashboard, ACH, API) matches what your team is experiencing.

Our Brex ACH transfer didn't arrive on time. Is Brex down?

Not necessarily. Same-day ACH has a Federal Reserve cutoff (typically 5 PM ET). Transfers initiated after the cutoff settle the next business day regardless of Brex's operational status. Check whether the transfer was initiated before or after the cutoff. If it was initiated before the cutoff and hasn't settled within the expected window, check Statusfield for a reported ACH or banking rail degradation.

The Brex API is returning errors but our cards are working. What's happening?

Brex's API layer and card transaction processing operate independently. An API degradation can occur while card authorization continues normally. This means ERP integrations and programmatic card management may fail while cardholders can still spend. Check Statusfield to confirm an API-specific degradation, and queue your failed API requests for retry rather than dropping them.

How long do Brex outages typically last?

Most Brex degradations are partial — affecting one component (e.g., the dashboard or API) while card transactions continue normally — and resolve within 15–60 minutes. Outages affecting card authorization directly are less common and typically resolve within 30–90 minutes. Check Statusfield for live status during an incident.