Skip to content
IP-API.io logo

Is IP-API.io API down?

Current status, daily uptime history and troubleshooting for the IP-API.io API (Geocoding).

No, IP-API.io is up

IP-API.io answered our last daily check (Oct 24, 2026, 12:25 UTC) in 522 ms with HTTP 200.

Checking IP-API.io now…

Sending a request from our server.

IP-API.io API uptime history

30 days agoLatest check
Uptime
2 checks so far
Last check
Oct 24, 2026, 12:25 UTC
Response
522 ms · HTTP 200
Last up
Now

We check IP-API.io's listed URL (https://ip-api.io) once a day. History started when IP-API.io was first checked, so new entries show fewer than 30 days.

IP-API.io API not working for you?

  1. IP-API.io 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.
  2. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  3. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  4. 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. 1ipwhois logo

    ipwhois API

    Online · 226 ms

    IP 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. 2administrative-divisons-db logo

    administrative-divisons-db API

    Online · 745 ms

    Get all administrative divisions of a country.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3HackMyIP logo

    HackMyIP API

    Online · 1047 ms

    IP 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. 4ipapi.co logo

    ipapi.co API

    Online · 780 ms

    Find IP address location information.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5LatLng logo

    LatLng API

    Online · 431 ms

    Geocoding, reverse geocoding, places, and static maps.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all IP-API.io alternatives · APIs down right now

IP-API.io API status FAQ

Is IP-API.io API down right now?

IP-API.io answered our last daily check (Oct 24, 2026, 12:25 UTC) in 522 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether IP-API.io is responding at this moment.

How do you check whether IP-API.io API is up?

Once a day our checker requests IP-API.io's listed URL (https://ip-api.io) 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 IP-API.io API is down?

Free Geocoding APIs that were up at their last check include ipwhois, administrative-divisons-db, HackMyIP. See the full list of IP-API.io alternatives for a comparison.

Why does IP-API.io API work for others but not for me?

IP-API.io 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.