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 34 min ago. Last stored result reached it in 267 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 153 ms | 0 |
| Tue 06 | 0 | 0.0 | 145 ms | 0 |
| Tue 08 | 0 | 0.0 | 545 ms | 0 |
| Tue 10 | 0 | 0.0 | 596 ms | 0 |
| Tue 12 | 0 | 0.0 | 178 ms | 0 |
| Tue 14 | 0 | 0.0 | 141 ms | 0 |
| Tue 16 | 0 | 0.0 | 153 ms | 0 |
| Tue 19 | 0 | 0.0 | 304 ms | 0 |
| Tue 21 | 0 | 0.0 | 336 ms | 0 |
| Tue 23 | 0 | 0.0 | 121 ms | 0 |
| Wed 01 | 0 | 0.0 | 92 ms | 0 |
| Wed 04 | 0 | 0.0 | 230 ms | 0 |
| Wed 06 | 0 | 0.0 | 398 ms | 0 |
| Wed 08 | 0 | 0.0 | 222 ms | 0 |
| Wed 10 | 0 | 0.0 | 311 ms | 0 |
| Wed 13 | 0 | 0.0 | 183 ms | 0 |
| Wed 15 | 0 | 0.0 | 540 ms | 0 |
| Wed 17 | 0 | 0.0 | 402 ms | 0 |
| Wed 19 | 0 | 0.0 | 197 ms | 0 |
| Wed 21 | 0 | 0.0 | 237 ms | 0 |
| Wed 23 | 0 | 0.0 | 350 ms | 0 |
| Thu 02 | 0 | 0.0 | 529 ms | 0 |
| Thu 04 | 0 | 0.0 | 290 ms | 0 |
| Thu 06 | 0 | 0.0 | 211 ms | 0 |
| Thu 08 | 0 | 0.0 | 486 ms | 0 |
| Thu 10 | 0 | 0.0 | 169 ms | 0 |
| Thu 12 | 0 | 0.0 | 289 ms | 0 |
| Thu 14 | 0 | 0.0 | 468 ms | 0 |
| Thu 16 | 0 | 0.0 | 445 ms | 0 |
| Thu 18 | 0 | 0.0 | 569 ms | 0 |
| Thu 20 | 0 | 0.0 | 275 ms | 0 |
| Thu 22 | 0 | 0.0 | 146 ms | 0 |
| Fri 00 | 0 | 0.0 | 128 ms | 0 |
| Fri 02 | 0 | 0.0 | 128 ms | 0 |
| Fri 04 | 0 | 0.0 | 133 ms | 0 |
| Fri 06 | 0 | 0.0 | 262 ms | 0 |
| Fri 07 | 0 | 0.0 | 117 ms | 0 |
| Fri 09 | 0 | 0.0 | 416 ms | 0 |
| Fri 10 | 0 | 0.0 | 123 ms | 0 |
| Fri 12 | 0 | 0.0 | 151 ms | 0 |
| Fri 14 | 0 | 0.0 | 156 ms | 0 |
| Fri 16 | 0 | 0.0 | 318 ms | 0 |
| Fri 17 | 0 | 0.0 | 126 ms | 0 |
| Fri 19 | 0 | 0.0 | 173 ms | 0 |
| Fri 20 | 0 | 0.0 | 247 ms | 0 |
| Fri 22 | 0 | 0.0 | 189 ms | 0 |
| Sat 00 | 0 | 0.0 | 85 ms | 0 |
| Sat 01 | 0 | 0.0 | 267 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 Qipu 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 Qipu goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Qipu alerts to Slack, Discord or a webhook — free.
Qipu, at qipu.org, is one of the Cloud & developer services we monitor. Budget, dette, marchés publics et subventions des communes, départements et régions, d’après les comptes publiés par l’État. Chaque montant est sourcé.
Qipu publishes an official status page at status.qipu.org; 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: 186 ms average, 73–416 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Qipu incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
186 ms on average over the last 24 hours (73–416 ms).
Yes, at https://status.qipu.org.
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 Qipu here at once, the problem is on Qipu'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 Qipu. 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.