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 2 hr ago. Last stored result reached it in 110 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 59 ms | 0 |
| Mon 21 | 0 | 0.0 | 171 ms | 0 |
| Mon 23 | 0 | 0.0 | 103 ms | 0 |
| Tue 01 | 0 | 0.0 | 147 ms | 0 |
| Tue 03 | 0 | 0.0 | 75 ms | 0 |
| Tue 05 | 0 | 0.0 | 72 ms | 0 |
| Tue 07 | 0 | 0.0 | 68 ms | 0 |
| Tue 09 | 0 | 0.0 | 105 ms | 0 |
| Tue 12 | 0 | 0.0 | 33 ms | 0 |
| Tue 14 | 0 | 0.0 | 50 ms | 0 |
| Tue 16 | 0 | 0.0 | 79 ms | 0 |
| Tue 18 | 0 | 0.0 | 123 ms | 0 |
| Tue 21 | 0 | 0.0 | 128 ms | 0 |
| Tue 23 | 0 | 0.0 | 94 ms | 0 |
| Wed 01 | 0 | 0.0 | 98 ms | 0 |
| Wed 03 | 0 | 0.0 | 51 ms | 0 |
| Wed 05 | 0 | 0.0 | 54 ms | 0 |
| Wed 07 | 0 | 0.0 | 125 ms | 0 |
| Wed 10 | 0 | 0.0 | 52 ms | 0 |
| Wed 12 | 0 | 0.0 | 86 ms | 0 |
| Wed 14 | 0 | 0.0 | 85 ms | 0 |
| Wed 16 | 0 | 0.0 | 177 ms | 0 |
| Wed 18 | 0 | 0.0 | 104 ms | 0 |
| Wed 20 | 0 | 0.0 | 104 ms | 0 |
| Wed 23 | 0 | 0.0 | 84 ms | 0 |
| Thu 01 | 0 | 0.0 | 100 ms | 0 |
| Thu 03 | 0 | 0.0 | 128 ms | 0 |
| Thu 05 | 0 | 0.0 | 35 ms | 0 |
| Thu 07 | 0 | 0.0 | 144 ms | 0 |
| Thu 09 | 0 | 0.0 | 86 ms | 0 |
| Thu 11 | 0 | 0.0 | 33 ms | 0 |
| Thu 13 | 0 | 0.0 | 78 ms | 0 |
| Thu 15 | 0 | 0.0 | 84 ms | 0 |
| Thu 17 | 0 | 0.0 | 99 ms | 0 |
| Thu 19 | 0 | 0.0 | 99 ms | 0 |
| Thu 20 | 0 | 0.0 | 71 ms | 0 |
| Thu 21 | 0 | 0.0 | 78 ms | 0 |
| Thu 23 | 0 | 0.0 | 71 ms | 0 |
| Fri 01 | 0 | 0.0 | 77 ms | 0 |
| Fri 04 | 0 | 0.0 | 96 ms | 0 |
| Fri 06 | 0 | 0.0 | 45 ms | 0 |
| Fri 08 | 0 | 0.0 | 116 ms | 0 |
| Fri 10 | 0 | 0.0 | 55 ms | 0 |
| Fri 12 | 0 | 0.0 | 39 ms | 0 |
| Fri 14 | 0 | 0.0 | 51 ms | 0 |
| Fri 16 | 0 | 0.0 | 42 ms | 0 |
| Fri 18 | 0 | 0.0 | 44 ms | 0 |
| Fri 20 | 0 | 0.0 | 93 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 6 days of data so far, so the 90-day numbers fill in over time.
GRS/CarltonOne maintenance Nov 13 2026
Kudos provider GRS will be undergoing maintenance at the schedule time. The main Kudos platforms will remain active, but there will be an interruption with GRS redemptions. This is the communication provided: Temporary service interruption This maintenance focuses on the stability, security and optimization of our servers, networks and operating system infrastructure. It is separate from our…
GRS/CarltonOne maintenance Nov 16 2026
Kudos provider GRS will be undergoing maintenance at the schedule time. The main Kudos platforms will remain active, but there will be an interruption with GRS redemptions. This is the communication provided: As part of CarltonOne's ongoing investment in platform reliability, scalability, and security, we will be completing the final migration of our systems infrastructure to Amazon Web Services…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Kudos 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 Kudos goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kudos alerts to Slack, Discord or a webhook — free.
We track Kudos (kudos.com) as part of the Cloud & developer group. Kudos® is the recognition and rewards platform designed to fit your unique workplace culture.
Kudos publishes an official status page at status.kudos.com; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 68 ms average, 39–116 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Kudos incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
68 ms on average over the last 24 hours (39–116 ms).
Yes, at https://status.kudos.com.
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 Kudos here at once, the problem is on Kudos'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 Kudos. 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.