From https://support.cloud.google.com/portal/system-status:

Status: Fully Resolved

Product group: Google Workspace

Products affected: Admin Console, Chrome Browser, Endpoint Management

Start time: Tuesday, June 16, 2026, 10:28:15 PM GMT-07:00

End time: Tuesday, June 16, 2026, 10:28:24 PM GMT-07:00

Description: A subset of users within the EU and Americas regions may have encountered a TLS certificate pop-up while using Workspace Apps.

Steps to reproduce: Impacted users may have encountered a popup where "lh3.googleusercontent.com" is asking for a TLS certificate when using any Workspace Apps.

This issue does not impact any critical functions on the corresponding Apps, as an option to bypass the prompt is available to users.

Workaround: The issue is mitigated now.

Updates: Tuesday, June 16, 2026, 5:31:51 PM GMT-07:00:

We are investigating a potential issue with Chrome Browser.

We will provide more information by Tuesday, 2026-06-16 18:00 PDT.

Tuesday, June 16, 2026, 5:40:40 PM GMT-07:00:

We are investigating the authentication prompt issue on Chrome browser beginning on Tuesday, 2026-06-16 05:30 PDT.

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2026-06-16 19:00 PDT with current details.

We apologize to all who are affected by the disruption.

Tuesday, June 16, 2026, 7:05:40 PM GMT-07:00:

We are investigating the authentication prompt issue while using Workspace Apps beginning on Tuesday, 2026-06-16 05:30 PDT.

Our engineering team has identified the root cause and mitigation is currently underway. We do not have ETA for mitigation at the moment.

We will provide an update by Tuesday, 2026-06-16 20:30 PDT with current details.

Tuesday, June 16, 2026, 8:16:33 PM GMT-07:00:

We are investigating the authentication prompt issue while using Workspace Apps beginning on Tuesday, 2026-06-16 05:30 PDT.

Our engineering team has identified the root cause and mitigation is currently underway. We do not have ETA for mitigation at the moment.

We will provide an update by Wednesday, 2026-06-17 00:00 PDT with current details.

Tuesday, June 16, 2026, 10:28:15 PM GMT-07:00:

The issue with Workspace Apps has been resolved for all affected users within the EU and Americas regions as of Tuesday, 2026-06-16 19:41 PDT

From a preliminary analysis, the issue was due to a configuration error that inadvertently requested client certificates. Our engineers have mitigated the issue by fully rolling back the affected configurations to a previous working state.

We thank you for your patience while we worked on resolving the issue.

Have you been to San Francisco or the Silicon Valley?

It has been my experience in tech companies and social circles that the term nerd is often considered a badge of honor and is even used to refer to one's self and friends.

See also https://vimeo.com/73589975

> the term nerd is often considered a badge of honor

N = 1, but in my experience this stopped being the case when being nerdy was deemed cool and anyone with glasses started proclaiming "I'm so nerdy".

I suppose this sort of makes me a hipster.

No, it makes you a second-wave nerd with hipster tendencies.

(I of course just made that up.)

It's OpenVZ or Virtuozzo.

http://openvz.org/

http://www.parallels.com/products/pvc/

Yeah, keep it classy.

"First, your data is stored on Google servers — essentially the same servers as Gmail. This means your secrets are as safe as your email."

Well, if David says so…

Except that qwerty_asdf wasn't referring to a /24 subnet, (s)he was talking about one of the three address spaces defined in RFC 1918 and described thusly:

"Note that (in pre-CIDR notation) the first block is nothing but a single class A network number, while the second block is a set of 16 contiguous class B network numbers, and third block is a set of 256 contiguous class C network numbers."

So it is common for crusty old network engineers and sysadmins to refer to 192.168/16 as "the class C" private block, even when they understand that you can subnet it however you'd like.

> ... (s)he was talking about one of the three address spaces defined ...

Right, I realized that when s/he said "reserved Class C range". It was more of a general observation. I always forget I have to be extremely specific here on HN.

This made me feel really old, so I checked your math:

  2003 1981 - p
  22
  1981 1949 - p
  32

This. I imagine that an agency with the resources of the NSA could probably work out a couple of ways to obtain almost any private key they want.

Interesting that this would bubble to the top today in light of the Verizon FISA story.

The White House and others defending the practice keep repeating “it’s just metadata.”

Knowing exactly who you talk to, when, where, and for how long can expose a lot about you and be pretty incriminating!