Is IPKit API down?
Current status, daily uptime history and troubleshooting for the IPKit API (Geocoding).
No, IPKit is up
IPKit answered our last daily check (Nov 15, 2026, 13:58 UTC) in 752 ms with HTTP 200.
Checking IPKit now…
Sending a request from our server.
IPKit API uptime history
- Uptime
- 100% of 10 checks
- Last check
- Nov 15, 2026, 13:58 UTC
- Response
- 752 ms · HTTP 200
- Last up
- Now
We check IPKit's listed URL (https://ipkit.dev/docs) once a day. History started when IPKit was first checked, so new entries show fewer than 30 days.
IPKit API not working for you?
- 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
Moradas API
Online · 1060 msPortuguese address autocomplete and 7-digit postal codes (CP7).
- No API key needed
- 100% uptime (30 days)
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
IPKit API status FAQ
Is IPKit API down right now?
IPKit answered our last daily check (Nov 15, 2026, 13:58 UTC) in 752 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether IPKit is responding at this moment.
How do you check whether IPKit API is up?
Once a day our checker requests IPKit's listed URL (https://ipkit.dev/docs) 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 IPKit API?
IPKit 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 IPKit API is down?
Free Geocoding APIs that were up at their last check include SLF, 17NAS, administrative-divisons-db. See the full list of IPKit alternatives for a comparison.
Why does IPKit API work for others but not for me?
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.