User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Whelp 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 → whelp.co—
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 655 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 14 | 0 | 0.0 | 749 ms | 0 |
| Mon 16 | 0 | 0.0 | 437 ms | 0 |
| Mon 18 | 0 | 0.0 | 731 ms | 0 |
| Mon 20 | 0 | 0.0 | 689 ms | 0 |
| Mon 22 | 0 | 0.0 | 756 ms | 0 |
| Tue 00 | 0 | 0.0 | 680 ms | 0 |
| Tue 03 | 0 | 0.0 | 682 ms | 0 |
| Tue 05 | 0 | 0.0 | 647 ms | 0 |
| Tue 07 | 0 | 0.0 | 723 ms | 0 |
| Tue 09 | 0 | 0.0 | 768 ms | 0 |
| Tue 11 | 0 | 0.0 | 711 ms | 0 |
| Tue 13 | 0 | 0.0 | 719 ms | 0 |
| Tue 16 | 0 | 0.0 | 747 ms | 0 |
| Tue 18 | 0 | 0.0 | 790 ms | 0 |
| Tue 20 | 0 | 0.0 | 741 ms | 0 |
| Tue 22 | 0 | 0.0 | 697 ms | 0 |
| Wed 00 | 0 | 0.0 | 745 ms | 0 |
| Wed 03 | 0 | 0.0 | 833 ms | 0 |
| Wed 05 | 0 | 0.0 | 906 ms | 0 |
| Wed 07 | 0 | 0.0 | 446 ms | 0 |
| Wed 10 | 0 | 0.0 | 6689 ms | 0 |
| Wed 12 | 0 | 0.0 | 721 ms | 0 |
| Wed 14 | 0 | 0.0 | 707 ms | 0 |
| Wed 16 | 0 | 0.0 | 657 ms | 0 |
| Wed 18 | 0 | 0.0 | 688 ms | 0 |
| Wed 20 | 0 | 0.0 | 772 ms | 0 |
| Wed 23 | 0 | 0.0 | 713 ms | 0 |
| Thu 01 | 0 | 0.0 | 749 ms | 0 |
| Thu 03 | 0 | 0.0 | 708 ms | 0 |
| Thu 05 | 0 | 0.0 | 700 ms | 0 |
| Thu 07 | 0 | 0.0 | 661 ms | 0 |
| Thu 09 | 0 | 0.0 | 776 ms | 0 |
| Thu 11 | 0 | 0.0 | 700 ms | 0 |
| Thu 13 | 0 | 0.0 | 652 ms | 0 |
| Thu 15 | 0 | 0.0 | 733 ms | 0 |
| Thu 17 | 0 | 0.0 | 775 ms | 0 |
| Thu 19 | 0 | 0.0 | 763 ms | 0 |
| Thu 21 | 0 | 0.0 | 713 ms | 0 |
| Thu 23 | 0 | 0.0 | 662 ms | 0 |
| Fri 02 | 0 | 0.0 | 669 ms | 0 |
| Fri 03 | 0 | 0.0 | 782 ms | 0 |
| Fri 05 | 0 | 0.0 | 814 ms | 0 |
| Fri 06 | 0 | 0.0 | 799 ms | 0 |
| Fri 08 | 0 | 0.0 | 722 ms | 0 |
| Fri 10 | 0 | 0.0 | 700 ms | 0 |
| Fri 11 | 0 | 0.0 | 780 ms | 0 |
| Fri 13 | 0 | 0.0 | 758 ms | 0 |
| Fri 15 | 0 | 0.0 | 655 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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Whelp 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 Whelp yet. Outages of 10 minutes or more get their own page here.
Having trouble with Whelp?
One report per service every 10 minutes from this network. No account.
Follow Whelp
Get an email when Whelp goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Whelp alerts to Slack, Discord or a webhook — free.
About Whelp
We track Whelp (whelp.co) as part of the AI group. Whelp gives businesses AI Agents that resolve customer questions instantly, plus one inbox for WhatsApp, web chat, SMS, email, voice and social.
Whelp publishes an official status page at status.whelp.co; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 735 ms average, 655–814 ms range across 14 successful checks.
Questions
Is Whelp down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Whelp last down?
We have not recorded a public Whelp incident since monitoring began 6 days ago.
What is Whelp's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Whelp respond?
735 ms on average over the last 24 hours (655–814 ms).
Does Whelp have an official status page?
Yes, at https://status.whelp.co.
Whelp 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 Whelp here at once, the problem is on Whelp'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 Whelp. 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.