<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Unix Timestamp — Guides</title>
    <link>https://unixtimestamp.live/guides</link>
    <description>Guides to Unix time, time zones and date formats.</description>
    <language>en</language>
    <atom:link href="https://unixtimestamp.live/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Monotonic Clocks — Why You Should Not Subtract Timestamps</title>
      <link>https://unixtimestamp.live/guides/monotonic-clocks</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/monotonic-clocks</guid>
      <description>Subtracting two Unix timestamps to measure a duration gives the wrong answer whenever the clock is adjusted — including negative durations.</description>
      <pubDate>Mon, 09 Feb 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Notable Unix Timestamps and Epoch Milestones</title>
      <link>https://unixtimestamp.live/guides/epoch-milestones</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/epoch-milestones</guid>
      <description>1234567890, 2147483647, 1000000000 — the timestamps worth recognising, and the boundaries worth having in your test fixtures.</description>
      <pubDate>Sat, 07 Feb 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Cron Jobs and Time Zones</title>
      <link>https://unixtimestamp.live/guides/cron-jobs-and-time-zones</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/cron-jobs-and-time-zones</guid>
      <description>A job at 02:30 local never runs in spring and runs twice in autumn. The fix is to schedule in UTC and make the job idempotent.</description>
      <pubDate>Thu, 05 Feb 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>JWT Expiry, Timestamps and Clock Skew</title>
      <link>https://unixtimestamp.live/guides/jwt-expiry-and-clock-skew</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/jwt-expiry-and-clock-skew</guid>
      <description>Pass Date.now() into exp and you have issued a token expiring in the year 56,000. Here is the whole class of timestamp bug around JWTs.</description>
      <pubDate>Tue, 03 Feb 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Negative Unix Timestamps and Dates Before 1970</title>
      <link>https://unixtimestamp.live/guides/negative-unix-timestamps</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/negative-unix-timestamps</guid>
      <description>-86400 is 31 December 1969. Most languages handle it correctly; a surprising number of databases, APIs and validators do not.</description>
      <pubDate>Sun, 01 Feb 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>RFC 3339 vs ISO 8601</title>
      <link>https://unixtimestamp.live/guides/rfc-3339-vs-iso-8601</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/rfc-3339-vs-iso-8601</guid>
      <description>Almost the same, but not quite a subset in either direction. If you are writing an API, target the overlap.</description>
      <pubDate>Wed, 28 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Storing Timestamps in Databases</title>
      <link>https://unixtimestamp.live/guides/storing-timestamps-in-databases</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/storing-timestamps-in-databases</guid>
      <description>The column type you pick determines whether your dates survive a server move, a time zone change and the year 2038. Most defaults are wrong.</description>
      <pubDate>Sun, 25 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Time Zones vs UTC Offsets</title>
      <link>https://unixtimestamp.live/guides/time-zones-vs-utc-offsets</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/time-zones-vs-utc-offsets</guid>
      <description>An offset like +05:30 tells you what a clock read. Asia/Kolkata tells you which clock, and what it will read next year. That difference matters for future dates.</description>
      <pubDate>Thu, 22 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Daylight Saving Time Bugs and How to Avoid Them</title>
      <link>https://unixtimestamp.live/guides/daylight-saving-bugs</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/daylight-saving-bugs</guid>
      <description>The missing hour and the repeated hour cause skipped jobs, double charges and impossible timestamps. All of it is preventable by scheduling in UTC.</description>
      <pubDate>Tue, 20 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>UTC vs GMT — What Is the Difference?</title>
      <link>https://unixtimestamp.live/guides/utc-vs-gmt</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/utc-vs-gmt</guid>
      <description>They agree to within a second, which is why the difference is usually ignored — and exactly why it surprises people when it finally matters.</description>
      <pubDate>Sun, 18 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Leap Seconds and Why Unix Time Ignores Them</title>
      <link>https://unixtimestamp.live/guides/leap-seconds</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/leap-seconds</guid>
      <description>Twenty-seven seconds have been inserted into UTC since 1972, and Unix time represents none of them. Usually harmless, occasionally catastrophic.</description>
      <pubDate>Thu, 15 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>ISO 8601 Explained</title>
      <link>https://unixtimestamp.live/guides/iso-8601-explained</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/iso-8601-explained</guid>
      <description>The interchange format that removes ambiguity from dates — and the handful of its features you should never use.</description>
      <pubDate>Mon, 12 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Seconds vs Milliseconds — The Most Common Timestamp Bug</title>
      <link>https://unixtimestamp.live/guides/seconds-vs-milliseconds</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/seconds-vs-milliseconds</guid>
      <description>Ten digits or thirteen. Get it backwards and your date lands either in January 1970 or somewhere around the year 55,000. Here is how to make the bug impossible.</description>
      <pubDate>Sat, 10 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Year 2038 Problem</title>
      <link>https://unixtimestamp.live/guides/year-2038-problem</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/year-2038-problem</guid>
      <description>At 03:14:07 UTC on 19 January 2038, a signed 32-bit time_t runs out of room and wraps to 1901. Most systems are fine. The ones that are not are hard to find.</description>
      <pubDate>Thu, 08 Jan 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What Is Unix Time?</title>
      <link>https://unixtimestamp.live/guides/what-is-unix-time</link>
      <guid isPermaLink="true">https://unixtimestamp.live/guides/what-is-unix-time</guid>
      <description>A single integer that identifies any instant, anywhere on Earth, with no time zone attached. Here is where it came from and what it deliberately leaves out.</description>
      <pubDate>Mon, 05 Jan 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
