●Incident
IBGE Names outage.
ResolvedDEGRADATION · HIGHOct 14, 2026, 07:30 PM · 11 days ago · Duration: 40h 10min
Incident Summary
Incident Summary
API IBGE Names is currently DOWN in us-east.
Diagnostic Details
Error Type: network HTTP Status: N/A Error Message: fetch failed Retry Attempts: 3 (all failed)
Validation Results
Validation Reason: All 3 retry attempts failed 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-14T19:30:45.918Z
Timeline
●Started
Oct 14, 2026, 07:30 PM
11 days ago
●Resolved
Oct 16, 2026, 11:40 AM
9 days ago
●Duration
40h 10min
Total downtime
Evidence Logs5 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Oct 14, 07:30 PM | us-east | down | 575ms | — |
| Oct 14, 07:26 PM | us-west | down | 569ms | — |
| Oct 14, 07:25 PM | europe | down | 628ms | — |
How many of your clients depend on IBGE?
When IBGE 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.
Alerts land on email, Slack, push or webhooks — with the client's name on them.