User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Fetch.ai 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 → fetch.ai—
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 1 hr ago. Last stored result reached it in 277 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 341 ms | 0 |
| Mon 23 | 0 | 0.0 | 456 ms | 0 |
| Tue 01 | 0 | 0.0 | 532 ms | 0 |
| Tue 04 | 0 | 0.0 | 333 ms | 0 |
| Tue 06 | 0 | 0.0 | 392 ms | 0 |
| Tue 08 | 0 | 0.0 | 211 ms | 0 |
| Tue 10 | 0 | 0.0 | 452 ms | 0 |
| Tue 12 | 0 | 0.0 | 296 ms | 0 |
| Tue 14 | 0 | 0.0 | 549 ms | 0 |
| Tue 17 | 0 | 0.0 | 319 ms | 0 |
| Tue 19 | 0 | 0.0 | 441 ms | 0 |
| Tue 21 | 0 | 0.0 | 447 ms | 0 |
| Tue 23 | 0 | 0.0 | 274 ms | 0 |
| Wed 01 | 0 | 0.0 | 290 ms | 0 |
| Wed 04 | 0 | 0.0 | 230 ms | 0 |
| Wed 05 | 0 | 0.0 | 292 ms | 0 |
| Wed 06 | 0 | 0.0 | 386 ms | 0 |
| Wed 08 | 0 | 0.0 | 309 ms | 0 |
| Wed 11 | 0 | 0.0 | 350 ms | 0 |
| Wed 13 | 0 | 0.0 | 435 ms | 0 |
| Wed 15 | 0 | 0.0 | 375 ms | 0 |
| Wed 17 | 0 | 0.0 | 330 ms | 0 |
| Wed 19 | 0 | 0.0 | 280 ms | 0 |
| Wed 21 | 0 | 0.0 | 317 ms | 0 |
| Wed 23 | 0 | 0.0 | 309 ms | 0 |
| Thu 02 | 0 | 0.0 | 407 ms | 0 |
| Thu 04 | 0 | 0.0 | 659 ms | 0 |
| Thu 05 | 0 | 0.0 | 412 ms | 0 |
| Thu 07 | 0 | 0.0 | 362 ms | 0 |
| Thu 09 | 0 | 0.0 | 295 ms | 0 |
| Thu 11 | 0 | 0.0 | 249 ms | 0 |
| Thu 13 | 0 | 0.0 | 503 ms | 0 |
| Thu 15 | 0 | 0.0 | 459 ms | 0 |
| Thu 17 | 0 | 0.0 | 472 ms | 0 |
| Thu 19 | 0 | 0.0 | 508 ms | 0 |
| Thu 21 | 0 | 0.0 | 286 ms | 0 |
| Thu 23 | 0 | 0.0 | 305 ms | 0 |
| Fri 01 | 0 | 0.0 | 435 ms | 0 |
| Fri 04 | 0 | 0.0 | 244 ms | 0 |
| Fri 06 | 0 | 0.0 | 421 ms | 0 |
| Fri 07 | 0 | 0.0 | 237 ms | 0 |
| Fri 09 | 0 | 0.0 | 301 ms | 0 |
| Fri 10 | 0 | 0.0 | 241 ms | 0 |
| Fri 11 | 0 | 0.0 | 285 ms | 0 |
| Fri 13 | 0 | 0.0 | 437 ms | 0 |
| Fri 15 | 0 | 0.0 | 351 ms | 0 |
| Fri 17 | 0 | 0.0 | 588 ms | 0 |
| Fri 18 | 0 | 0.0 | 277 ms | 0 |
Reliability
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 Fetch.ai 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 Fetch.ai yet. Outages of 10 minutes or more get their own page here.
Having trouble with Fetch.ai?
One report per service every 10 minutes from this network. No account.
Follow Fetch.ai
Get an email when Fetch.ai goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fetch.ai alerts to Slack, Discord or a webhook — free.
About Fetch.ai
Fetch.ai is listed in our AI category and checked at fetch.ai. The Complete Ecosystem for the Agentic Economy.
Fetch.ai publishes an official status page at status.fetch.ai; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 361 ms average, 233–942 ms range across 15 successful checks.
Questions
Is Fetch.ai down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Fetch.ai last down?
We have not recorded a public Fetch.ai incident since monitoring began 8 days ago.
What is Fetch.ai's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Fetch.ai respond?
361 ms on average over the last 24 hours (233–942 ms).
Does Fetch.ai have an official status page?
Yes, at https://status.fetch.ai.
Fetch.ai 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 AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Fetch.ai here at once, the problem is on Fetch.ai'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 Fetch.ai. 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.