Troubleshooting

404 errors in your browser console for satellite tiles are expected and harmless: they're real coverage gaps, not a bug. If the map is stuck on "Loading satellite data…", that usually means a lost connection; reload the page.

Why do I see 404 errors in the browser console?

Chlorofishy never renders a tile for water a satellite genuinely didn't cover: a real swath gap, not a data quality issue. Your browser still requests every tile in the visible area to check, and the ones that were never generated come back 404. That shows up as an error in your browser's developer console, but it doesn't affect what you see on the map, which already shows those areas correctly as empty. See why there are holes for what a gap actually means.

The map won't stop loading. What's wrong?

A map that stays on "Loading satellite data…" and never settles almost always means the connection needed to load the base map dropped partway through, common right after your signal drops or on a weak connection. There's no offline mode to fall back to, so the fix is simply to reload once your connection is back.

A region shows no data: is that a bug?

Not necessarily. See satellite pass coverage by region for the difference between a region that's genuinely empty right now and one where passes exist but aren't included in your plan; the map shows a different message for each.

Still stuck?

Email [email protected] with what you were trying to do. For billing or subscription issues specifically, use [email protected] instead, per managing your subscription.