The map tile backend is in the middle of a multi year effort to migrate from the Flippity Service to the Floopity Service. The FlippityFlooper was believed to have finished the necessary format conversions for all map tiles in the US and Canada but 5% of the data sources were missed due to a bug that was discovered after the creator of FlippityFlooper had been promoted and changed teams, so those Floopity tiles are filled in from an older source. A junior engineer vibe-coded a stopgap fallback called FloopityFlipper that redirects to legacy Flippity Service when Floopity staleness is detected, but that redirect broke three months later due to a change in an injected dependency's experiment configuration. A bug was auto-filed and marked P2 by an overworked product manager who slightly misunderstood the scope, but the FloopityFlipper engineer will probably have a look once they are back from paternity leave.
I made all of that up but it's more plausible than conspiracy theories.
alt Hacker News
The map tile backend is in the middle of a multi year effort to migrate from the Flippity Service to the Floopity Service. The FlippityFlooper was believed to have finished the necessary format conversions for all map tiles in the US and Canada but 5% of the data sources were missed due to a bug that was discovered after the creator of FlippityFlooper had been promoted and changed teams, so those Floopity tiles are filled in from an older source. A junior engineer vibe-coded a stopgap fallback called FloopityFlipper that redirects to legacy Flippity Service when Floopity staleness is detected, but that redirect broke three months later due to a change in an injected dependency's experiment configuration. A bug was auto-filed and marked P2 by an overworked product manager who slightly misunderstood the scope, but the FloopityFlipper engineer will probably have a look once they are back from paternity leave.
I made all of that up but it's more plausible than conspiracy theories.