According to the logs, Samus connected to the WiFi and went online in ~4 seconds, but then quickly lost Internet access (ie: connected but not online). I've been meaning to talk to the Chrome team about this for a while- I've personally experienced similar problems before (with Gmail as well!), and my hunch is that this is not a WiFi problem.

Alex (Komoroske), could we get some Chrome eyes on this? Also, the next time you see this issue, could you note whether the WiFi icon is animating ("looking for WiFi") during the 10-30 seconds, or it's static ("connected to WiFi") after a while but you still can't connect to the Internet?

Chrome OS WiFi team, could someone help quickly verify that WiFi is not at fault here?

Thanks!

Can we request the user to turn off BeyondCorp temporarily and try to work on (connect, disconnect, launch apps) Google-A for a bit? 
The "connected but not online" makes me more suspicious of BeyondCorp.

In response to #1, when it's in this state the wifi icon is not animated, but shows fully connected even when nothing connect.

I will leave the BeyondCorp extension off all day tomorrow and see if the problem goes away. 

Alright, as expected (it's likely not a WiFi problem). Let's see if turning off BeyondCorp will resolve this. Thanks Alex!

Just opened my computer on Google-A for the first time today, with BeyondCorp set to "Off". Wifi worked instantly. I'd say that makes it pretty clear that it's on BeyondCorp's side. I'll file an internal bug.

Filed b/28949520