CDN · file snapshot 2026-09-21

Bunny.net IP ranges

The Bunny.net file fetched on 2026-09-21 contained 587 distinct IPv4 prefix strings and 0 IPv6 prefix strings. Inspect the source URL, recorded fields and content hash below.

IPv4
587
IPv6
0
Fetched
2026-09-21
Publisher
Bunny.net
Category
CDN
IPv4 prefix strings
587
IPv6 prefix strings
0
Source file
https://api.bunny.net/system/edgeserverlist
File format
JSON
Size
9,607 bytes
Fetched (UTC)
SHA-256
3c428f160da2e8511cb314c8cd6ab4399653ff51aec7ac4a4e679f9af1abf012
Documentation
bunny.net/docs/cdn/connectivity

File measurement

Distinct valid prefix strings in the downloaded file. Overlapping prefixes are kept, so the count describes entries, not address-space size.
587
IPv4 prefix strings
0
IPv6 prefix strings
9,607
bytes
JSON
file format
Prefix count split: IPv4 100.0% / IPv6 0.0%. This compares entries, not address-space size.

Fields recorded from the file

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 it. The result includes counts, fields and a hash; a different hash means you measured different bytes. Full counting method.
Measure a saved file
python3 ip-ranges-measure.py provider-file

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.
Bunny.net ASN records
ASNRIPEstat holderChecked
AS200325BunnyCDN BUNNYWAY, informacijske storitve d.o.o.2026-09-21

Interpreting this snapshot

Where is the Bunny.net IP range file?
The selected snapshot was downloaded from https://api.bunny.net/system/edgeserverlist. The source and documentation links on this page 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.670263+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.

To test an address against a saved file, follow the Python cloud CIDR matching guide. Its example parses AWS JSON; adapt the parser to this publisher's schema and preserve all matching records.

Sources

A range file lists addresses the publisher attributes to its service. Matching an address against it shows only that the address falls inside a listed prefix; it does not identify the requester or the location of a device.