●Incident

Banco Central do Brasil outage.

ResolvedDEGRADATION · HIGH

Oct 24, 2026, 10:30 AM · 1 day ago · Duration: 25min

Detected by Probecast

Incident Summary

API Banco Central do Brasil is currently DOWN in us-east.

Diagnostic Details

Error Type: http HTTP Status: 500 Error Message: API returned HTTP 500 Retry Attempts: 1 (all failed)

Validation Results

Validation Reason: DOWN in multiple regions: europe, us-west + us-east Consecutive DOWN Checks: 2 Time Between Checks: 300s

Cross-Region Impact

Also DOWN in: europe, us-west Total Affected Regions: 3

Severity Assessment

Level: HIGH Multiple regions affected or critical error type detected.

Detected by Probecast Health Monitor - 2026-10-24T10:30:57.782Z

Timeline

●Started

Oct 24, 2026, 10:30 AM

1 day ago

●Resolved

Oct 24, 2026, 10:56 AM

1 day ago

●Duration

25min

Total downtime

Evidence Logs4 checks

Time	Region	Status	Latency	Code
Oct 24, 10:30 AM	us-east	down	701ms	500
Oct 24, 10:29 AM	us-west	down	198ms	500
Oct 24, 10:29 AM	europe	down	3470ms	500

For the projects you ship

How many of your clients depend on Banco Central do Brasil?

When Banco Central do Brasil slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.

One provider breaks. See every client it touches.

Ordered by how many clients it hits, so you message the right people first.

Each client's site and store, checked from four regions.

US West & East, Europe and Asia — a regional outage never hides.

A monthly report under your brand, reviewed by your team before it goes out.

Uptime, incidents, traffic, revenue and support — signed off by a person.

Your team scoped per client. Every change on the record.

Freelancers see only their clients; every change lands in an append-only audit log.

Start free Book 15 minutes →View Banco Central do Brasil full status →

Alerts land on email, Slack, push or webhooks — with the client's name on them.