●Incident
Open Data München outage.
ResolvedDEGRADATION · HIGHOct 16, 2026, 12:02 PM · about 22 hours ago · Duration: 1h 19min
Incident Summary
Incident Summary
API Open Data München is currently DOWN in us-east.
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 2 regions: us-west, us-east Consecutive DOWN Checks: 2 Time Between Checks: 308s
Cross-Region Impact
Also DOWN in: us-west Total Affected Regions: 2
Severity Assessment
Level: MEDIUM Limited regional impact or recoverable error type.
Detected by Probecast Health Monitor - 2026-10-16T12:02:17.138Z
Timeline
●Started
Oct 16, 2026, 12:02 PM
about 22 hours ago
●Resolved
Oct 16, 2026, 01:21 PM
about 21 hours ago
●Duration
1h 19min
Total downtime
Evidence Logs4 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Oct 16, 12:02 PM | us-east | down | 471ms | 503 |
| Oct 16, 11:57 AM | us-west | down | 503ms | 503 |
| Oct 16, 11:57 AM | europe | down | 68ms | 503 |
How many of your clients depend on Open Data München?
When Open Data München 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.
Alerts land on email, Slack, push or webhooks — with the client's name on them.