Panservice

Data as of 2026-09-13
Registry
This organisation
Netblocks9 · 1,028 IPv4 addresses
IPv6 4 prefixes (largest 2001:7f8:10::2:912/128)
Also registered under this name 14 netblocks across 5 separate records
Record ID242137839
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.97.14/32 Panservice PEERINGDB ASSIGNED ● high
185.1.114.43/32 Panservice PEERINGDB ASSIGNED ● high
193.201.28.31/32 Panservice PEERINGDB ASSIGNED ● high
217.29.67.54/32 Panservice PEERINGDB ASSIGNED ● high
2001:7f8:b:100:1d1:a5d2:912:54/128 Panservice PEERINGDB ASSIGNED ● high
2001:7f8:10::2:912/128 Panservice PEERINGDB ASSIGNED ● high
2001:7f8:b9::14:1/128 Panservice PEERINGDB ASSIGNED ● high
2001:7f8:c5::a502:912:1/128 Panservice PEERINGDB ASSIGNED ● high
212.66.96.0/22 PANSERVICE-NET RIPE ASSIGNED PA ● low

IPv6 ranges (4)

CIDR
2001:7f8:10::2:912/128
2001:7f8:b9::14:1/128
2001:7f8:b:100:1d1:a5d2:912:54/128
2001:7f8:c5::a502:912:1/128

Footprint over time

12 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-09-13

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

AS20912 DUMY-RIPE DUMY-RIPE PANSERVICE-NOC