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 11 min ago. Last stored result reached it in 58 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 298 ms | 0 |
| Mon 15 | 0 | 0.0 | 160 ms | 0 |
| Mon 18 | 0 | 0.0 | 286 ms | 0 |
| Mon 20 | 0 | 0.0 | 182 ms | 0 |
| Mon 22 | 0 | 0.0 | 242 ms | 0 |
| Tue 00 | 0 | 0.0 | 111 ms | 0 |
| Tue 02 | 0 | 0.0 | 158 ms | 0 |
| Tue 04 | 0 | 0.0 | 184 ms | 0 |
| Tue 06 | 0 | 0.0 | 281 ms | 0 |
| Tue 08 | 0 | 0.0 | 200 ms | 0 |
| Tue 10 | 0 | 0.0 | 199 ms | 0 |
| Tue 13 | 0 | 0.0 | 193 ms | 0 |
| Tue 15 | 0 | 0.0 | 527 ms | 0 |
| Tue 17 | 0 | 0.0 | 300 ms | 0 |
| Tue 19 | 0 | 0.0 | 49 ms | 0 |
| Tue 22 | 0 | 0.0 | 136 ms | 0 |
| Wed 00 | 0 | 0.0 | 501 ms | 0 |
| Wed 02 | 0 | 0.0 | 199 ms | 0 |
| Wed 04 | 0 | 0.0 | 87 ms | 0 |
| Wed 07 | 0 | 0.0 | 93 ms | 0 |
| Wed 09 | 0 | 0.0 | 148 ms | 0 |
| Wed 11 | 0 | 0.0 | 182 ms | 0 |
| Wed 13 | 0 | 0.0 | 227 ms | 0 |
| Wed 15 | 0 | 0.0 | 177 ms | 0 |
| Wed 17 | 0 | 0.0 | 208 ms | 0 |
| Wed 20 | 0 | 0.0 | 244 ms | 0 |
| Wed 22 | 0 | 0.0 | 235 ms | 0 |
| Thu 00 | 0 | 0.0 | 178 ms | 0 |
| Thu 02 | 0 | 0.0 | 203 ms | 0 |
| Thu 04 | 0 | 0.0 | 336 ms | 0 |
| Thu 06 | 0 | 0.0 | 186 ms | 0 |
| Thu 08 | 0 | 0.0 | 716 ms | 0 |
| Thu 10 | 0 | 0.0 | 441 ms | 0 |
| Thu 12 | 0 | 0.0 | 284 ms | 0 |
| Thu 14 | 0 | 0.0 | 192 ms | 0 |
| Thu 16 | 0 | 0.0 | 110 ms | 0 |
| Thu 18 | 0 | 0.0 | 206 ms | 0 |
| Thu 20 | 0 | 0.0 | 218 ms | 0 |
| Thu 22 | 0 | 0.0 | 149 ms | 0 |
| Fri 00 | 0 | 0.0 | 95 ms | 0 |
| Fri 02 | 0 | 0.0 | 195 ms | 0 |
| Fri 05 | 0 | 0.0 | 220 ms | 0 |
| Fri 07 | 0 | 0.0 | 168 ms | 0 |
| Fri 08 | 0 | 0.0 | 226 ms | 0 |
| Fri 10 | 0 | 0.0 | 68 ms | 0 |
| Fri 11 | 0 | 0.0 | 110 ms | 0 |
| Fri 13 | 0 | 0.0 | 155 ms | 0 |
| Fri 15 | 0 | 0.0 | 126 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 Userflow 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 Userflow goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Userflow alerts to Slack, Discord or a webhook — free.
Userflow is listed in our AI category and checked at userflow.com. Userflow is the AI-powered product adoption engine for customer-obsessed teams. Build in-app onboarding, guide users in the moment, and know what to improve next—all in one platform.
Userflow publishes an official status page at status.userflow.com; 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: 158 ms average, 58–226 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 Userflow incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
158 ms on average over the last 24 hours (58–226 ms).
Yes, at https://status.userflow.com.
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 Userflow here at once, the problem is on Userflow'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 Userflow. 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.