User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 40 min ago. Last stored result reached it in 1261 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 21 | 0 | 0.0 | 986 ms | 0 |
| Tue 23 | 0 | 0.0 | 1352 ms | 0 |
| Wed 01 | 0 | 0.0 | 1065 ms | 0 |
| Wed 04 | 0 | 0.0 | 1242 ms | 0 |
| Wed 06 | 0 | 0.0 | 795 ms | 0 |
| Wed 08 | 0 | 0.0 | 959 ms | 0 |
| Wed 10 | 0 | 0.0 | 1311 ms | 0 |
| Wed 13 | 0 | 0.0 | 894 ms | 0 |
| Wed 15 | 0 | 0.0 | 1127 ms | 0 |
| Wed 17 | 0 | 0.0 | 866 ms | 0 |
| Wed 19 | 0 | 0.0 | 758 ms | 0 |
| Wed 21 | 0 | 0.0 | 980 ms | 0 |
| Wed 23 | 0 | 0.0 | 898 ms | 0 |
| Thu 02 | 0 | 0.0 | 986 ms | 0 |
| Thu 04 | 0 | 0.0 | 1207 ms | 0 |
| Thu 06 | 0 | 0.0 | 1291 ms | 0 |
| Thu 08 | 0 | 0.0 | 1497 ms | 0 |
| Thu 10 | 0 | 0.0 | 801 ms | 0 |
| Thu 12 | 0 | 0.0 | 805 ms | 0 |
| Thu 14 | 0 | 0.0 | 1157 ms | 0 |
| Thu 16 | 0 | 0.0 | 749 ms | 0 |
| Thu 18 | 0 | 0.0 | 802 ms | 0 |
| Thu 20 | 0 | 0.0 | 1112 ms | 0 |
| Thu 22 | 0 | 0.0 | 857 ms | 0 |
| Fri 00 | 0 | 0.0 | 1384 ms | 0 |
| Fri 02 | 0 | 0.0 | 836 ms | 0 |
| Fri 04 | 0 | 0.0 | 1097 ms | 0 |
| Fri 07 | 0 | 0.0 | 1320 ms | 0 |
| Fri 09 | 0 | 0.0 | 918 ms | 0 |
| Fri 10 | 0 | 0.0 | 1156 ms | 0 |
| Fri 12 | 0 | 0.0 | 819 ms | 0 |
| Fri 14 | 0 | 0.0 | 894 ms | 0 |
| Fri 16 | 0 | 0.0 | 972 ms | 0 |
| Fri 18 | 0 | 0.0 | 1284 ms | 0 |
| Fri 20 | 0 | 0.0 | 826 ms | 0 |
| Fri 22 | 0 | 0.0 | 1047 ms | 0 |
| Sat 00 | 0 | 0.0 | 1178 ms | 0 |
| Sat 02 | 0 | 0.0 | 748 ms | 0 |
| Sat 03 | 0 | 0.0 | 1127 ms | 0 |
| Sat 05 | 0 | 0.0 | 1432 ms | 0 |
| Sat 06 | 0 | 0.0 | 639 ms | 0 |
| Sat 07 | 0 | 0.0 | 1128 ms | 0 |
| Sat 09 | 0 | 0.0 | 1007 ms | 0 |
| Sat 11 | 0 | 0.0 | 1350 ms | 0 |
| Sat 14 | 0 | 0.0 | 1436 ms | 0 |
| Sat 16 | 0 | 0.0 | 985 ms | 0 |
| Sat 18 | 0 | 0.0 | 1190 ms | 0 |
| Sat 21 | 0 | 0.0 | 1261 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Sesame HR 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 Sesame HR goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Sesame HR is listed in our Productivity category and checked at sesametime.com. Descubre Sesame, la aplicación de control horario más completa del mercado. Gestiona horarios, vacaciones, turnos, trabajo remoto... ¡Pruébalo gratis!
Sesame HR publishes an official status page at status.sesametime.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 1118 ms average, 639–1436 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Sesame HR incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
1118 ms on average over the last 24 hours (639–1436 ms).
Yes, at https://status.sesametime.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Sesame HR here at once, the problem is on Sesame HR'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 Sesame HR. 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.