User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
opencagedata.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests opencagedata.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1496 ms · 1 min ago.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 1713 ms | 0 |
| 03:15 | 0 | 0.0 | 188 ms | 0 |
| 03:30 | 0 | 0.0 | 1195 ms | 0 |
| 03:45 | 0 | 0.0 | 1477 ms | 0 |
| 04:00 | 0 | 0.0 | 1072 ms | 0 |
| 04:15 | 0 | 0.0 | 1085 ms | 0 |
| 04:30 | 0 | 0.0 | 952 ms | 0 |
| 04:45 | 0 | 0.0 | 2248 ms | 0 |
| 05:00 | 0 | 0.0 | 576 ms | 0 |
| 05:15 | 0 | 0.0 | 403 ms | 0 |
| 05:30 | 0 | 0.0 | 712 ms | 0 |
| 05:45 | 0 | 0.0 | 384 ms | 0 |
| 06:00 | 0 | 0.0 | 575 ms | 0 |
| 06:15 | 0 | 0.0 | 455 ms | 0 |
| 06:30 | 0 | 0.0 | 703 ms | 0 |
| 06:45 | 0 | 0.0 | 717 ms | 0 |
| 07:00 | 0 | 0.0 | 592 ms | 0 |
| 07:15 | 0 | 0.0 | 882 ms | 0 |
| 07:30 | 0 | 0.0 | 1781 ms | 0 |
| 07:45 | 0 | 0.0 | 1007 ms | 0 |
| 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 | 1496 ms | 0 |
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.
No outages on record for OpenCage yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
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.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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.
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.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.