Cloud platform / file snapshot 2026-09-21
Akamai Connected Cloud (Linode) IP ranges
The Akamai Connected Cloud (Linode) file fetched on 2026-09-21 contained 5,409 distinct IPv4 prefix strings and 96 IPv6 prefix strings. Inspect the source URL, recorded fields and content hash below.
File measurement
5,409
IPv4 prefix strings
96
IPv6 prefix strings
192,744
bytes
TEXT
file format
- Source URL
- https://geoip.linode.com/
- Fetched at (UTC)
- SHA-256 of downloaded bytes
- e534ed66ae7c46926c05d43b5b5ff1a68680c1405336d3e64561ef05edcd65c9
Fields recorded from the file
These are literal field names and values. A timestamp or counter is shown without assigning an update schedule to it.
The parser recorded no publisher version or timestamp field for this file.
No selected facet values were collected by this measurement.
Reproduce the count
Save the linked source as provider-file, download the Python measurement script, then run:
python3 ip-ranges-measure.py provider-fileThe result includes counts, fields and a hash. A different hash means you measured different bytes. Counts retain overlapping prefixes and repeated address space under different prefix lengths. Full counting method.
ASN reference records
Holder names were read from RIPEstat on the dates below. These are separately selected reference records, not a mapping of every prefix to its origin ASN. A listed holder may differ from the provider named on this page.
Interpreting this snapshot
Where is the Akamai Connected Cloud (Linode) IP range file?
The selected snapshot was downloaded from https://geoip.linode.com/. The source and documentation links above let you inspect the publisher's current data and scope.
What does a matching prefix establish?
A match means an address falls inside a prefix in this selected file. The measurement does not establish the identity of a requester, a device location or ownership of every address. Check the publisher’s documentation before applying access rules.
How often is this file updated?
This record measures the file fetched at 2026-09-21T19:35:32.812694+00:00. Publisher fields are reproduced as recorded, without inferring a future update schedule. Download the current source and compare hashes to check for a change.