User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Kaze 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 → kaze.so—
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 47 min ago. Last stored result reached it in 1067 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 1232 ms | 0 |
| Mon 20 | 0 | 0.0 | 1148 ms | 0 |
| Mon 22 | 0 | 0.0 | 1551 ms | 0 |
| Tue 00 | 0 | 0.0 | 1170 ms | 0 |
| Tue 02 | 0 | 0.0 | 1436 ms | 0 |
| Tue 05 | 0 | 0.0 | 1194 ms | 0 |
| Tue 07 | 0 | 0.0 | 1426 ms | 0 |
| Tue 09 | 0 | 0.0 | 795 ms | 0 |
| Tue 11 | 0 | 0.0 | 1148 ms | 0 |
| Tue 13 | 0 | 0.0 | 1394 ms | 0 |
| Tue 15 | 0 | 0.0 | 1468 ms | 0 |
| Tue 18 | 0 | 0.0 | 1486 ms | 0 |
| Tue 20 | 0 | 0.0 | 1504 ms | 0 |
| Tue 22 | 0 | 0.0 | — | 0 |
| Wed 00 | 0 | 0.0 | 1398 ms | 0 |
| Wed 03 | 0 | 0.0 | 1049 ms | 0 |
| Wed 05 | 0 | 0.0 | 1212 ms | 0 |
| Wed 07 | 0 | 0.0 | 3018 ms | 0 |
| Wed 09 | 0 | 0.0 | 1377 ms | 0 |
| Wed 12 | 0 | 0.0 | 1281 ms | 0 |
| Wed 14 | 0 | 0.0 | 1107 ms | 0 |
| Wed 16 | 0 | 0.0 | 992 ms | 0 |
| Wed 18 | 0 | 0.0 | 937 ms | 0 |
| Wed 20 | 0 | 0.0 | 957 ms | 0 |
| Wed 22 | 0 | 0.0 | 1241 ms | 0 |
| Thu 00 | 0 | 0.0 | 1362 ms | 0 |
| Thu 03 | 0 | 0.0 | 1203 ms | 0 |
| Thu 05 | 0 | 0.0 | 852 ms | 0 |
| Thu 07 | 0 | 0.0 | 1224 ms | 0 |
| Thu 09 | 0 | 0.0 | 1620 ms | 0 |
| Thu 11 | 0 | 0.0 | 1128 ms | 0 |
| Thu 13 | 0 | 0.0 | 1576 ms | 0 |
| Thu 15 | 0 | 0.0 | 1086 ms | 0 |
| Thu 17 | 0 | 0.0 | 1459 ms | 0 |
| Thu 19 | 0 | 0.0 | 1083 ms | 0 |
| Thu 21 | 0 | 0.0 | 1565 ms | 0 |
| Thu 22 | 0 | 0.0 | 1532 ms | 0 |
| Fri 00 | 0 | 0.0 | 1087 ms | 0 |
| Fri 02 | 0 | 0.0 | 1353 ms | 0 |
| Fri 04 | 0 | 0.0 | 1310 ms | 0 |
| Fri 06 | 0 | 0.0 | 1345 ms | 0 |
| Fri 08 | 0 | 0.0 | 1402 ms | 0 |
| Fri 10 | 0 | 0.0 | 1590 ms | 0 |
| Fri 12 | 0 | 0.0 | 1262 ms | 0 |
| Fri 14 | 0 | 0.0 | 1054 ms | 0 |
| Fri 16 | 0 | 0.0 | 1083 ms | 0 |
| Fri 17 | 0 | 0.0 | 1027 ms | 0 |
| Fri 19 | 0 | 0.0 | 1067 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Kaze 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 Kaze yet. Outages of 10 minutes or more get their own page here.
Having trouble with Kaze?
One report per service every 10 minutes from this network. No account.
Follow Kaze
Get an email when Kaze goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kaze alerts to Slack, Discord or a webhook — free.
About Kaze
Kaze, at kaze.so, is one of the Cloud & developer services we monitor. Kaze connecte donneurs d'ordre, prestataires, intervenants et bénéficiaires : ordres de mission, dispatch, suivi en temps réel à la Uber, PV signés avec photos, facturation et API. Né dans l'assistance automobile, ouvert à tous les métiers d'intervention.
Kaze publishes an official status page at status.kaze.so; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 1265 ms average, 924–1590 ms range across 14 successful checks.
Questions
Is Kaze down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Kaze last down?
We have not recorded a public Kaze incident since monitoring began 6 days ago.
What is Kaze's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Kaze respond?
1265 ms on average over the last 24 hours (924–1590 ms).
Does Kaze have an official status page?
Yes, at https://status.kaze.so.
Kaze 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 Kaze here at once, the problem is on Kaze'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 Kaze. 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.