Every IP range, resolved to its timezone.

The database's schema and metadata are documented carefully. It is published as CSVGZ and MMDB.

One call gets you the current IP Timezone build. Every official client wraps it three ways: straight to disk, a time-limited link you hand to your own runner, or bytes in memory. A file written to disk lands only once the whole transfer has arrived, and checksums() returns the published digests to verify it against.

download()

Streams the current build to a file, which lands only once the whole transfer has arrived, so a failed one never leaves a truncated file behind.

downloadUrl()

The time-limited link the API redirects to, for your own downloader, a job runner or a CDN pull.

downloadBytes()

The build in memory, for a small database or a pipeline that never touches a filesystem.

metadata()

Row count, file sizes and when the build last updated. Poll it and fetch only when a new one has landed.

checksums()

The md5, sha1, sha256 and sha512 digests of one file, to verify it once it lands.

PythonPHPNode.jsJavaGocURL

import os
from internetdata import InternetData
 
client = InternetData(os.environ["INTERNETDATA_API_KEY"])
 
# what is in today's build, without moving the file
meta = client.database.metadata("ip_timezone_v1")
 
client.database.download("ip_timezone_v1", "mmdb", "./ip_timezone_v1.mmdb")
sums = client.database.checksums("ip_timezone_v1", "mmdb")
print(meta.updated, meta.entries, sums["sha256"])

load.pypip install internetdata

Also available for .NET, Ruby, Rust, Swift, Erlang, Perl and Zig. See all on GitHub →

Getting your hands on it.

The file is the product. Teams join IP Timezone against traffic they already log, inside their own infrastructure, and never send an address anywhere to get an answer.