Is sthan.io Reverse Geocoding API down?
Current status, daily uptime history and troubleshooting for the sthan.io Reverse Geocoding API (Geocoding).
No, sthan.io Reverse Geocoding is up
sthan.io Reverse Geocoding answered our last daily check (Oct 24, 2026, 12:25 UTC) in 838 ms with HTTP 200.
Checking sthan.io Reverse Geocoding now…
Sending a request from our server.
sthan.io Reverse Geocoding API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 838 ms · HTTP 200
- Last up
- Now
We check sthan.io Reverse Geocoding's listed URL (https://sthan.io/products/reverse-geocoding-usa) once a day. History started when sthan.io Reverse Geocoding was first checked, so new entries show fewer than 30 days.
sthan.io Reverse Geocoding API not working for you?
- sthan.io Reverse Geocoding 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.
- sthan.io Reverse Geocoding doesn't send CORS headers, so browsers block calls made directly from a web page. 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 sthan.io Reverse Geocoding alternatives · APIs down right now
sthan.io Reverse Geocoding API status FAQ
Is sthan.io Reverse Geocoding API down right now?
sthan.io Reverse Geocoding answered our last daily check (Oct 24, 2026, 12:25 UTC) in 838 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether sthan.io Reverse Geocoding is responding at this moment.
How do you check whether sthan.io Reverse Geocoding API is up?
Once a day our checker requests sthan.io Reverse Geocoding's listed URL (https://sthan.io/products/reverse-geocoding-usa) 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 sthan.io Reverse Geocoding API is down?
Free Geocoding APIs that were up at their last check include ipwhois, administrative-divisons-db, HackMyIP. See the full list of sthan.io Reverse Geocoding alternatives for a comparison.
Why does sthan.io Reverse Geocoding API work for others but not for me?
sthan.io Reverse Geocoding 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. sthan.io Reverse Geocoding doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.