●Incident

Open Data Barcelona outage.

ResolvedDEGRADATION · HIGH

Oct 31, 2026, 10:30 AM · 3 days ago · Duration: 18min

Detected by Probecast

Incident Summary

API Open Data Barcelona is currently DOWN in europe.

Diagnostic Details

Error Type: timeout HTTP Status: N/A Error Message: Request timeout after 10000ms Retry Attempts: 3 (all failed)

Validation Results

Validation Reason: All 3 retry attempts failed Consecutive DOWN Checks: 2 Time Between Checks: 304s

Cross-Region Impact

Also DOWN in: asia, us-east, us-west Total Affected Regions: 4

Severity Assessment

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

Detected by Probecast Health Monitor - 2026-10-31T10:30:28.577Z

Timeline

●Started

Oct 31, 2026, 10:30 AM

3 days ago

●Resolved

Oct 31, 2026, 10:48 AM

3 days ago

●Duration

18min

Total downtime

Evidence Logs6 checks

Time	Region	Status	Latency	Code
Oct 31, 10:30 AM	us-east	down	10001ms	—
Oct 31, 10:30 AM	europe	down	10001ms	—
Oct 31, 10:26 AM	us-west	down	10000ms	—

For the projects you ship

How many of your clients depend on Open Data Barcelona?

When Open Data Barcelona 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 up to 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 Open Data Barcelona full status →

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