You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This migration is taking place this week with a DNS update to perf.golang.org. The new infrastructure will not provision SSL certificates for perf.golang.org until this DNS change completes rolling out. As a result, you may see invalid SSL certificate warnings [1] if you receive the updated DNS records prior to certificate provisioning.
https://perf.golang.org is a low traffic service so we do not expect this to affect many users.
As part of #48803, we are making various improvements to https://perf.golang.org, including moving this service to the same infrastructure used by https://build.golang.org and others.
This migration is taking place this week with a DNS update to
perf.golang.org
. The new infrastructure will not provision SSL certificates forperf.golang.org
until this DNS change completes rolling out. As a result, you may see invalid SSL certificate warnings [1] if you receive the updated DNS records prior to certificate provisioning.https://perf.golang.org is a low traffic service so we do not expect this to affect many users.
Note that the performance storage service (contacted by tools like
benchsave
), https://perfdata.golang.org, is not affected by this migration and will remain accessible. This service can be contacted directly as a workaround for accessing benchmark results. e.g., https://perf.golang.org/search?q=upload:20220411.10 -> https://perfdata.golang.org/search?q=upload:20220411.10We expect this roll out to take a few days, and will close this issue once certificate provisioning is complete.
[1] In this period, I believe users will receive a certificate issued to
Common Name (CN) gerritbot.golang.org
, rather thanperf.golang.org
.The text was updated successfully, but these errors were encountered: