●Incident

ExchangeRate-API outage.

ResolvedDEGRADATION · HIGH

Oct 21, 2026, 01:23 PM · about 5 hours ago · Duration: 20min

Detected by Probecast

Incident Summary

Incident Summary

API ExchangeRate-API is currently DOWN in us-west.

Diagnostic Details

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

Validation Results

Validation Reason: DOWN in 2 regions: asia, us-west Consecutive DOWN Checks: 2 Time Between Checks: 289s

Cross-Region Impact

Also DOWN in: asia Total Affected Regions: 2 Still UP in: europe, us-east

Severity Assessment

Level: MEDIUM Limited regional impact or recoverable error type.


Detected by Probecast Health Monitor - 2026-10-21T13:23:21.015Z

Timeline

●Started

Oct 21, 2026, 01:23 PM

about 5 hours ago

●Resolved

Oct 21, 2026, 01:43 PM

about 4 hours ago

●Duration

20min

Total downtime

Evidence Logs3 checks

TimeRegionStatusLatencyCode
Oct 21, 01:23 PMus-westdown13ms500
Oct 21, 01:20 PMasiadown183ms502
Oct 21, 01:18 PMus-westdown2ms502
Probecast for agencies

How many of your clients depend on ExchangeRate-API?

When ExchangeRate-API 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 ExchangeRate-API full status →

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

Related Incidents