User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is QRaGo down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with QRaGo.
What to try while QRaGo is having problems
Estimated fix: Not enough QRaGo history yet; similar Cloud & developer outages lasted 2 h (median, typically 50 min–7.5 h; 86 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → qrago.de—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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.
Checks by region
Reachable from all 4 regions we check from.
US East · ORDReachable444 ms · 32 min ago
US West · SJCReachable658 ms · 32 min ago
Europe · AMSReachable134 ms · 32 min ago
Asia-Pacific · KIXReachable584 ms · 32 min ago
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 33 min ago. Last stored result reached it in 433 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 570 ms | 0 |
| Tue 10 | 0 | 0.0 | 398 ms | 0 |
| Tue 12 | 0 | 0.0 | 509 ms | 0 |
| Tue 14 | 0 | 0.0 | 404 ms | 0 |
| Tue 16 | 0 | 0.0 | 389 ms | 0 |
| Tue 19 | 0 | 0.0 | 561 ms | 0 |
| Tue 21 | 0 | 0.0 | 447 ms | 0 |
| Tue 23 | 0 | 0.0 | 574 ms | 0 |
| Wed 01 | 0 | 0.0 | 559 ms | 0 |
| Wed 04 | 0 | 0.0 | 610 ms | 0 |
| Wed 06 | 0 | 0.0 | 395 ms | 0 |
| Wed 08 | 0 | 0.0 | 567 ms | 0 |
| Wed 10 | 0 | 0.0 | 457 ms | 0 |
| Wed 13 | 0 | 0.0 | 560 ms | 0 |
| Wed 15 | 0 | 0.0 | 491 ms | 0 |
| Wed 17 | 0 | 0.0 | 390 ms | 0 |
| Wed 19 | 0 | 0.0 | 631 ms | 0 |
| Wed 21 | 0 | 0.0 | 420 ms | 0 |
| Wed 23 | 0 | 0.0 | 428 ms | 0 |
| Thu 01 | 0 | 0.0 | 413 ms | 0 |
| Thu 03 | 0 | 0.0 | 400 ms | 0 |
| Thu 05 | 0 | 0.0 | 542 ms | 0 |
| Thu 07 | 0 | 0.0 | 400 ms | 0 |
| Thu 10 | 0 | 0.0 | 402 ms | 0 |
| Thu 12 | 0 | 0.0 | 415 ms | 0 |
| Thu 14 | 0 | 0.0 | 405 ms | 0 |
| Thu 16 | 0 | 0.0 | 416 ms | 0 |
| Thu 18 | 0 | 0.0 | 431 ms | 0 |
| Thu 20 | 0 | 0.0 | 258 ms | 0 |
| Thu 22 | 0 | 0.0 | 557 ms | 0 |
| Fri 00 | 0 | 0.0 | 405 ms | 0 |
| Fri 02 | 0 | 0.0 | 423 ms | 0 |
| Fri 04 | 0 | 0.0 | 515 ms | 0 |
| Fri 06 | 0 | 0.0 | 473 ms | 0 |
| Fri 08 | 0 | 0.0 | 453 ms | 0 |
| Fri 11 | 0 | 0.0 | 446 ms | 0 |
| Fri 13 | 0 | 0.0 | 398 ms | 0 |
| Fri 15 | 0 | 0.0 | 438 ms | 0 |
| Fri 17 | 0 | 0.0 | 425 ms | 0 |
| Fri 18 | 0 | 0.0 | 391 ms | 0 |
| Fri 19 | 0 | 0.0 | 641 ms | 0 |
| Fri 21 | 0 | 0.0 | 461 ms | 0 |
| Fri 23 | 0 | 0.0 | 403 ms | 0 |
| Sat 01 | 0 | 0.0 | 491 ms | 0 |
| Sat 03 | 0 | 0.0 | 227 ms | 0 |
| Sat 05 | 0 | 0.0 | 386 ms | 0 |
| Sat 06 | 0 | 0.0 | 397 ms | 0 |
| Sat 08 | 0 | 0.0 | 454 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 QRaGo 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
Having trouble with QRaGo?
One report per service every 10 minutes from this network. No account.
Follow QRaGo
Get an email when QRaGo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send QRaGo alerts to Slack, Discord or a webhook — free.
About QRaGo
QRaGo, at qrago.de, is one of the Cloud & developer services we monitor. QRAGO: Die digitale Lösung in der Pflegelogistik
QRaGo publishes an official status page at status.qrago.de; 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. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 409 ms average, 19–641 ms range across 17 successful checks.
Questions
Is QRaGo down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was QRaGo last down?
The most recent public incident we recorded started 2026-11-06 and lasted 3 days 12 h. 1 incident since monitoring began 8 days ago.
What is QRaGo's uptime?
From our own checks: 100% over 8 days of checks.
How fast does QRaGo respond?
409 ms on average over the last 24 hours (19–641 ms). Latest regional checks: US East 444 ms, US West 658 ms, Europe 134 ms, Asia-Pacific 584 ms.
Does QRaGo have an official status page?
Yes, at https://status.qrago.de.
QRaGo 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 QRaGo here at once, the problem is on QRaGo'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 QRaGo. 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.