Server has wrong time/date

[ianhobson]

ian@hobsoni:~$ timedatectl status
                      Local time: Sun 2019-11-17 16:45:20 GMT
                  Universal time: Sun 2019-11-17 16:45:20 UTC
                        RTC time: n/a
                       Time zone: Europe/London (GMT, +0000)
       System clock synchronized: yes
systemd-timesyncd.service active: yes
                 RTC in local TZ: no
ian@hobsoni:~$ curl -i letsencrypt.org 2>&1 | grep Date
Date: Fri, 15 Nov 2019 23:34:08 GMT
ian@hobsoni:~$

Need I say more - your server is a bit slow!

How/where can I report/

[rmbolger]

This may be a side effect of the service disruption they’re experiencing. I’d hold off until everything is green again.

[Osiris]

Doubtful @rmbolger, as letsencrypt.org is hosted on the public data center while the disruption is affecting High Assurance Datacenter 1 and High Assurance Datacenter 2?

[Phil]

We will reach out to Netlify about this.

[rg305]

From your

@ianhobson

Need I say more - your server is a bit slow!

I guess, I would say "YES", please say more.

I don't see how the "timestamp" on a web page indicates the current time on that system.
[If that's what you are implying.]

I do see that different systems returned different timestamps:
[that may be a problem - out-of-sync]

curl -i letsencrypt.org 2>&1 | grep Date
Date: Sat, 16 Nov 2019 22:37:52 GMT
Date: Fri, 15 Nov 2019 23:35:30 GMT
Date: Fri, 15 Nov 2019 23:35:30 GMT
Date: Fri, 15 Nov 2019 23:35:30 GMT
Date: Sat, 16 Nov 2019 22:37:53 GMT

[ianhobson]

I was having a lot of errors failing to obtain the certificate status. After 2-3 days of this, I followed up on How to solve OCSP_check_validity() error? withut reading it carefully.
I expected the times to be close. They were not.

However the problem appears to have cleared now. So I can’t get any new evidence.
Rgds

[rg305]