User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
ipquery.io · Cloud & developer
Is IPQuery down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → ipquery.io—
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. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 4 min ago. Last stored result reached it in 63 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 08 | 0 | 0.0 | 52 ms | 0 |
| Mon 10 | 0 | 0.0 | 27 ms | 0 |
| Mon 12 | 0 | 0.0 | 32 ms | 0 |
| Mon 14 | 0 | 0.0 | 233 ms | 0 |
| Mon 17 | 0 | 0.0 | 47 ms | 0 |
| Mon 19 | 0 | 0.0 | 80 ms | 0 |
| Mon 21 | 0 | 0.0 | 28 ms | 0 |
| Mon 23 | 0 | 0.0 | 29 ms | 0 |
| Tue 01 | 0 | 0.0 | 64 ms | 0 |
| Tue 03 | 0 | 0.0 | 174 ms | 0 |
| Tue 05 | 0 | 0.0 | 95 ms | 0 |
| Tue 07 | 0 | 0.0 | 53 ms | 0 |
| Tue 09 | 0 | 0.0 | 44 ms | 0 |
| Tue 12 | 0 | 0.0 | 25 ms | 0 |
| Tue 14 | 0 | 0.0 | 244 ms | 0 |
| Tue 16 | 0 | 0.0 | 111 ms | 0 |
| Tue 18 | 0 | 0.0 | 36 ms | 0 |
| Tue 21 | 0 | 0.0 | 40 ms | 0 |
| Tue 23 | 0 | 0.0 | 59 ms | 0 |
| Wed 01 | 0 | 0.0 | 18 ms | 0 |
| Wed 03 | 0 | 0.0 | 151 ms | 0 |
| Wed 06 | 0 | 0.0 | 200 ms | 0 |
| Wed 08 | 0 | 0.0 | 31 ms | 0 |
| Wed 10 | 0 | 0.0 | 151 ms | 0 |
| Wed 12 | 0 | 0.0 | 27 ms | 0 |
| Wed 14 | 0 | 0.0 | 227 ms | 0 |
| Wed 16 | 0 | 0.0 | 39 ms | 0 |
| Wed 19 | 0 | 0.0 | 75 ms | 0 |
| Wed 21 | 0 | 0.0 | 60 ms | 0 |
| Wed 23 | 0 | 0.0 | 97 ms | 0 |
| Thu 01 | 0 | 0.0 | 169 ms | 0 |
| Thu 03 | 0 | 0.0 | 312 ms | 0 |
| Thu 05 | 0 | 0.0 | 65 ms | 0 |
| Thu 07 | 0 | 0.0 | 32 ms | 0 |
| Thu 09 | 0 | 0.0 | 36 ms | 0 |
| Thu 11 | 0 | 0.0 | 239 ms | 0 |
| Thu 13 | 0 | 0.0 | 27 ms | 0 |
| Thu 16 | 0 | 0.0 | 81 ms | 0 |
| Thu 18 | 0 | 0.0 | 43 ms | 0 |
| Thu 19 | 0 | 0.0 | 17 ms | 0 |
| Thu 21 | 0 | 0.0 | 269 ms | 0 |
| Thu 23 | 0 | 0.0 | 318 ms | 0 |
| Fri 01 | 0 | 0.0 | 35 ms | 0 |
| Fri 03 | 0 | 0.0 | 136 ms | 0 |
| Fri 05 | 0 | 0.0 | 175 ms | 0 |
| Fri 07 | 0 | 0.0 | 243 ms | 0 |
| Fri 09 | 0 | 0.0 | 127 ms | 0 |
| Fri 10 | 0 | 0.0 | 63 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live IPQuery badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for IPQuery yet. Outages of 10 minutes or more get their own page here.
Having trouble with IPQuery?
One report per service every 10 minutes from this network. No account.
Follow IPQuery
Get an email when IPQuery goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send IPQuery alerts to Slack, Discord or a webhook — free.
About IPQuery
We track IPQuery (ipquery.io) as part of the Cloud & developer group. Look up IPv4 and IPv6 addresses for geolocation, ASN, ISP, VPN, proxy, Tor and hosting data. Use the public API without an API key.
IPQuery publishes an official status page at status.ipquery.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 138 ms average, 6–318 ms range across 15 successful checks.
Questions
Is IPQuery down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was IPQuery last down?
We have not recorded a public IPQuery incident since monitoring began 8 days ago.
What is IPQuery's uptime?
From our own checks: 100% over 8 days of checks.
How fast does IPQuery respond?
138 ms on average over the last 24 hours (6–318 ms).
Does IPQuery have an official status page?
Yes, at https://status.ipquery.io.
IPQuery not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report IPQuery here at once, the problem is on IPQuery's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with IPQuery. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.