Last tested: May 12, 2020
For users who would like to keep very secure networks for their Looker instance, it is possible for them to create network settings that result in network blackholing, which is the process of discarding incoming or outgoing traffic. When this happens we can have processes like Chromium wait for a timeout before completing their tasks.
We have see this primarily with Chromium tasks. When trying to perform a Chromium task, we would have about 4 minutes of unaccounted time where we are waiting for a response back from Google Analytics or ping.looker.com. After this response is timed out, Chromium performs its task as expected, but happens slowly.
The way to fix this is to immediately reject this traffic or disable it in the first place. Some ways to accomplish this are:
This content is subject to limited support.