User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
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 190 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 171 ms | 0 |
| Tue 04 | 0 | 0.0 | 200 ms | 0 |
| Tue 07 | 0 | 0.0 | 164 ms | 0 |
| Tue 09 | 0 | 0.0 | 220 ms | 0 |
| Tue 11 | 0 | 0.0 | 189 ms | 0 |
| Tue 13 | 0 | 0.0 | 163 ms | 0 |
| Tue 15 | 0 | 0.0 | 227 ms | 0 |
| Tue 17 | 0 | 0.0 | 157 ms | 0 |
| Tue 20 | 0 | 0.0 | 268 ms | 0 |
| Tue 22 | 0 | 0.0 | 196 ms | 0 |
| Wed 00 | 0 | 0.0 | 295 ms | 0 |
| Wed 02 | 0 | 0.0 | 183 ms | 0 |
| Wed 05 | 0 | 0.0 | 179 ms | 0 |
| Wed 07 | 0 | 0.0 | 178 ms | 0 |
| Wed 09 | 0 | 0.0 | 142 ms | 0 |
| Wed 12 | 0 | 0.0 | 160 ms | 0 |
| Wed 14 | 0 | 0.0 | 166 ms | 0 |
| Wed 16 | 0 | 0.0 | 159 ms | 0 |
| Wed 18 | 0 | 0.0 | 160 ms | 0 |
| Wed 20 | 0 | 0.0 | 366 ms | 0 |
| Wed 22 | 0 | 0.0 | 201 ms | 0 |
| Thu 01 | 0 | 0.0 | 228 ms | 0 |
| Thu 03 | 0 | 0.0 | 1493 ms | 0 |
| Thu 05 | 0 | 0.0 | 795 ms | 0 |
| Thu 07 | 0 | 0.0 | 881 ms | 0 |
| Thu 09 | 0 | 0.0 | 203 ms | 0 |
| Thu 11 | 0 | 0.0 | 167 ms | 0 |
| Thu 13 | 0 | 0.0 | 217 ms | 0 |
| Thu 15 | 0 | 0.0 | 211 ms | 0 |
| Thu 17 | 0 | 0.0 | 198 ms | 0 |
| Thu 19 | 0 | 0.0 | 454 ms | 0 |
| Thu 21 | 0 | 0.0 | 274 ms | 0 |
| Thu 23 | 0 | 0.0 | 139 ms | 0 |
| Fri 01 | 0 | 0.0 | 146 ms | 0 |
| Fri 03 | 0 | 0.0 | 258 ms | 0 |
| Fri 06 | 0 | 0.0 | 203 ms | 0 |
| Fri 08 | 0 | 0.0 | 667 ms | 0 |
| Fri 10 | 0 | 0.0 | 151 ms | 0 |
| Fri 11 | 0 | 0.0 | 205 ms | 0 |
| Fri 13 | 0 | 0.0 | 220 ms | 0 |
| Fri 15 | 0 | 0.0 | 248 ms | 0 |
| Fri 17 | 0 | 0.0 | 161 ms | 0 |
| Fri 19 | 0 | 0.0 | 217 ms | 0 |
| Fri 21 | 0 | 0.0 | 164 ms | 0 |
| Fri 23 | 0 | 0.0 | 240 ms | 0 |
| Sat 00 | 0 | 0.0 | 207 ms | 0 |
| Sat 02 | 0 | 0.0 | 175 ms | 0 |
| Sat 04 | 0 | 0.0 | 190 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 Voquent 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 Voquent goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Voquent alerts to Slack, Discord or a webhook — free.
Voquent is listed in our Telecom category and checked at voquent.com. Voquent is a global voice-over service platform that enables both direct contact and fully managed productions in over 1700 distinct languages and dialects. Get outstanding, human, broadcast-quality narration, dubbing, and translation services.
Voquent publishes an official status page at status.voquent.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with telecom services: no service or data, account and billing pages failing, and app sign-in problems.
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: 231 ms average, 132–667 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Voquent incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
231 ms on average over the last 24 hours (132–667 ms).
Yes, at https://status.voquent.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For telecom services, watch for no service or data, account and billing pages failing, and app sign-in problems. If many people report Voquent here at once, the problem is on Voquent'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 Voquent. 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.