●Incident

Canada Open Data Search outage.

ResolvedDEGRADATION · HIGH

Oct 16, 2026, 09:21 PM · about 14 hours ago · Duration: 34min

Detected by Probecast

Incident Summary

API Canada Open Data Search 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: 299s

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-16T21:21:39.110Z

Timeline

●Started

Oct 16, 2026, 09:21 PM

about 14 hours ago

●Resolved

Oct 16, 2026, 09:55 PM

about 13 hours ago

●Duration

34min

Total downtime

Evidence Logs6 checks

Time	Region	Status	Latency	Code
Oct 16, 09:21 PM	europe	down	10000ms	—
Oct 16, 09:19 PM	asia	down	10000ms	—
Oct 16, 09:17 PM	us-east	down	10001ms	—

Probecast for agencies

How many of your clients depend on Government of Canada?

When Government of Canada 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 Government of Canada full status →

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