User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
qloaked.com · Cloud & developer
Is Qloaked down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 → qloaked.com—
Your browser → us—
Our checksReaching it
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
Reaching it
Last checked 2 hr ago. Last stored result reached it in 185 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 |
|---|---|---|---|---|
| Tue 06 | 0 | 0.0 | 172 ms | 0 |
| Tue 08 | 0 | 0.0 | 404 ms | 0 |
| Tue 10 | 0 | 0.0 | 98 ms | 0 |
| Tue 12 | 0 | 0.0 | 85 ms | 0 |
| Tue 14 | 0 | 0.0 | 247 ms | 0 |
| Tue 16 | 0 | 0.0 | 83 ms | 0 |
| Tue 19 | 0 | 0.0 | 339 ms | 0 |
| Tue 21 | 0 | 0.0 | 506 ms | 0 |
| Tue 23 | 0 | 0.0 | 110 ms | 0 |
| Wed 01 | 0 | 0.0 | 52 ms | 0 |
| Wed 04 | 0 | 0.0 | 71 ms | 0 |
| Wed 06 | 0 | 0.0 | 193 ms | 0 |
| Wed 08 | 0 | 0.0 | 287 ms | 0 |
| Wed 10 | 0 | 0.0 | 258 ms | 0 |
| Wed 13 | 0 | 0.0 | 138 ms | 0 |
| Wed 15 | 0 | 0.0 | 274 ms | 0 |
| Wed 17 | 0 | 0.0 | 280 ms | 0 |
| Wed 19 | 0 | 0.0 | 260 ms | 0 |
| Wed 21 | 0 | 0.0 | 162 ms | 0 |
| Wed 23 | 0 | 0.0 | 267 ms | 0 |
| Thu 02 | 0 | 0.0 | 211 ms | 0 |
| Thu 04 | 0 | 0.0 | 230 ms | 0 |
| Thu 06 | 0 | 0.0 | 134 ms | 0 |
| Thu 08 | 0 | 0.0 | 240 ms | 0 |
| Thu 10 | 0 | 0.0 | 126 ms | 0 |
| Thu 12 | 0 | 0.0 | 244 ms | 0 |
| Thu 14 | 0 | 0.0 | 338 ms | 0 |
| Thu 16 | 0 | 0.0 | 263 ms | 0 |
| Thu 18 | 0 | 0.0 | 253 ms | 0 |
| Thu 20 | 0 | 0.0 | 270 ms | 0 |
| Thu 22 | 0 | 0.0 | 159 ms | 0 |
| Fri 00 | 0 | 0.0 | 92 ms | 0 |
| Fri 02 | 0 | 0.0 | 192 ms | 0 |
| Fri 04 | 0 | 0.0 | 124 ms | 0 |
| Fri 06 | 0 | 0.0 | 302 ms | 0 |
| Fri 07 | 0 | 0.0 | 240 ms | 0 |
| Fri 09 | 0 | 0.0 | 89 ms | 0 |
| Fri 10 | 0 | 0.0 | 304 ms | 0 |
| Fri 12 | 0 | 0.0 | 173 ms | 0 |
| Fri 14 | 0 | 0.0 | 88 ms | 0 |
| Fri 16 | 0 | 0.0 | 185 ms | 0 |
| Fri 17 | 0 | 0.0 | 311 ms | 0 |
| Fri 18 | 0 | 0.0 | 196 ms | 0 |
| Fri 20 | 0 | 0.0 | 280 ms | 0 |
| Fri 22 | 0 | 0.0 | 149 ms | 0 |
| Sat 00 | 0 | 0.0 | 226 ms | 0 |
| Sat 01 | 0 | 0.0 | 75 ms | 0 |
| Sat 03 | 0 | 0.0 | 185 ms | 0 |
Reliability
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.
Embed this status: free live Qloaked 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 Qloaked yet. Outages of 10 minutes or more get their own page here.
Having trouble with Qloaked?
One report per service every 10 minutes from this network. No account.
Follow Qloaked
Get an email when Qloaked goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Qloaked alerts to Slack, Discord or a webhook — free.
About Qloaked
Qloaked is listed in our Cloud & developer category and checked at qloaked.com. Instantly secure the third-party domains pointing at your app. Fully automated.
Qloaked publishes an official status page at status.qloaked.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 192 ms average, 23–311 ms range across 18 successful checks.
Questions
Is Qloaked down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Qloaked last down?
We have not recorded a public Qloaked incident since monitoring began 8 days ago.
What is Qloaked's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Qloaked respond?
192 ms on average over the last 24 hours (23–311 ms).
Does Qloaked have an official status page?
Yes, at https://status.qloaked.com.
Qloaked 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Qloaked here at once, the problem is on Qloaked'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 Qloaked. 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.