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 16 min ago. Last stored result reached it in 237 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 220 ms | 0 |
| Mon 15 | 0 | 0.0 | 238 ms | 0 |
| Mon 17 | 0 | 0.0 | 305 ms | 0 |
| Mon 19 | 0 | 0.0 | 186 ms | 0 |
| Mon 21 | 0 | 0.0 | 361 ms | 0 |
| Mon 23 | 0 | 0.0 | 215 ms | 0 |
| Tue 01 | 0 | 0.0 | 327 ms | 0 |
| Tue 03 | 0 | 0.0 | 269 ms | 0 |
| Tue 05 | 0 | 0.0 | 185 ms | 0 |
| Tue 08 | 0 | 0.0 | 400 ms | 0 |
| Tue 10 | 0 | 0.0 | 274 ms | 0 |
| Tue 12 | 0 | 0.0 | 311 ms | 0 |
| Tue 14 | 0 | 0.0 | 215 ms | 0 |
| Tue 16 | 0 | 0.0 | 307 ms | 0 |
| Tue 18 | 0 | 0.0 | 416 ms | 0 |
| Tue 21 | 0 | 0.0 | 430 ms | 0 |
| Tue 23 | 0 | 0.0 | 273 ms | 0 |
| Wed 01 | 0 | 0.0 | 361 ms | 0 |
| Wed 03 | 0 | 0.0 | 255 ms | 0 |
| Wed 06 | 0 | 0.0 | 190 ms | 0 |
| Wed 08 | 0 | 0.0 | 289 ms | 0 |
| Wed 10 | 0 | 0.0 | 226 ms | 0 |
| Wed 12 | 0 | 0.0 | 624 ms | 0 |
| Wed 14 | 0 | 0.0 | 280 ms | 0 |
| Wed 16 | 0 | 0.0 | 213 ms | 0 |
| Wed 19 | 0 | 0.0 | 344 ms | 0 |
| Wed 21 | 0 | 0.0 | 305 ms | 0 |
| Wed 23 | 0 | 0.0 | 410 ms | 0 |
| Thu 01 | 0 | 0.0 | 171 ms | 0 |
| Thu 03 | 0 | 0.0 | 225 ms | 0 |
| Thu 05 | 0 | 0.0 | 358 ms | 0 |
| Thu 07 | 0 | 0.0 | 159 ms | 0 |
| Thu 09 | 0 | 0.0 | 220 ms | 0 |
| Thu 12 | 0 | 0.0 | 234 ms | 0 |
| Thu 14 | 0 | 0.0 | 311 ms | 0 |
| Thu 16 | 0 | 0.0 | 179 ms | 0 |
| Thu 18 | 0 | 0.0 | 325 ms | 0 |
| Thu 20 | 0 | 0.0 | 414 ms | 0 |
| Thu 22 | 0 | 0.0 | 455 ms | 0 |
| Fri 00 | 0 | 0.0 | 440 ms | 0 |
| Fri 02 | 0 | 0.0 | 375 ms | 0 |
| Fri 04 | 0 | 0.0 | 279 ms | 0 |
| Fri 06 | 0 | 0.0 | 190 ms | 0 |
| Fri 08 | 0 | 0.0 | 141 ms | 0 |
| Fri 10 | 0 | 0.0 | 169 ms | 0 |
| Fri 12 | 0 | 0.0 | 172 ms | 0 |
| Fri 14 | 0 | 0.0 | 255 ms | 0 |
| Fri 16 | 0 | 0.0 | 237 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 Kundo 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 Kundo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kundo alerts to Slack, Discord or a webhook — free.
We track Kundo (kundo.se) as part of the Cloud & developer group. En helhetslösning för kundservice som förenar ärendehantering och self-service i samma lösning.
Kundo publishes an official status page at status.kundo.se; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 283 ms average, 141–455 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 Kundo incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
283 ms on average over the last 24 hours (141–455 ms).
Yes, at https://status.kundo.se.
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 Kundo here at once, the problem is on Kundo'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 Kundo. 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.