I have outbound QOS to prioritize HTTP over other traffic, but Google Maps immediately detects that as an attack and forces me to re-enter the captcha to re-enable the satellite view. I spent about two days trying to figure it out. The solution is to add another QOS rule on Google Maps' subnet 220.127.116.11 to lowest priority. This has almost no effect on Google map's refresh speed and prevents tripping Google's IDS. Is this a real bug or one of those QOS caveats we have to live with?