User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Monologue 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 → monologue.to—
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 232 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 20 | 0 | 0.0 | 744 ms | 0 |
| Mon 22 | 0 | 0.0 | 859 ms | 0 |
| Tue 00 | 0 | 0.0 | 122 ms | 0 |
| Tue 02 | 0 | 0.0 | 177 ms | 0 |
| Tue 04 | 0 | 0.0 | 270 ms | 0 |
| Tue 06 | 0 | 0.0 | 260 ms | 0 |
| Tue 08 | 0 | 0.0 | 112 ms | 0 |
| Tue 11 | 0 | 0.0 | 111 ms | 0 |
| Tue 13 | 0 | 0.0 | 684 ms | 0 |
| Tue 15 | 0 | 0.0 | 732 ms | 0 |
| Tue 17 | 0 | 0.0 | 168 ms | 0 |
| Tue 20 | 0 | 0.0 | 248 ms | 0 |
| Tue 22 | 0 | 0.0 | 745 ms | 0 |
| Wed 00 | 0 | 0.0 | 100 ms | 0 |
| Wed 02 | 0 | 0.0 | 890 ms | 0 |
| Wed 05 | 0 | 0.0 | 250 ms | 0 |
| Wed 07 | 0 | 0.0 | 673 ms | 0 |
| Wed 09 | 0 | 0.0 | 130 ms | 0 |
| Wed 11 | 0 | 0.0 | 231 ms | 0 |
| Wed 13 | 0 | 0.0 | 232 ms | 0 |
| Wed 15 | 0 | 0.0 | 905 ms | 0 |
| Wed 18 | 0 | 0.0 | 1002 ms | 0 |
| Wed 20 | 0 | 0.0 | 195 ms | 0 |
| Wed 22 | 0 | 0.0 | 271 ms | 0 |
| Thu 00 | 0 | 0.0 | 470 ms | 0 |
| Thu 02 | 0 | 0.0 | 252 ms | 0 |
| Thu 04 | 0 | 0.0 | 206 ms | 0 |
| Thu 06 | 0 | 0.0 | 252 ms | 0 |
| Thu 08 | 0 | 0.0 | 156 ms | 0 |
| Thu 10 | 0 | 0.0 | 647 ms | 0 |
| Thu 13 | 0 | 0.0 | 217 ms | 0 |
| Thu 15 | 0 | 0.0 | 839 ms | 0 |
| Thu 17 | 0 | 0.0 | 179 ms | 0 |
| Thu 19 | 0 | 0.0 | 243 ms | 0 |
| Thu 21 | 0 | 0.0 | 155 ms | 0 |
| Thu 23 | 0 | 0.0 | 134 ms | 0 |
| Fri 00 | 0 | 0.0 | 686 ms | 0 |
| Fri 02 | 0 | 0.0 | 1015 ms | 0 |
| Fri 04 | 0 | 0.0 | 268 ms | 0 |
| Fri 06 | 0 | 0.0 | 828 ms | 0 |
| Fri 08 | 0 | 0.0 | 85 ms | 0 |
| Fri 10 | 0 | 0.0 | 575 ms | 0 |
| Fri 11 | 0 | 0.0 | 763 ms | 0 |
| Fri 12 | 0 | 0.0 | 146 ms | 0 |
| Fri 13 | 0 | 0.0 | 87 ms | 0 |
| Fri 15 | 0 | 0.0 | 303 ms | 0 |
| Fri 17 | 0 | 0.0 | 152 ms | 0 |
| Fri 18 | 0 | 0.0 | 232 ms | 0 |
Reliability
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Monologue 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 Monologue yet. Outages of 10 minutes or more get their own page here.
Having trouble with Monologue?
One report per service every 10 minutes from this network. No account.
Follow Monologue
Get an email when Monologue goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Monologue alerts to Slack, Discord or a webhook — free.
About Monologue
Monologue is listed in our AI category and checked at monologue.to. Monologue brings voice dictation, voice notes, and bot-free meeting transcription together in one app for Mac, iPhone, iPad, and Apple Watch.
Monologue publishes an official status page at status.monologue.to; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 372 ms average, 85–1015 ms range across 15 successful checks.
Questions
Is Monologue down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Monologue last down?
We have not recorded a public Monologue incident since monitoring began 7 days ago.
What is Monologue's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Monologue respond?
372 ms on average over the last 24 hours (85–1015 ms).
Does Monologue have an official status page?
Yes, at https://status.monologue.to.
Monologue 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 Monologue here at once, the problem is on Monologue'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 Monologue. 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.