User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
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.
Our checks can't reach QuestBlue right now
QuestBlue is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 2 hr ago. Last stored result reached it in 10 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 718 ms | 0 |
| Nov 7 | 0 | 0.0 | 695 ms | 0 |
| Nov 8 | 0 | 0.0 | 741 ms | 0 |
| Nov 8 | 0 | 0.0 | 725 ms | 0 |
| Nov 8 | 0 | 0.0 | 720 ms | 0 |
| Nov 8 | 0 | 0.0 | 715 ms | 0 |
| Nov 9 | 0 | 0.0 | 753 ms | 0 |
| Nov 9 | 0 | 0.0 | 635 ms | 0 |
| Nov 9 | 0 | 0.0 | 681 ms | 1 |
| Nov 9 | 0 | 0.0 | 746 ms | 0 |
| Nov 10 | 0 | 0.0 | 699 ms | 0 |
| Nov 10 | 0 | 0.0 | 728 ms | 0 |
| Nov 10 | 0 | 0.0 | 708 ms | 0 |
| Nov 10 | 0 | 0.0 | 621 ms | 0 |
| Nov 11 | 0 | 0.0 | 770 ms | 0 |
| Nov 11 | 0 | 0.0 | 736 ms | 0 |
| Nov 11 | 0 | 0.0 | 776 ms | 0 |
| Nov 11 | 0 | 0.0 | 756 ms | 0 |
| Nov 12 | 0 | 0.0 | 769 ms | 0 |
| Nov 12 | 0 | 0.0 | 584 ms | 0 |
| Nov 12 | 0 | 0.0 | 717 ms | 0 |
| Nov 12 | 0 | 0.0 | 68 ms | 0 |
| Nov 13 | 0 | 0.0 | 61 ms | 0 |
| Nov 13 | 0 | 0.0 | 29 ms | 0 |
| Nov 13 | 0 | 0.0 | 32 ms | 0 |
| Nov 13 | 0 | 0.0 | 35 ms | 0 |
98.68% 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.
No outages on record for QuestBlue 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 QuestBlue goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send QuestBlue alerts to Slack, Discord or a webhook — free.
QuestBlue, at questblue.com, is one of the Telecom services we monitor. QuestBlue is the global cloud communications platform companies choose for cloud-ready voice, text, fax, and emergency services.
QuestBlue publishes an official status page at status.questblue.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with telecom services: no service or data, account and billing pages failing, and app sign-in problems.
Measured uptime from our checks: 98.68% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 44 ms average, 10–105 ms range across 14 successful checks.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
We have not recorded a public QuestBlue incident since monitoring began 7 days ago.
From our own checks: 98.68% over 7 days of checks.
44 ms on average over the last 24 hours (10–105 ms).
Yes, at https://status.questblue.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 QuestBlue here at once, the problem is on QuestBlue'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 QuestBlue. 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.