Does it jive with this?
https://sinfulforums.net/t/test-topic-title/141.json
[{"id":526,
"name":"Lunorian","username":"lunorian",
"avatar_template":"/user_avatar/sinfulforums.net/lunorian/{size}/3_1.png",
"created_at":"2017-11-11T21:09:26.238Z",
"cooked":"\u003cp\u003etest text goes here we are just testing\u003c/p\u003e",
"post_number":1,"post_type":1,
"updated_at":"2017-11-11T21:09:26.238Z","reply_count":0,
When you posted, it should be around 11pm EST (what are you doing anyway up close to midnight on Saturday night?) 
That means it would have been around 4am UTC.
The database record shows that it is created_at is 9pm UTC, which is obviously not correct. Therefore your problem came about at the time the database record is created.
EDIT: There is a difference of 7 hours, which if you wind your browser BACKWARDS by 7hr, it brings you EXACTLY to the date line. I suspect some time zone mistake.
EDIT 2: Notice that the UTC timestamp is Nov 11, not Nov 12. Which means that it is going BACKWARDS 7 hr.
So server time isn’t the issue, Discourse time is, where is Discourse getting the time from and how can this be corrected?
AFAIK, Discourse uses Ruby Time, the default is
Did you change that?
I’m in the Eastern timezone, and when I go to this site I see a difference of 7 hours for the UTC time
It looks like if I were to somehow pass my local time as the create time it would become “7 hours ago”
Are you posting through the UI or through the API or email?
The database record is incorrect, so there’s an issue when it’s saving the record.
What do these commands return?
$ date
$ date -u
$ readlink /etc/localtime
Along with the time on your machine when running that.
So apparently time was going away haywire due to NTP Sync and the DDoS Protection. A work-around is in place and the issue is resolved.