User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 23 min ago. Last stored result reached it in 1103 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 875 ms | 0 |
| Mon 18 | 0 | 0.0 | 1125 ms | 0 |
| Mon 20 | 0 | 0.0 | 347 ms | 0 |
| Mon 22 | 0 | 0.0 | 404 ms | 0 |
| Tue 00 | 0 | 0.0 | 317 ms | 0 |
| Tue 02 | 0 | 0.0 | 346 ms | 0 |
| Tue 05 | 0 | 0.0 | 298 ms | 0 |
| Tue 07 | 0 | 0.0 | 1251 ms | 0 |
| Tue 09 | 0 | 0.0 | 101 ms | 0 |
| Tue 11 | 0 | 0.0 | 156 ms | 0 |
| Tue 13 | 0 | 0.0 | 274 ms | 0 |
| Tue 15 | 0 | 0.0 | 564 ms | 0 |
| Tue 17 | 0 | 0.0 | 357 ms | 0 |
| Tue 20 | 0 | 0.0 | 359 ms | 0 |
| Tue 22 | 0 | 0.0 | 361 ms | 0 |
| Wed 00 | 0 | 0.0 | 278 ms | 0 |
| Wed 02 | 0 | 0.0 | 306 ms | 0 |
| Wed 05 | 0 | 0.0 | 318 ms | 0 |
| Wed 07 | 0 | 0.0 | 258 ms | 0 |
| Wed 09 | 0 | 0.0 | 299 ms | 0 |
| Wed 11 | 0 | 0.0 | 617 ms | 0 |
| Wed 14 | 0 | 0.0 | 397 ms | 0 |
| Wed 16 | 0 | 0.0 | 534 ms | 0 |
| Wed 18 | 0 | 0.0 | 317 ms | 0 |
| Wed 20 | 0 | 0.0 | 469 ms | 0 |
| Wed 22 | 0 | 0.0 | 328 ms | 0 |
| Thu 00 | 0 | 0.0 | 140 ms | 0 |
| Thu 02 | 0 | 0.0 | 333 ms | 0 |
| Thu 04 | 0 | 0.0 | 115 ms | 0 |
| Thu 07 | 0 | 0.0 | 352 ms | 0 |
| Thu 09 | 0 | 0.0 | 318 ms | 0 |
| Thu 11 | 0 | 0.0 | 455 ms | 0 |
| Thu 13 | 0 | 0.0 | 100 ms | 0 |
| Thu 15 | 0 | 0.0 | 331 ms | 0 |
| Thu 17 | 0 | 0.0 | 332 ms | 0 |
| Thu 19 | 0 | 0.0 | 276 ms | 0 |
| Thu 21 | 0 | 0.0 | 518 ms | 0 |
| Thu 23 | 0 | 0.0 | 1003 ms | 0 |
| Fri 01 | 0 | 0.0 | 408 ms | 0 |
| Fri 03 | 0 | 0.0 | 108 ms | 0 |
| Fri 05 | 0 | 0.0 | 867 ms | 0 |
| Fri 07 | 0 | 0.0 | 369 ms | 0 |
| Fri 08 | 0 | 0.0 | 289 ms | 0 |
| Fri 10 | 0 | 0.0 | 418 ms | 0 |
| Fri 12 | 0 | 0.0 | 499 ms | 0 |
| Fri 14 | 0 | 0.0 | 306 ms | 0 |
| Fri 16 | 0 | 0.0 | 1103 ms | 0 |
| Fri 17 | 0 | 0.0 | 319 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 Aha! 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 Aha! goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Aha! alerts to Slack, Discord or a webhook — free.
We track Aha! (aha.io) as part of the Cloud & developer group. Aha! is the world's #1 product management software. See why 1,000,000+ product builders trust us to build lovable products and be happy doing it.
Aha! publishes an official status page at status.aha.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: 487 ms average, 108–1103 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Aha! incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
487 ms on average over the last 24 hours (108–1103 ms).
Yes, at https://status.aha.io.
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 Aha! here at once, the problem is on Aha!'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 Aha!. 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.