User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 52 min ago. Last stored result reached it in 439 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 592 ms | 0 |
| Tue 01 | 0 | 0.0 | 571 ms | 0 |
| Tue 03 | 0 | 0.0 | 223 ms | 0 |
| Tue 06 | 0 | 0.0 | 597 ms | 0 |
| Tue 08 | 0 | 0.0 | 408 ms | 0 |
| Tue 10 | 0 | 0.0 | 577 ms | 0 |
| Tue 12 | 0 | 0.0 | 562 ms | 0 |
| Tue 14 | 0 | 0.0 | 565 ms | 0 |
| Tue 16 | 0 | 0.0 | 617 ms | 0 |
| Tue 19 | 0 | 0.0 | 425 ms | 0 |
| Tue 21 | 0 | 0.0 | 478 ms | 0 |
| Tue 23 | 0 | 0.0 | 583 ms | 0 |
| Wed 01 | 0 | 0.0 | 630 ms | 0 |
| Wed 04 | 0 | 0.0 | 583 ms | 0 |
| Wed 06 | 0 | 0.0 | 566 ms | 0 |
| Wed 08 | 0 | 0.0 | 615 ms | 0 |
| Wed 10 | 0 | 0.0 | 503 ms | 0 |
| Wed 13 | 0 | 0.0 | 537 ms | 0 |
| Wed 15 | 0 | 0.0 | 547 ms | 0 |
| Wed 17 | 0 | 0.0 | 559 ms | 0 |
| Wed 19 | 0 | 0.0 | 251 ms | 0 |
| Wed 21 | 0 | 0.0 | 564 ms | 0 |
| Wed 23 | 0 | 0.0 | 503 ms | 0 |
| Thu 02 | 0 | 0.0 | 594 ms | 0 |
| Thu 04 | 0 | 0.0 | 485 ms | 0 |
| Thu 06 | 0 | 0.0 | 437 ms | 0 |
| Thu 08 | 0 | 0.0 | 483 ms | 0 |
| Thu 10 | 0 | 0.0 | 555 ms | 0 |
| Thu 12 | 0 | 0.0 | 466 ms | 0 |
| Thu 14 | 0 | 0.0 | 534 ms | 0 |
| Thu 16 | 0 | 0.0 | 579 ms | 0 |
| Thu 18 | 0 | 0.0 | 3423 ms | 0 |
| Thu 20 | 0 | 0.0 | 571 ms | 0 |
| Thu 22 | 0 | 0.0 | 538 ms | 0 |
| Fri 00 | 0 | 0.0 | 588 ms | 0 |
| Fri 02 | 0 | 0.0 | 644 ms | 0 |
| Fri 04 | 0 | 0.0 | 760 ms | 0 |
| Fri 06 | 0 | 0.0 | 647 ms | 0 |
| Fri 08 | 0 | 0.0 | 551 ms | 0 |
| Fri 10 | 0 | 0.0 | 579 ms | 0 |
| Fri 11 | 0 | 0.0 | 580 ms | 0 |
| Fri 12 | 0 | 0.0 | 567 ms | 0 |
| Fri 14 | 0 | 0.0 | 549 ms | 0 |
| Fri 16 | 0 | 0.0 | 557 ms | 0 |
| Fri 18 | 0 | 0.0 | 583 ms | 0 |
| Fri 19 | 0 | 0.0 | 236 ms | 0 |
| Fri 21 | 0 | 0.0 | 573 ms | 0 |
| Fri 23 | 0 | 0.0 | 439 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for QR 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 QR goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send QR alerts to Slack, Discord or a webhook — free.
QR is listed in our Cloud & developer category and checked at qr.io. Generate fully customized QR Codes, with color & shape, logo and keep track of how many people scan your QR Codes, from where and on what date.
QR publishes an official status page at status.qr.io; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 561 ms average, 236–760 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public QR incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
561 ms on average over the last 24 hours (236–760 ms).
Yes, at https://status.qr.io.
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 QR here at once, the problem is on QR'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 QR. 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.