Brex: Brex for Slack App Degraded Due to Ongoing Upstream Slack Incident

What to do

Check whether your product depends on Brex. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 2h 15m it lasted.
Anything that failed between 2026-05-14 15:00 UTC and 2026-05-14 17:14 UTC may need a replay.
Subscribe to Brex's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=brex works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingMay 14, 2026, 3:00 PM UTC
An incident at Slack is causing issues with our Brex for Slack application. Expect a degraded experience receiving notifications and interacting with our Brex application in Slack. The Slack team has acknowledged the incident and we will continue to monitor. Slack Status: https://slack-status.com/2026-05/fe557ca05fdb64fa
provider
identifiedMay 14, 2026, 3:00 PM UTC
The issue has been identified and a fix is being implemented.
provider
resolvedMay 14, 2026, 5:14 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Brex still down?

No, this incident was resolved 2026-05-14 17:14 UTC. For Brex's live state, see https://down.guide/brex.

How long did it last?

2h 15m, from 2026-05-14 15:00 UTC to 2026-05-14 17:14 UTC, by the times Brex posted.

What caused it?

Brex hasn't published a root cause. If it does, it shows here.

Where does this come from?

Brex's official status page, https://status.brex.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.