<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Murugan Vellaichamy</title>
    <description>The latest articles on DEV Community by Murugan Vellaichamy (@murugan_vellaichamy_2922a).</description>
    <link>https://dev.to/murugan_vellaichamy_2922a</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4115906%2Facbcca98-989b-45fb-9a65-0d85fbcc93ff.png</url>
      <title>DEV Community: Murugan Vellaichamy</title>
      <link>https://dev.to/murugan_vellaichamy_2922a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/murugan_vellaichamy_2922a"/>
    <language>en</language>
    <item>
      <title>Why Date.now() can return values that go backwards</title>
      <dc:creator>Murugan Vellaichamy</dc:creator>
      <pubDate>Tue, 17 Nov 2026 18:10:09 +0000</pubDate>
      <link>https://dev.to/murugan_vellaichamy_2922a/why-datenow-can-return-values-that-go-backwards-25eg</link>
      <guid>https://dev.to/murugan_vellaichamy_2922a/why-datenow-can-return-values-that-go-backwards-25eg</guid>
      <description>&lt;p&gt;Here's a JavaScript snippet that, on rare occasions in production, will fail:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;start&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nf"&gt;doSomeWork&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;end&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;elapsed&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;end&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;start&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`Took ${elapsed}ms`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="c1"&gt;// → Sometimes: "Took -1832ms"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;How can &lt;code&gt;end&lt;/code&gt; be smaller than &lt;code&gt;start&lt;/code&gt;? The work happened in real time, and the calls were sequential. What's going on?&lt;/p&gt;

&lt;h2&gt;
  
  
  Date.now() reads the wall clock
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;Date.now()&lt;/code&gt; returns the system wall clock, the same clock shown in your operating system's status bar. That clock can be changed underneath your program:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Clock step corrections.&lt;/strong&gt; Time-sync daemons normally slew the clock (speed it up or slow it down a little), which never goes backwards. But when the offset is large, they step it. For example, &lt;code&gt;ntpd&lt;/code&gt; steps the clock by default if the offset is above 128 ms (&lt;a href="https://docs.redhat.com/en/documentation/Red_Hat_Enterprise_Linux/6/html/deployment_guide/s1-understanding_ntp" rel="noopener noreferrer"&gt;Red Hat NTP docs&lt;/a&gt;). A step can go backwards.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Manual adjustment.&lt;/strong&gt; Someone changes the time in the system settings.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Virtual machine resume.&lt;/strong&gt; When a VM is suspended and resumed, its clock may snap forward or backward to match the host.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Daylight saving time does not cause this.&lt;/strong&gt; DST changes the displayed local time, but &lt;code&gt;Date.now()&lt;/code&gt; returns milliseconds since the Unix epoch, which has no time zone.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Any of the first three can make two consecutive &lt;code&gt;Date.now()&lt;/code&gt; calls return non-monotonic values. It's rare, but it happens often enough in production to be a real source of bugs.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix: performance.now() for durations
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;performance.now()&lt;/code&gt; reads a different clock. MDN describes the time origin it counts from as &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/Performance/now" rel="noopener noreferrer"&gt;"a monotonic clock: its current time never decreases and isn't subject to adjustments"&lt;/a&gt;. It returns a high-resolution value in milliseconds, with fractions.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;start&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;performance&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nf"&gt;doSomeWork&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;end&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;performance&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;elapsed&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;end&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;start&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="c1"&gt;// elapsed is never negative&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use &lt;code&gt;performance.now()&lt;/code&gt; for anything that measures a duration. Use &lt;code&gt;Date.now()&lt;/code&gt; when you need to record an absolute moment (a log entry, a database row, a scheduled event). Don't use &lt;code&gt;Date.now()&lt;/code&gt; for timing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The other failure mode: ID generation
&lt;/h2&gt;

