Ip Api logo

Is Ip Api Down?

SaaSLive status, outages, and incident history

No. Ip Api is up right now.

Every monitored Ip Api system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment Ip Api breaks

Ip Api is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Ip Api status page
How we know: the official Ip Api status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Ip Api Status Summary

As of 09:00 UTC on 9 November 2026, Ip Api is operational. PulsAPI checked Ip Api's official status page and found 38 of 38 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.92% uptime for Ip Api, counting degraded performance as up.

Cite as: PulsAPI, “Ip Api status”, checked 9 November 2026, 09:00 UTC. https://www.pulsapi.com/services/ip-api

Ip Api Component Status

The main Ip Api systems on this page. All 38 are operational right now.

38operational
Dashboard/Billing [FR-Roubaix]
Operational
DNS [a]
Operational
DNS [b]
Operational

35 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking EDNS API [DE-Limburg], Fingerprint API [FR-Roubaix], Free API [Anycast Load Balancer], Free API [AU-Sydney], Free API [NL-Amsterdam], Free API [SG-Singapore], Free API [UK-London], Free API [US-Ashburn], Free API [US-Dallas], Free API [US-Los Angeles], Free API [US-Seattle], Map Cache [FR-Roubaix], and 23 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Ip Api Outages & Incidents

Incident history from the official Ip Api status page, including resolution updates.

No recent incidents reported by the vendor.

Ip Api Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Ip Api incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 21 days with incidentsNov 9

Going further back: Ip Api uptime by month and every recorded Ip Api outage.

Live Ip Api Outage Reports

Problems reported by engineers using Ip Api. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Ip Api problems reported yet.

Something wrong with Ip Api on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Ip Api

Ip Api publishes overall service health on its public status page at status.ip-api.com. PulsAPI tracks Ip Api outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Ip Api uptime at 99.92%. Response times, incident history, and SLA tracking for Ip Api are available on the PulsAPI dashboard.

Ip Api Status FAQ

Is Ip Api down right now?

The verdict at the top of this page comes from the latest poll of the official Ip Api status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Ip Api is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Ip Api recovers.

How do I check Ip Api uptime history?

PulsAPI tracks Ip Api uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.92%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Ip Api changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Ip Api outages?

PulsAPI reads the official Ip Api status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Ip Api components?

Yes. PulsAPI monitors 38 individual Ip Api components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Ip Api goes down?

Yes. Create a free account and subscribe to Ip Api: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Ip Api to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Ip Api problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Ip Api?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Ip Api plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Ip Api with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services