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 33 min ago. Last stored result reached it in 533 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 575 ms | 0 |
| Nov 7 | 0 | 0.0 | 695 ms | 0 |
| Nov 7 | 0 | 0.0 | 806 ms | 0 |
| Nov 7 | 0 | 0.0 | 520 ms | 0 |
| Nov 7 | 0 | 0.0 | 693 ms | 0 |
| Nov 8 | 0 | 0.0 | 668 ms | 0 |
| Nov 8 | 0 | 0.0 | 790 ms | 0 |
| Nov 8 | 0 | 0.0 | 577 ms | 0 |
| Nov 8 | 0 | 0.0 | 576 ms | 0 |
| Nov 9 | 0 | 0.0 | 735 ms | 0 |
| Nov 9 | 0 | 0.0 | 643 ms | 0 |
| Nov 9 | 0 | 0.0 | 632 ms | 0 |
| Nov 9 | 0 | 0.0 | 625 ms | 0 |
| Nov 10 | 0 | 0.0 | 611 ms | 0 |
| Nov 10 | 0 | 0.0 | 747 ms | 0 |
| Nov 10 | 0 | 0.0 | 639 ms | 0 |
| Nov 10 | 0 | 0.0 | 632 ms | 0 |
| Nov 11 | 0 | 0.0 | 720 ms | 0 |
| Nov 11 | 0 | 0.0 | 704 ms | 0 |
| Nov 11 | 0 | 0.0 | 758 ms | 0 |
| Nov 11 | 0 | 0.0 | 737 ms | 0 |
| Nov 12 | 0 | 0.0 | 597 ms | 0 |
| Nov 12 | 0 | 0.0 | 549 ms | 0 |
| Nov 12 | 0 | 0.0 | 633 ms | 0 |
| Nov 12 | 0 | 0.0 | 595 ms | 0 |
| Nov 13 | 0 | 0.0 | 581 ms | 0 |
| Nov 13 | 0 | 0.0 | 542 ms | 0 |
| Nov 13 | 0 | 0.0 | 677 ms | 0 |
| Nov 13 | 0 | 0.0 | 545 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 Hackle 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 Hackle goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Hackle alerts to Slack, Discord or a webhook — free.
We track Hackle (hackle.io) as part of the AI group. Unlock growth with data-driven decisions. Hackle combines behavior analytics, A/B testing, CRM marketing, feature flags, and remote config into one AI-powered platform — empowering marketers, PMs, and developers to move faster, smarter.
Hackle publishes an official status page at status.hackle.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 605 ms average, 493–828 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Hackle incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
605 ms on average over the last 24 hours (493–828 ms).
Yes, at https://status.hackle.io.
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 Hackle here at once, the problem is on Hackle'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 Hackle. 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.