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 1 hr ago. Last stored result reached it in 451 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 692 ms | 0 |
| Mon 20 | 0 | 0.0 | 637 ms | 0 |
| Mon 22 | 0 | 0.0 | 513 ms | 0 |
| Tue 00 | 0 | 0.0 | 498 ms | 0 |
| Tue 03 | 0 | 0.0 | 521 ms | 0 |
| Tue 05 | 0 | 0.0 | 506 ms | 0 |
| Tue 07 | 0 | 0.0 | 595 ms | 0 |
| Tue 09 | 0 | 0.0 | 568 ms | 0 |
| Tue 11 | 0 | 0.0 | 510 ms | 0 |
| Tue 13 | 0 | 0.0 | 503 ms | 0 |
| Tue 16 | 0 | 0.0 | 519 ms | 0 |
| Tue 18 | 0 | 0.0 | 526 ms | 0 |
| Tue 20 | 0 | 0.0 | 602 ms | 0 |
| Tue 22 | 0 | 0.0 | 527 ms | 0 |
| Wed 00 | 0 | 0.0 | 596 ms | 0 |
| Wed 03 | 0 | 0.0 | 707 ms | 0 |
| Wed 05 | 0 | 0.0 | 681 ms | 0 |
| Wed 07 | 0 | 0.0 | 318 ms | 0 |
| Wed 09 | 0 | 0.0 | 471 ms | 0 |
| Wed 10 | 0 | 0.0 | 78 ms | 0 |
| Wed 12 | 0 | 0.0 | 478 ms | 0 |
| Wed 14 | 0 | 0.0 | 493 ms | 0 |
| Wed 16 | 0 | 0.0 | 506 ms | 0 |
| Wed 18 | 0 | 0.0 | 524 ms | 0 |
| Wed 20 | 0 | 0.0 | 534 ms | 0 |
| Wed 22 | 0 | 0.0 | 458 ms | 0 |
| Thu 00 | 0 | 0.0 | 653 ms | 0 |
| Thu 02 | 0 | 0.0 | 486 ms | 0 |
| Thu 04 | 0 | 0.0 | 517 ms | 0 |
| Thu 06 | 0 | 0.0 | 422 ms | 0 |
| Thu 08 | 0 | 0.0 | 640 ms | 0 |
| Thu 10 | 0 | 0.0 | 506 ms | 0 |
| Thu 13 | 0 | 0.0 | 540 ms | 0 |
| Thu 15 | 0 | 0.0 | 515 ms | 0 |
| Thu 17 | 0 | 0.0 | 479 ms | 0 |
| Thu 19 | 0 | 0.0 | 589 ms | 0 |
| Thu 21 | 0 | 0.0 | 550 ms | 0 |
| Fri 00 | 0 | 0.0 | 497 ms | 0 |
| Fri 02 | 0 | 0.0 | 521 ms | 0 |
| Fri 04 | 0 | 0.0 | 212 ms | 0 |
| Fri 06 | 0 | 0.0 | 647 ms | 0 |
| Fri 08 | 0 | 0.0 | 593 ms | 0 |
| Fri 10 | 0 | 0.0 | 480 ms | 0 |
| Fri 12 | 0 | 0.0 | 503 ms | 0 |
| Fri 14 | 0 | 0.0 | 558 ms | 0 |
| Fri 16 | 0 | 0.0 | 517 ms | 0 |
| Fri 17 | 0 | 0.0 | 563 ms | 0 |
| Fri 19 | 0 | 0.0 | 451 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Watermelon 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 Watermelon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Watermelon alerts to Slack, Discord or a webhook — free.
Watermelon, at watermelon.ai, is one of the AI services we monitor. Customer service without availability as a bottleneck. Dutch AI Agent that automatically handles repetitive questions. EU-hosted, ISO 27001 certified.
Watermelon publishes an official status page at status.watermelon.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 488 ms average, 40–647 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Watermelon incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
488 ms on average over the last 24 hours (40–647 ms).
Yes, at https://status.watermelon.ai.
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 Watermelon here at once, the problem is on Watermelon'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 Watermelon. 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.