I’ve been seeing similar issues with large travel sites lately, so your experience doesn’t surprise me. When the homepage returns a 200 but shows an error page, it usually means something broke in their reverse proxy or CDN rules. That tends to happen when a new deployment goes live without enough real-world testing.

Since most of Expedia Group’s support is script-driven, it’s almost impossible to report a technical problem unless you know someone on their engineering team. The shifting behavior across browsers and devices also makes it look like a bad A/B test or traffic-split configuration.

It’s not great when a company that size lets something this visible slip into production. Hopefully someone from their engineering team notices this thread and rolls back the change.