User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
opencagedata.com · Cloud & developer
Is OpenCage down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → opencagedata.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 2042 ms · 2 min ago.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:00 | 0 | 0.0 | 465 ms | 0 |
| 08:15 | 0 | 0.0 | 1487 ms | 0 |
| 08:30 | 0 | 0.0 | 899 ms | 0 |
| 08:45 | 0 | 0.0 | 626 ms | 0 |
| 09:00 | 0 | 0.0 | 718 ms | 0 |
| 09:15 | 0 | 0.0 | 221 ms | 0 |
| 09:30 | 0 | 0.0 | 538 ms | 0 |
| 09:45 | 0 | 0.0 | 652 ms | 0 |
| 10:00 | 0 | 0.0 | 739 ms | 0 |
| 10:15 | 0 | 0.0 | 992 ms | 0 |
| 10:30 | 0 | 0.0 | 1155 ms | 0 |
| 10:45 | 0 | 0.0 | 313 ms | 0 |
| 11:00 | 0 | 0.0 | 1823 ms | 0 |
| 11:15 | 0 | 0.0 | 899 ms | 0 |
| 11:30 | 0 | 0.0 | 1122 ms | 0 |
| 11:45 | 0 | 0.0 | 1097 ms | 0 |
| 12:00 | 0 | 0.0 | 2261 ms | 0 |
| 12:15 | 0 | 0.0 | 442 ms | 0 |
| 12:30 | 0 | 0.0 | 584 ms | 0 |
| 12:45 | 0 | 0.0 | 639 ms | 0 |
| 13:00 | 0 | 0.0 | 569 ms | 0 |
| 13:15 | 0 | 0.0 | 1088 ms | 0 |
| 13:30 | 0 | 0.0 | 220 ms | 0 |
| 13:45 | 0 | 0.0 | 293 ms | 0 |
| 14:00 | 0 | 0.0 | 1257 ms | 0 |
| 14:15 | 0 | 0.0 | 1298 ms | 0 |
| 14:30 | 0 | 0.0 | 758 ms | 0 |
| 14:45 | 0 | 0.0 | 1027 ms | 0 |
| 15:00 | 0 | 0.0 | 566 ms | 0 |
| 15:15 | 0 | 0.0 | 819 ms | 0 |
| 15:30 | 0 | 0.0 | 1113 ms | 0 |
| 15:45 | 0 | 0.0 | 1102 ms | 0 |
| 16:00 | 0 | 0.0 | 1041 ms | 0 |
| 16:15 | 0 | 0.0 | 623 ms | 0 |
| 16:30 | 0 | 0.0 | 723 ms | 0 |
| 16:45 | 0 | 0.0 | 1704 ms | 0 |
| 17:00 | 0 | 0.0 | 344 ms | 0 |
| 17:15 | 0 | 0.0 | 537 ms | 0 |
| 17:30 | 0 | 0.0 | 539 ms | 0 |
| 17:45 | 0 | 0.0 | 930 ms | 0 |
| 18:00 | 0 | 0.0 | 1287 ms | 0 |
| 18:15 | 0 | 0.0 | 1118 ms | 0 |
| 18:30 | 0 | 0.0 | 1342 ms | 0 |
| 18:45 | 0 | 0.0 | 395 ms | 0 |
| 19:00 | 0 | 0.0 | 1774 ms | 0 |
| 19:15 | 0 | 0.0 | 1098 ms | 0 |
| 19:30 | 0 | 0.0 | 822 ms | 0 |
| 19:45 | 0 | 0.0 | 2042 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live OpenCage status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for OpenCage yet. Outages of 10 minutes or more get their own page here.
Having trouble with OpenCage?
One report per service every 10 minutes from this network. No account.
Follow OpenCage
Get an email when OpenCage goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpenCage alerts to Slack, Discord or a webhook — free.
Questions
Is OpenCage down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
OpenCage not working for me but the status is fine. What now?
If OpenCage is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on OpenCage's side.
How does Damn is it down decide OpenCage's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is OpenCage checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.