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 2 hr ago. Last stored result reached it in 153 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 154 ms | 0 |
| Tue 03 | 0 | 0.0 | 206 ms | 0 |
| Tue 05 | 0 | 0.0 | 172 ms | 0 |
| Tue 07 | 0 | 0.0 | 157 ms | 0 |
| Tue 09 | 0 | 0.0 | 215 ms | 0 |
| Tue 12 | 0 | 0.0 | 130 ms | 0 |
| Tue 14 | 0 | 0.0 | 126 ms | 0 |
| Tue 16 | 0 | 0.0 | 197 ms | 0 |
| Tue 18 | 0 | 0.0 | 54 ms | 0 |
| Tue 21 | 0 | 0.0 | 134 ms | 0 |
| Tue 23 | 0 | 0.0 | 181 ms | 0 |
| Wed 01 | 0 | 0.0 | 72 ms | 0 |
| Wed 03 | 0 | 0.0 | 175 ms | 0 |
| Wed 06 | 0 | 0.0 | 148 ms | 0 |
| Wed 08 | 0 | 0.0 | 55 ms | 0 |
| Wed 10 | 0 | 0.0 | 189 ms | 0 |
| Wed 12 | 0 | 0.0 | 230 ms | 0 |
| Wed 14 | 0 | 0.0 | 73 ms | 0 |
| Wed 16 | 0 | 0.0 | 199 ms | 0 |
| Wed 19 | 0 | 0.0 | 251 ms | 0 |
| Wed 21 | 0 | 0.0 | 139 ms | 0 |
| Wed 23 | 0 | 0.0 | 170 ms | 0 |
| Thu 01 | 0 | 0.0 | 208 ms | 0 |
| Thu 03 | 0 | 0.0 | 126 ms | 0 |
| Thu 05 | 0 | 0.0 | 173 ms | 0 |
| Thu 07 | 0 | 0.0 | 171 ms | 0 |
| Thu 09 | 0 | 0.0 | 183 ms | 0 |
| Thu 12 | 0 | 0.0 | 211 ms | 0 |
| Thu 14 | 0 | 0.0 | 167 ms | 0 |
| Thu 16 | 0 | 0.0 | 67 ms | 0 |
| Thu 18 | 0 | 0.0 | 139 ms | 0 |
| Thu 20 | 0 | 0.0 | 208 ms | 0 |
| Thu 22 | 0 | 0.0 | 413 ms | 0 |
| Fri 00 | 0 | 0.0 | 207 ms | 0 |
| Fri 02 | 0 | 0.0 | 145 ms | 0 |
| Fri 04 | 0 | 0.0 | 187 ms | 0 |
| Fri 06 | 0 | 0.0 | 166 ms | 0 |
| Fri 08 | 0 | 0.0 | 123 ms | 0 |
| Fri 10 | 0 | 0.0 | 123 ms | 0 |
| Fri 11 | 0 | 0.0 | 118 ms | 0 |
| Fri 13 | 0 | 0.0 | 188 ms | 0 |
| Fri 15 | 0 | 0.0 | 188 ms | 0 |
| Fri 17 | 0 | 0.0 | 154 ms | 0 |
| Fri 18 | 0 | 0.0 | 154 ms | 0 |
| Fri 20 | 0 | 0.0 | 204 ms | 0 |
| Fri 22 | 0 | 0.0 | 171 ms | 0 |
| Sat 00 | 0 | 0.0 | 140 ms | 0 |
| Sat 02 | 0 | 0.0 | 153 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 Rosie 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 Rosie goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Rosie alerts to Slack, Discord or a webhook — free.
Rosie, at heyrosie.com, is one of the AI services we monitor. Never miss another call with our AI-powered call answering service. 10x better than voicemail. 10x cheaper than a traditional phone answering service.
Rosie publishes an official status page at status.heyrosie.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 157 ms average, 118–204 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Rosie incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
157 ms on average over the last 24 hours (118–204 ms).
Yes, at https://status.heyrosie.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 Rosie here at once, the problem is on Rosie'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 Rosie. 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.