GigaPIX Route Servers

Data as of 2026-09-27
BGP inherited
This organisation
Netblocks8
IPv6 4 prefixes (largest 2001:7f8:a:1::1000/128)
Record ID246007500
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.136.250.244/32 GigaPIX Route Servers PEERINGDB ASSIGNED ● high
193.136.250.245/32 GigaPIX Route Servers PEERINGDB ASSIGNED ● high
193.136.251.61/32 GigaPIX Route Servers PEERINGDB ASSIGNED ● high
193.136.251.62/32 GigaPIX Route Servers PEERINGDB ASSIGNED ● high
2001:7f8:a:1::1000/128 GigaPIX Route Servers PEERINGDB ASSIGNED ● high
2001:7f8:a:1::1244/128 GigaPIX Route Servers PEERINGDB ASSIGNED ● high
2001:7f8:a:2::1061/128 GigaPIX Route Servers PEERINGDB ASSIGNED ● high
2001:7f8:a:2::1062/128 GigaPIX Route Servers PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Footprint over time

14 weekly snapshots · JSON
8 -1 netblocks since 2026-07-05
2026-07-05 peak 9 2026-09-27

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (4 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS12833