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.
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.
My immediate reaction when reading that paragraph was that someone as security-minded as Aaron would probably not leave his password saved in a Skype client.
“You can’t really raise enough money on Kickstarter yet. There are some new sites starting that will eventually allow anyone and everyone to own a piece of a movie; invest in it like a stock. But you can imagine the amount of legal issues this raises. So look for it sometime around 3012.”
Your goals and Zach’s just don’t align on this one—so don’t back it. His feelings will probably not be hurt and he will still be glad to sell you a DVD when the time comes.
This is a Kickstarter project, not an Amazon pre-order.
And also those same fans are now less motivated to go see the film in theaters because their DVD is already pre-ordered, potentially hurting box office revenue.
It is actually brilliant, now he can go to the distributors and say "these thousands of people were so excited about this project that they paid to make it... so of course they will pay us to see it!"
I am not sure that "gospel truth" is a fair characterization.
Anonymous IRC person has provided verifiable details that strongly suggest he or she had access to Linode administrative systems. Fyodor's post to nmap-dev supports the notion that customer nodes were accessed as well.
Linode has provided no details or evidence of anything.
I don't think one has to take that IRC log as gospel truth to be reasonably concerned about the security of their data stored by Linode.
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.