PIT - IP Services

Data as of 2026-08-23
BGP inherited
Cluster stats
Netblocks9
IPv6 4 prefixes (largest 2801:11:8400:2::11/128)
Registered in CO (3) · EC (1) · PE (1)
All fragments 35 blocks across 2 clusters
Cluster ID229201415
RegistryPEERINGDB
Customersfind customers using 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

Footprint over time

9 weekly snapshots · JSON
9 +2 netblocks since 2026-07-05
2026-07-05 peak 9 2026-08-23

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.24.12/32 PIT - IP Services PEERINGDB ASSIGNED ● high
45.68.24.14/32 PIT - IP Services PEERINGDB ASSIGNED ● high
45.68.31.11/32 PIT - IP Services PEERINGDB ASSIGNED ● high
45.68.122.11/32 PIT - IP Services PEERINGDB ASSIGNED ● high
45.183.47.15/32 PIT - IP Services PEERINGDB ASSIGNED ● high
2801:11:8400:2::11/128 PIT - IP Services PEERINGDB ASSIGNED ● high
2801:1a:5800:140::f/128 PIT - IP Services PEERINGDB ASSIGNED ● high
2803:cd60:57ff::11/128 PIT - IP Services PEERINGDB ASSIGNED ● high
2803:cd60:6411:5::f/128 PIT - IP Services PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Network trust

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

NIC Handles

AS64146