Service Status
Live status of ipto infrastructure.
What this page checks
Each row is a live probe run from your browser against ipto's own endpoints when the page loads: the core API (an IP lookup round-trip), the geolocation dataset (the bundled IP-to-location database), the cache layer (Cloudflare KV, used for rate limits and memoised lookups) and the CDN / edge (the Cloudflare network that terminates your connection). A row turns green when its probe answers correctly and quickly, amber when it is slow, and red when it fails. Because the probes run from your own browser, the page shows the service as you experience it, including any problem on your own network path.
What each component means
- Core API: the Worker that answers lookups and serves this site. If it is down, nothing else on ipto will respond.
- Geolocation dataset: the location, ASN and network records behind every IP result. A problem here usually shows up as missing city or ISP fields.
- Cache layer: stores rate-limit counters and recently computed answers. When it is slow, requests still succeed but take longer.
- CDN / edge: the global network that delivers pages and API responses close to the visitor.
How ipto is run
ipto runs on Cloudflare Workers, so requests are answered from the data centre closest to the caller. IP, ASN, threat-feed and exchange-rate datasets are refreshed by a daily scheduled job; if a refresh fails, the previous snapshot keeps serving until the next successful run, so lookups degrade to slightly older data rather than failing outright. The site never stores the IP addresses you look up, which is why this page reports health only and carries no per-user history.
If something looks wrong
A red row usually means a transient network problem between you and the edge. Reload the page after a minute; if it persists, check the API documentation for the current endpoint behaviour or the FAQ for known limits such as the free-tier daily quota.