&lt;p&gt;A common pattern:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Generate a "unique" ID using the current time&lt;/span&gt;
&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;makeId&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This works until two events happen in the same millisecond, and then you get a duplicate. People usually add a random suffix:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;makeId&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;random&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toString&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;36&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;slice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;6&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Better, but it still has the non-monotonic problem. If your IDs are supposed to sort by creation time (an assumption that often goes unstated), a backward clock jump can produce new IDs that sort before older ones. If you use IDs as cursors in a paginated API, that's a real bug.&lt;/p&gt;

&lt;p&gt;UUIDv7 puts a timestamp at the front, so IDs sort by time. RFC 9562 describes optional methods for keeping UUIDv7 values increasing: an implementation remembers the last timestamp it used and counts up from it if the wall clock moves backwards. Many libraries do this, but a plain generator doesn't have to. Node's built-in &lt;code&gt;crypto.randomUUID()&lt;/code&gt; only makes random v4 UUIDs, so use a library for v7 and check that it keeps IDs monotonic.&lt;/p&gt;

&lt;h2&gt;
  
  
  The sneakier failure: cache expiration
&lt;/h2&gt;

&lt;p&gt;This TTL cache looks correct but has the same bug:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;TtlCache&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;constructor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ttlMs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kc"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ttl&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;ttlMs&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kc"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;store&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nb"&gt;Map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="nf"&gt;set&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kc"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;store&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;set&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;expiresAt&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="kc"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ttl&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;entry&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;store&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;entry&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;now&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;entry&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;expiresAt&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="kc"&gt;this&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;store&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="k"&gt;delete&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
      &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;entry&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It works until the clock jumps. If the clock jumps forward an hour (a manual change or a VM resume, say), every entry expires at once, because &lt;code&gt;Date.now()&lt;/code&gt; is now an hour ahead of when they were set. Your cache hit rate drops to near zero and your downstream service gets hammered. A jump backwards does the opposite: entries live longer than their TTL.&lt;/p&gt;

&lt;p&gt;The fix is to base the deadline on a monotonic clock: store &lt;code&gt;performance.now() + ttl&lt;/code&gt;, and compare against &lt;code&gt;performance.now()&lt;/code&gt;. Or use a cache library that already does this.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you can do
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Use &lt;code&gt;performance.now()&lt;/code&gt; for durations. Never &lt;code&gt;Date.now() - Date.now()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Use UUIDv7 for time-ordered IDs, from a library that keeps them monotonic. Don't build them from &lt;code&gt;Date.now()&lt;/code&gt; yourself.&lt;/li&gt;
&lt;li&gt;Use a monotonic clock for cache TTLs, or a library that does.&lt;/li&gt;
&lt;li&gt;For absolute timestamps in logs, &lt;code&gt;Date.now()&lt;/code&gt; is fine. Just don't rely on it only moving forward.&lt;/li&gt;
&lt;li&gt;Test the bad case: mock &lt;code&gt;Date.now()&lt;/code&gt; and check that your code survives a clock that suddenly moves back an hour.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Precision of performance.now()
&lt;/h2&gt;

&lt;p&gt;Browsers deliberately limit the precision of &lt;code&gt;performance.now()&lt;/code&gt; to make timing attacks harder. The High Resolution Time spec sets a default resolution of 100 microseconds, or 5 microseconds when the page is cross-origin isolated, and says implementations may use a coarser value (&lt;a href="https://www.w3.org/TR/hr-time-3/" rel="noopener noreferrer"&gt;W3C spec, section 4&lt;/a&gt;). MDN gives the same two numbers.&lt;/p&gt;

&lt;p&gt;That is fine for almost every use. If you need sharper timing for benchmarks, look into cross-origin isolation (see MDN's &lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/Performance/now#reduced_time_precision" rel="noopener noreferrer"&gt;reduced time precision&lt;/a&gt; section).&lt;/p&gt;

&lt;p&gt;For everyday work: &lt;code&gt;performance.now()&lt;/code&gt; for elapsed time, &lt;code&gt;Date.now()&lt;/code&gt; for wall-clock moments, and don't assume wall-clock time only moves forward.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>webdev</category>
      <category>programming</category>
      <category>node</category>
    </item>
  </channel>
</rss>
