Status
API status
A live check of the speech-to-text API every 5 minutes: the health endpoint and a short real stream with Finalize. Times are Eastern.
Last 24 hours
One bar per check, every 5 minutes. Hover or tap a bar for its time and result.
Finalize to final transcript
Milliseconds from sending Finalize to receiving the final transcript, for each working check. Measured from our web server in US East, so it includes only a very short network hop; add your own round trip.
Show the last 24 hours as a table
| Hour (ET) | Checks | Down | Slow | Median ms |
|---|---|---|---|---|
| No checks yet. | ||||
How we check
- Every 5 minutes, from our web server in US East, we call
GET https://api.saidwire.com/healthand open a real stream onwss://api.saidwire.com/v1/listen: 2.5 seconds of speech in 100 ms frames at real-time pace, thenFinalize. The words that come back must match. - Working: the final transcript arrived within 250 ms of Finalize, the words matched, and the health endpoint said "ok".
- Slow or partly working: the stream worked, but the final took longer than 250 ms, the words were wrong, or the health endpoint was not "ok". These checks still count as up.
- Down: the stream failed (refused, dropped, or no final within 5 s), and failed again on a retry 10 seconds later.
- Uptime is the share of checks that were working or slow. It covers the time since checks began, up to 30 days.
These checks don't see your network or your region. If the API looks fine here but not for you, email support@saidwire.com with a request_id. During the public beta there is no uptime commitment unless we agree one in writing (see the API terms).
For machines: api.saidwire.com/health (live state of the serving API) and /static/status/status.json (the data on this page).