All services / Cloud & developer

qrago.de · 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.

No ads · We don't sell your data

What's broken? (optional)
Is it just me?

Vendor-reported issue

What to try while QRaGo is having problems

Estimated fix: Not enough QRaGo history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–7.5 h; 87 outages).

  • Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.

Official QRaGo status page

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 · ORDReachable395 ms · 3 min ago
US West · SJCReachable545 ms · 3 min ago
Europe · AMSReachable172 ms · 3 min ago
Asia-Pacific · KIXReachable632 ms · 3 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.

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.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last checked 54 min ago. Last stored result reached it in 437 ms.

Official status

Minor incident

Some components degraded (no active incident posted) Official status page

Reports and checks

Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
Nov 600.0477 ms0
Nov 700.0351 ms0
Nov 700.0388 ms0
Nov 700.0387 ms0
Nov 800.0421 ms0
Nov 800.0451 ms0
Nov 800.0468 ms0
Nov 800.0368 ms0
Nov 900.0404 ms0
Nov 900.0431 ms0
Nov 900.0556 ms0
Nov 900.0492 ms0
Nov 1000.0382 ms0
Nov 1000.0411 ms0
Nov 1000.0457 ms0
Nov 1000.0561 ms0
Nov 1100.0585 ms0
Nov 1100.0457 ms0
Nov 1100.0491 ms0
Nov 1100.0431 ms0
Nov 1200.0413 ms0
Nov 1200.0401 ms0
Nov 1200.0410 ms0
Nov 1200.0434 ms0
Nov 1300.0430 ms0
Nov 1300.0453 ms0
Nov 1300.0425 ms0
Nov 1300.0432 ms0
Nov 1400.0411 ms0
Nov 1400.0435 ms0

Reliability

Score 99/100 · grade A

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.

QRaGo status badge 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

QRaGo status and 30-day uptime badge

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.

Past outages

StartedPeakDurationStatusDetails
2026-11-06 23:49 UTCVendor-reported issue3 days 12 hResolvedDetails →

All QRaGo outages · Every recent outage

Having trouble with QRaGo?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

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: 408 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?

408 ms on average over the last 24 hours (19–641 ms). Latest regional checks: US East 395 ms, US West 545 ms, Europe 172 ms, Asia-Pacific 632 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.