User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
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 273 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 275 ms | 0 |
| Tue 11 | 0 | 0.0 | 265 ms | 0 |
| Tue 14 | 0 | 0.0 | 306 ms | 0 |
| Tue 16 | 0 | 0.0 | 383 ms | 0 |
| Tue 18 | 0 | 0.0 | 292 ms | 0 |
| Tue 20 | 0 | 0.0 | 501 ms | 0 |
| Tue 23 | 0 | 0.0 | 278 ms | 0 |
| Wed 01 | 0 | 0.0 | 299 ms | 0 |
| Wed 03 | 0 | 0.0 | 314 ms | 0 |
| Wed 05 | 0 | 0.0 | 331 ms | 0 |
| Wed 07 | 0 | 0.0 | 336 ms | 0 |
| Wed 08 | 0 | 0.0 | 250 ms | 0 |
| Wed 10 | 0 | 0.0 | 350 ms | 0 |
| Wed 12 | 0 | 0.0 | 246 ms | 0 |
| Wed 14 | 0 | 0.0 | 397 ms | 0 |
| Wed 16 | 0 | 0.0 | 637 ms | 0 |
| Wed 18 | 0 | 0.0 | 352 ms | 0 |
| Wed 21 | 0 | 0.0 | 304 ms | 0 |
| Wed 23 | 0 | 0.0 | 327 ms | 0 |
| Thu 01 | 0 | 0.0 | 724 ms | 0 |
| Thu 03 | 0 | 0.0 | 358 ms | 0 |
| Thu 05 | 0 | 0.0 | 343 ms | 0 |
| Thu 07 | 0 | 0.0 | 357 ms | 0 |
| Thu 09 | 0 | 0.0 | 300 ms | 0 |
| Thu 11 | 0 | 0.0 | 323 ms | 0 |
| Thu 13 | 0 | 0.0 | 484 ms | 0 |
| Thu 15 | 0 | 0.0 | 457 ms | 0 |
| Thu 16 | 0 | 0.0 | 339 ms | 0 |
| Thu 18 | 0 | 0.0 | 282 ms | 0 |
| Thu 20 | 0 | 0.0 | 319 ms | 0 |
| Thu 22 | 0 | 0.0 | 277 ms | 0 |
| Fri 00 | 0 | 0.0 | 333 ms | 0 |
| Fri 03 | 0 | 0.0 | 332 ms | 0 |
| Fri 05 | 0 | 0.0 | 300 ms | 0 |
| Fri 07 | 0 | 0.0 | 330 ms | 0 |
| Fri 08 | 0 | 0.0 | 247 ms | 0 |
| Fri 10 | 0 | 0.0 | 279 ms | 0 |
| Fri 11 | 0 | 0.0 | 471 ms | 0 |
| Fri 13 | 0 | 0.0 | 299 ms | 0 |
| Fri 15 | 0 | 0.0 | 260 ms | 0 |
| Fri 17 | 0 | 0.0 | 338 ms | 0 |
| Fri 19 | 0 | 0.0 | 345 ms | 0 |
| Fri 21 | 0 | 0.0 | 298 ms | 0 |
| Fri 23 | 0 | 0.0 | 268 ms | 0 |
| Sat 00 | 0 | 0.0 | 273 ms | 0 |
| Sat 01 | 0 | 0.0 | 301 ms | 0 |
| Sat 03 | 0 | 0.0 | 1329 ms | 0 |
| Sat 04 | 0 | 0.0 | 273 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for VoiceMap 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 VoiceMap goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send VoiceMap alerts to Slack, Discord or a webhook — free.
VoiceMap is listed in our Travel category and checked at voicemap.me. Take a self-guided tour with VoiceMap's audio guide app. There are walking tours, driving tours and even boat rides in over 600 destinations around the world. Or create your own self-guided tour with our straightforward publishing tools.
VoiceMap publishes an official status page at status.voicemap.me; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 374 ms average, 247–1329 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public VoiceMap incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
374 ms on average over the last 24 hours (247–1329 ms).
Yes, at https://status.voicemap.me.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For travel services, watch for booking and check-in failures, flight-status pages not loading, and app errors. If many people report VoiceMap here at once, the problem is on VoiceMap'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 VoiceMap. 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.