User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 39 min ago. Last stored result reached it in 191 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 360 ms | 0 |
| Tue 00 | 0 | 0.0 | 233 ms | 0 |
| Tue 02 | 0 | 0.0 | 276 ms | 0 |
| Tue 04 | 0 | 0.0 | 287 ms | 0 |
| Tue 07 | 0 | 0.0 | 350 ms | 0 |
| Tue 09 | 0 | 0.0 | 276 ms | 0 |
| Tue 11 | 0 | 0.0 | 366 ms | 0 |
| Tue 13 | 0 | 0.0 | 400 ms | 0 |
| Tue 15 | 0 | 0.0 | 392 ms | 0 |
| Tue 17 | 0 | 0.0 | 341 ms | 0 |
| Tue 20 | 0 | 0.0 | 279 ms | 0 |
| Tue 22 | 0 | 0.0 | 399 ms | 0 |
| Wed 00 | 0 | 0.0 | 331 ms | 0 |
| Wed 02 | 0 | 0.0 | 220 ms | 0 |
| Wed 05 | 0 | 0.0 | 239 ms | 0 |
| Wed 07 | 0 | 0.0 | 317 ms | 0 |
| Wed 09 | 0 | 0.0 | 448 ms | 0 |
| Wed 11 | 0 | 0.0 | 360 ms | 0 |
| Wed 13 | 0 | 0.0 | 332 ms | 0 |
| Wed 15 | 0 | 0.0 | 389 ms | 0 |
| Wed 18 | 0 | 0.0 | 406 ms | 0 |
| Wed 20 | 0 | 0.0 | 489 ms | 0 |
| Wed 22 | 0 | 0.0 | 332 ms | 0 |
| Thu 00 | 0 | 0.0 | 549 ms | 0 |
| Thu 02 | 0 | 0.0 | 305 ms | 0 |
| Thu 04 | 0 | 0.0 | 426 ms | 0 |
| Thu 06 | 0 | 0.0 | 185 ms | 0 |
| Thu 08 | 0 | 0.0 | 416 ms | 0 |
| Thu 10 | 0 | 0.0 | 193 ms | 0 |
| Thu 12 | 0 | 0.0 | 291 ms | 0 |
| Thu 15 | 0 | 0.0 | 280 ms | 0 |
| Thu 17 | 0 | 0.0 | 575 ms | 0 |
| Thu 19 | 0 | 0.0 | 434 ms | 0 |
| Thu 21 | 0 | 0.0 | 274 ms | 0 |
| Thu 23 | 0 | 0.0 | 182 ms | 0 |
| Fri 01 | 0 | 0.0 | 348 ms | 0 |
| Fri 03 | 0 | 0.0 | 321 ms | 0 |
| Fri 05 | 0 | 0.0 | 499 ms | 0 |
| Fri 07 | 0 | 0.0 | 397 ms | 0 |
| Fri 09 | 0 | 0.0 | 167 ms | 0 |
| Fri 11 | 0 | 0.0 | 231 ms | 0 |
| Fri 13 | 0 | 0.0 | 201 ms | 0 |
| Fri 15 | 0 | 0.0 | 520 ms | 0 |
| Fri 17 | 0 | 0.0 | 207 ms | 0 |
| Fri 19 | 0 | 0.0 | 190 ms | 0 |
| Fri 20 | 0 | 0.0 | 518 ms | 0 |
| Fri 22 | 0 | 0.0 | 394 ms | 0 |
| Sat 00 | 0 | 0.0 | 191 ms | 0 |
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.
No outages on record for AnySearch 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 AnySearch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AnySearch alerts to Slack, Discord or a webhook — free.
AnySearch is listed in our AI category and checked at anysearch.com. AnySearch is a privacy-first search infrastructure for AI Agents, with anonymous access, smart routing, structured output, and native API, MCP, and Skill integration.
AnySearch publishes an official status page at status.anysearch.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 331 ms average, 167–526 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AnySearch incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
331 ms on average over the last 24 hours (167–526 ms).
Yes, at https://status.anysearch.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report AnySearch here at once, the problem is on AnySearch'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 AnySearch. 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.