Hilariously, it didn't at first. I forgot I was on an IPv6 only network for a second wondering if it was supposed to be a real page or not before doing an nslookup on it. That out of the way, I would strongly suspect the airport network of faulting/interfering with the traffic first before google issues, because reCAPTCHA (while still a google product/service) by nature usually 'just works' in almost every supported browser today, and has to for adoption/usage purposes. If it were a firefox issue, there would be a whole lot more noise going around about it, but in this case, it seems very location/network specific. I suspect cellular tether or a different network would not have had the same issue at the time this occurred. -----Original Message----- From: Chris via NANOG <nanog@lists.nanog.org> Sent: Thursday, February 5, 2026 3:49 PM To: North American Network Operators Group <nanog@lists.nanog.org> Cc: Chris <nanog@hrcommunications.net> Subject: Re: Hey Google - Recaptcha sucks On 2026-02-05 12:06, William Herrin via NANOG wrote:
I'm at SEATAC airport trying to access www.google.com via the public wifi with Firefox. Apparently you really don't like that because it's stuck in a Recaptcha loop displaying captcha after captcha after captcha.
I can't help but notice that Chrome works. It's your _competitor_ Firefox that you don't seem to like. Browser bigotry. Always a treat. My interpretation; we're too cheap to hire real developers. So we just test with the browser that's on the system we're making this thing on. does https://thestart.page work for you?
IP address: 198.134.98.50 Time: 2026-02-05T20:03:35Z URL: https://www.google.com/
FIx it, eh?
Regards, Bill Herrin _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/EC BKHASYMABWJ7QVL35FFAHNX2KZ633F/
_______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/OCJWQCUY...