Is FindIP API down?
Current status, daily uptime history and troubleshooting for the FindIP API (Geocoding).
No, FindIP is up
FindIP answered our last daily check (Nov 15, 2026, 13:58 UTC) in 952 ms with HTTP 200.
Checking FindIP now…
Sending a request from our server.
FindIP API uptime history
- Uptime
- 100% of 10 checks
- Last check
- Nov 15, 2026, 13:58 UTC
- Response
- 952 ms · HTTP 200
- Last up
- Now
We check FindIP's listed URL (https://www.findip.net/Docs/api-response) once a day. History started when FindIP was first checked, so new entries show fewer than 30 days.
FindIP API not working for you?
- FindIP 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 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
SLF API
Online · 285 msGerman city, country, river, database.
- No API key needed
- 100% uptime (30 days)
- Fast: 285 ms response
- Callable from the browser (CORS)
No authHTTPSCORS - 2
17NAS API
Online · 1147 msFree IP geolocation API with IPv4/IPv6 detection, ASN and country info, no auth required.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
administrative-divisons-db API
Online · 452 msGet all administrative divisions of a country.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
ipapi.co API
Online · 951 msFind IP address location information.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
IPKit API
Online · 752 msIP lookup with location, ASN/ISP and VPN/proxy/Tor signals.
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
FindIP API status FAQ
Is FindIP API down right now?
FindIP answered our last daily check (Nov 15, 2026, 13:58 UTC) in 952 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether FindIP is responding at this moment.
How do you check whether FindIP API is up?
Once a day our checker requests FindIP's listed URL (https://www.findip.net/Docs/api-response) 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.
How reliable is FindIP API?
FindIP answered 100% of our last 10 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.
What can I use if FindIP API is down?
Free Geocoding APIs that were up at their last check include SLF, 17NAS, administrative-divisons-db. See the full list of FindIP alternatives for a comparison.
Why does FindIP API work for others but not for me?
FindIP 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 it works from one network but not another, check firewalls, VPNs and regional blocks.