●Incident

Open Data Berlin outage.

ResolvedDEGRADATION · HIGH

Oct 20, 2026, 01:17 PM · about 4 hours ago · Duration: 19min

Detected by Probecast

Incident Summary

API Open Data Berlin is currently DOWN in europe.

Diagnostic Details

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

Validation Results

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

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-20T13:17:34.553Z

Timeline

●Started

Oct 20, 2026, 01:17 PM

about 4 hours ago

●Resolved

Oct 20, 2026, 01:36 PM

about 3 hours ago

●Duration

19min

Total downtime

Evidence Logs5 checks

Time	Region	Status	Latency	Code
Oct 20, 01:17 PM	europe	down	14ms	503
Oct 20, 01:15 PM	us-west	down	159ms	503
Oct 20, 01:15 PM	asia	down	188ms	503

Probecast for agencies

How many of your clients depend on Open Data Berlin?

When Open Data Berlin slows down, every client that depends on it feels it at once, and the first call usually goes to the agency. Probecast watches your clients' sites and the providers underneath them, shows which clients an outage touches, and turns the 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.

Book 15 minutes →View Open Data Berlin full status →

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