User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: ASR Service (US) — Service disruption | ASR Service (US) — Degraded performance
Source: the vendor's status page · We are not affiliated with Plaud Developer.
Estimated fix: Not enough Plaud Developer history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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.
Reachable from all 4 regions we check from.
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.
Not enough checks
Last checked 11 min ago. Last stored result reached it in 7 ms.
Critical incident
ASR Service (US) — Service disruption | ASR Service (US) — Degraded performance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 07:45 | 0 | 0.0 | 308 ms | 0 |
| 09:45 | 0 | 0.0 | 368 ms | 0 |
| 11:45 | 0 | 0.0 | 171 ms | 0 |
| 14:00 | 0 | 0.0 | 47 ms | 0 |
| 16:00 | 0 | 0.0 | 160 ms | 0 |
| 18:00 | 0 | 0.0 | 33 ms | 0 |
| 20:00 | 0 | 0.0 | 19 ms | 0 |
| 22:15 | 0 | 0.0 | 22 ms | 0 |
| 00:00 | 0 | 0.0 | 22 ms | 0 |
| 02:15 | 0 | 0.0 | 350 ms | 0 |
| 04:15 | 0 | 0.0 | 32 ms | 0 |
| 06:30 | 0 | 0.0 | 12 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 Plaud Developer 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 Plaud Developer goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Plaud Developer alerts to Slack, Discord or a webhook — free.
Plaud Developer is listed in our AI category and checked at plaud.ai. The only AI note-taking platform that bridges in-person, phone calls, and online meetings into one workflow, trusted by 3 million+ users globally. Discover P...
Plaud Developer publishes an official status page at status.plaud.ai; 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: 120 ms average, 7–368 ms range across 13 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: ASR Service (US) — Service disruption | ASR Service (US) — Degraded performance
We have not recorded a public Plaud Developer incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
120 ms on average over the last 24 hours (7–368 ms). Latest regional checks: US East 6 ms, US West 6 ms, Europe 12 ms, Asia-Pacific 360 ms.
Yes, at https://status.plaud.ai.
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 Plaud Developer here at once, the problem is on Plaud Developer'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 Plaud Developer. 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.