Time left
399duntil the stamp expiresSafe Until // Uptime Kuma, as deployed
● 400-day horizon proved
Tested under a faked clock (libfaketime)
Safe until
2027-11-29
Next clock event
America/New_York: clocks go back 60 minYour tests pass today. That's the problem. CI only ever tests now. This pipeline runs the app at the dates it will meet: every daylight-saving change in the next 400 days, with the server itself in UTC, New York and Sydney. It stamps each release with the first date it would give a wrong answer.
Instants probed
19,9923 server time zonesWrong answers
0across every probeHazards tracked
17next 2026-11-01no wrong answer in 19992 probes up to the end of the tested horizon.
The clock is the villain
The next 400 days
Every daylight-saving change in the tested horizon, and what the build did there.
2027
passedwrong answernot probed
Flight recorder
Hazard calendar
Each instant the pipeline jumped the clock to, in UTC, with the local time it means.
- DST foldAmerica/New_York: clocks go back 60 min2026-11-01 01:00:00 PASS · 1,176
- DST foldAmerica/Chicago: clocks go back 60 min2026-11-01 01:00:00 PASS · 1,176
- DST foldAmerica/Los_Angeles: clocks go back 60 min2026-11-01 01:00:00 PASS · 1,176
- DST gapAmerica/New_York: clocks go forward 60 min2027-03-14 03:00:00 PASS · 1,176
- DST gapAmerica/Chicago: clocks go forward 60 min2027-03-14 03:00:00 PASS · 1,176
- DST gapAmerica/Los_Angeles: clocks go forward 60 min2027-03-14 03:00:00 PASS · 1,176
- DST gapEurope/London: clocks go forward 60 min2027-03-28 02:00:00 PASS · 1,176
- DST gapEurope/Berlin: clocks go forward 60 min2027-03-28 03:00:00 PASS · 1,176
- DST foldPacific/Auckland: clocks go back 60 min2027-04-04 02:00:00 PASS · 1,176
- DST foldAustralia/Sydney: clocks go back 60 min2027-04-04 02:00:00 PASS · 1,176
- DST gapPacific/Auckland: clocks go forward 60 min2027-09-26 03:00:00 PASS · 1,176
- DST gapAustralia/Sydney: clocks go forward 60 min2027-10-03 03:00:00 PASS · 1,176
- DST foldEurope/London: clocks go back 60 min2027-10-31 01:00:00 PASS · 1,176
- DST foldEurope/Berlin: clocks go back 60 min2027-10-31 02:00:00 PASS · 1,176
- DST foldAmerica/New_York: clocks go back 60 min2027-11-07 01:00:00 PASS · 1,176
- DST foldAmerica/Chicago: clocks go back 60 min2027-11-07 01:00:00 PASS · 1,176
- DST foldAmerica/Los_Angeles: clocks go back 60 min2027-11-07 01:00:00 PASS · 1,176
How this is proved
Nobody in the loop
A scheduled pipeline does all of it.
1. ProbeUptime Kuma's own maintenance scheduler runs under libfaketime at each instant, and its answer is checked against the wall clock.
2. DefuseA wrong answer opens an issue due on the day it breaks. The Defuser, a GitLab Duo agent flow, writes the fix and a test pinned to that instant.
3. Prove and shipThe merge request pipeline re-runs every probe. Only a build with zero wrong answers is merged, stamped and deployed.