Chrony Thinks It's 1970!?!?

I started getting weird logs on my database and realized the OS date is not correct:

Last login: Thu Jan  1 00:02:18 1970 from 192.168.1.96
[cachedrive@db1 ~]$ date
Thu Jan  1 00:42:11 UTC 1970 <--- :<'wtf'

I verified I had Chrony installed / running:

* chrony.service - Chrony Network Time Daemon
   Loaded: loaded (/usr/lib/systemd/system/chrony.service; enabled; vendor prese                                        t: disabled)
   Active: active (running) since Thu 1970-01-01 00:00:10 UTC; 43min ago
  Process: 276 ExecStart=/usr/bin/chronyd -u chrony (code=exited, status=0/SUCCE                                        SS)
 Main PID: 280 (chronyd)
   CGroup: /system.slice/chrony.service
           `-280 /usr/bin/chronyd -u chrony

Jan 01 00:00:10  systemd[1]: Starting Chrony Network Time Daemon...
Jan 01 00:00:10  chronyd[280]: chronyd version 2.2.1 starting (+CMDMON ...G)
Jan 01 00:00:10  chronyd[280]: Frequency 4.637 +/- 82.173 ppm read from...ft
Jan 01 00:00:10  systemd[1]: Started Chrony Network Time Daemon.
Jan 01 00:00:15  chronyd[280]: Selected source 104.131.53.252
Jan 01 00:00:45  chronyd[280]: Selected source 129.6.15.30
Jan 01 00:02:26  chronyd[280]: Selected source 104.131.53.252
Jan 01 00:07:15  chronyd[280]: Selected source 129.6.15.30
Hint: Some lines were ellipsized, use -l to show in full.

Any idea how to fix my system date? I have restarted the daemon / OS several times. My configs are pointing to valid time servers:

server 0.arch.pool.ntp.org iburst iburst
server 1.arch.pool.ntp.org iburst iburst
server 2.arch.pool.ntp.org iburst iburst

! pool 3.arch.pool.ntp.org iburst

I don't see errors in my logs and Chrony starts fine / no issues. Any ideas?