Is Google Earth Engine API down?
Current status, daily uptime history and troubleshooting for the Google Earth Engine API (Geocoding).
No, Google Earth Engine is up
Google Earth Engine answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1977 ms with HTTP 200.
Checking Google Earth Engine now…
Sending a request from our server.
Google Earth Engine API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 1977 ms · HTTP 200
- Last up
- Now
We check Google Earth Engine's listed URL (https://developers.google.com/earth-engine/) once a day. History started when Google Earth Engine was first checked, so new entries show fewer than 30 days.
Google Earth Engine API not working for you?
- Google Earth Engine needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If calls fail only in the browser with a CORS error, Google Earth Engine may not allow cross-origin requests. Call it from your server instead.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Geocoding APIs up at their last check
- 1
ipwhois API
Online · 226 msIP geolocation with country, city, coordinates, ISP, timezone and flag data.
- No API key needed
- Fast: 226 ms response
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
administrative-divisons-db API
Online · 745 msGet all administrative divisions of a country.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
HackMyIP API
Online · 1047 msIP geolocation, ISP and privacy/VPN scoring, email breach checks, DNS and WHOIS lookups.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
ipapi.co API
Online · 780 msFind IP address location information.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
LatLng API
Online · 431 msGeocoding, reverse geocoding, places, and static maps.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
Compare all Google Earth Engine alternatives · APIs down right now
Google Earth Engine API status FAQ
Is Google Earth Engine API down right now?
Google Earth Engine answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1977 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether Google Earth Engine is responding at this moment.
How do you check whether Google Earth Engine API is up?
Once a day our checker requests Google Earth Engine's listed URL (https://developers.google.com/earth-engine/) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if Google Earth Engine API is down?
Free Geocoding APIs that were up at their last check include ipwhois, administrative-divisons-db, HackMyIP. See the full list of Google Earth Engine alternatives for a comparison.
Why does Google Earth Engine API work for others but not for me?
Google Earth Engine needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, Google Earth Engine may not allow cross-origin requests. Call it from your server instead.