User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
uniqode.com · Cloud & developer
Is Uniqode 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 → uniqode.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 75 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 66 ms | 0 |
| Mon 23 | 0 | 0.0 | 44 ms | 0 |
| Tue 01 | 0 | 0.0 | 142 ms | 0 |
| Tue 03 | 0 | 0.0 | 129 ms | 0 |
| Tue 05 | 0 | 0.0 | 37 ms | 0 |
| Tue 07 | 0 | 0.0 | 141 ms | 0 |
| Tue 09 | 0 | 0.0 | 104 ms | 0 |
| Tue 11 | 0 | 0.0 | 66 ms | 0 |
| Tue 13 | 0 | 0.0 | 125 ms | 0 |
| Tue 16 | 0 | 0.0 | 50 ms | 0 |
| Tue 18 | 0 | 0.0 | 157 ms | 0 |
| Tue 20 | 0 | 0.0 | 233 ms | 0 |
| Tue 23 | 0 | 0.0 | 123 ms | 0 |
| Wed 01 | 0 | 0.0 | 85 ms | 0 |
| Wed 03 | 0 | 0.0 | 92 ms | 0 |
| Wed 05 | 0 | 0.0 | 77 ms | 0 |
| Wed 07 | 0 | 0.0 | 55 ms | 0 |
| Wed 10 | 0 | 0.0 | 122 ms | 0 |
| Wed 12 | 0 | 0.0 | 115 ms | 0 |
| Wed 14 | 0 | 0.0 | 102 ms | 0 |
| Wed 16 | 0 | 0.0 | 47 ms | 0 |
| Wed 18 | 0 | 0.0 | 74 ms | 0 |
| Wed 21 | 0 | 0.0 | 244 ms | 0 |
| Wed 23 | 0 | 0.0 | 111 ms | 0 |
| Thu 01 | 0 | 0.0 | 136 ms | 0 |
| Thu 03 | 0 | 0.0 | 121 ms | 0 |
| Thu 05 | 0 | 0.0 | 112 ms | 0 |
| Thu 07 | 0 | 0.0 | 134 ms | 0 |
| Thu 09 | 0 | 0.0 | 145 ms | 0 |
| Thu 11 | 0 | 0.0 | 44 ms | 0 |
| Thu 13 | 0 | 0.0 | 121 ms | 0 |
| Thu 15 | 0 | 0.0 | 144 ms | 0 |
| Thu 17 | 0 | 0.0 | 99 ms | 0 |
| Thu 20 | 0 | 0.0 | 79 ms | 0 |
| Thu 22 | 0 | 0.0 | 58 ms | 0 |
| Fri 00 | 0 | 0.0 | 54 ms | 0 |
| Fri 02 | 0 | 0.0 | 130 ms | 0 |
| Fri 04 | 0 | 0.0 | 165 ms | 0 |
| Fri 05 | 0 | 0.0 | 98 ms | 0 |
| Fri 07 | 0 | 0.0 | 104 ms | 0 |
| Fri 08 | 0 | 0.0 | 73 ms | 0 |
| Fri 10 | 0 | 0.0 | 95 ms | 0 |
| Fri 11 | 0 | 0.0 | 43 ms | 0 |
| Fri 13 | 0 | 0.0 | 151 ms | 0 |
| Fri 15 | 0 | 0.0 | 117 ms | 0 |
| Fri 17 | 0 | 0.0 | 111 ms | 0 |
| Fri 19 | 0 | 0.0 | 141 ms | 0 |
| Fri 21 | 0 | 0.0 | 75 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 Uniqode 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 Uniqode yet. Outages of 10 minutes or more get their own page here.
Having trouble with Uniqode?
One report per service every 10 minutes from this network. No account.
Follow Uniqode
Get an email when Uniqode goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Uniqode alerts to Slack, Discord or a webhook — free.
About Uniqode
We track Uniqode (uniqode.com) as part of the Cloud & developer group. Create, manage and track your dynamic QR Codes with Uniqode’s advanced yet easy-to-use QR Code platform. Get started today.
Uniqode publishes an official status page at status.uniqode.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 105 ms average, 43–165 ms range across 14 successful checks.
Questions
Is Uniqode down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Uniqode last down?
We have not recorded a public Uniqode incident since monitoring began 8 days ago.
What is Uniqode's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Uniqode respond?
105 ms on average over the last 24 hours (43–165 ms).
Does Uniqode have an official status page?
Yes, at https://status.uniqode.com.
Uniqode 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 Uniqode here at once, the problem is on Uniqode'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 Uniqode. 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.