User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Telecom
Is QuestBlue down?
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
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → questblue.com—
Your browser → us—
Our checksNot enough checks
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Not enough checks
Last checked 33 min ago. Last stored result reached it in 10 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 746 ms | 0 |
| Mon 20 | 0 | 0.0 | 838 ms | 0 |
| Mon 22 | 0 | 0.0 | 721 ms | 0 |
| Tue 00 | 0 | 0.0 | 451 ms | 0 |
| Tue 02 | 0 | 0.0 | 689 ms | 0 |
| Tue 05 | 0 | 0.0 | 720 ms | 0 |
| Tue 06 | 0 | 0.0 | 727 ms | 0 |
| Tue 09 | 0 | 0.0 | 735 ms | 0 |
| Tue 11 | 0 | 0.0 | 678 ms | 0 |
| Tue 13 | 0 | 0.0 | 678 ms | 0 |
| Tue 15 | 0 | 0.0 | 754 ms | 0 |
| Tue 17 | 0 | 0.0 | 708 ms | 0 |
| Tue 20 | 0 | 0.0 | 476 ms | 0 |
| Tue 22 | 0 | 0.0 | 765 ms | 0 |
| Wed 00 | 0 | 0.0 | 770 ms | 0 |
| Wed 02 | 0 | 0.0 | 843 ms | 0 |
| Wed 05 | 0 | 0.0 | 736 ms | 0 |
| Wed 07 | 0 | 0.0 | 753 ms | 0 |
| Wed 09 | 0 | 0.0 | 638 ms | 0 |
| Wed 11 | 0 | 0.0 | 736 ms | 0 |
| Wed 14 | 0 | 0.0 | 783 ms | 0 |
| Wed 16 | 0 | 0.0 | 769 ms | 0 |
| Wed 18 | 0 | 0.0 | 756 ms | 0 |
| Wed 20 | 0 | 0.0 | 747 ms | 0 |
| Wed 22 | 0 | 0.0 | 759 ms | 0 |
| Thu 00 | 0 | 0.0 | 709 ms | 0 |
| Thu 01 | 0 | 0.0 | 749 ms | 0 |
| Thu 03 | 0 | 0.0 | 788 ms | 0 |
| Thu 05 | 0 | 0.0 | 7128 ms | 0 |
| Thu 07 | 0 | 0.0 | 517 ms | 0 |
| Thu 09 | 0 | 0.0 | 584 ms | 0 |
| Thu 11 | 0 | 0.0 | 845 ms | 0 |
| Thu 13 | 0 | 0.0 | 717 ms | 0 |
| Thu 15 | 0 | 0.0 | 806 ms | 0 |
| Thu 17 | 0 | 0.0 | 23 ms | 0 |
| Thu 19 | 0 | 0.0 | 67 ms | 0 |
| Thu 21 | 0 | 0.0 | 70 ms | 0 |
| Thu 23 | 0 | 0.0 | 69 ms | 0 |
| Fri 02 | 0 | 0.0 | 105 ms | 0 |
| Fri 04 | 0 | 0.0 | 16 ms | 0 |
| Fri 06 | 0 | 0.0 | 60 ms | 0 |
| Fri 08 | 0 | 0.0 | 16 ms | 0 |
| Fri 10 | 0 | 0.0 | 20 ms | 0 |
| Fri 11 | 0 | 0.0 | 38 ms | 0 |
| Fri 12 | 0 | 0.0 | 20 ms | 0 |
| Fri 14 | 0 | 0.0 | 64 ms | 0 |
| Fri 17 | 0 | 0.0 | 32 ms | 0 |
| Fri 18 | 0 | 0.0 | 35 ms | 0 |
Reliability
98.65%Uptime · 30 days
98.65%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
98.65% 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.
Embed this status: free live QuestBlue badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for QuestBlue yet. Outages of 10 minutes or more get their own page here.
Having trouble with QuestBlue?
One report per service every 10 minutes from this network. No account.
Follow QuestBlue
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.
About QuestBlue
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.65% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 47 ms average, 10–105 ms range across 16 successful checks.
Questions
Is QuestBlue down right now?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
When was QuestBlue last down?
We have not recorded a public QuestBlue incident since monitoring began 7 days ago.
What is QuestBlue's uptime?
From our own checks: 98.65% over 7 days of checks.
How fast does QuestBlue respond?
47 ms on average over the last 24 hours (10–105 ms).
Does QuestBlue have an official status page?
Yes, at https://status.questblue.com.
QuestBlue not working for me but the status is fine. What now?
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.