Pixel Hosting

PixelHosting
Data as of 2026-11-01
Registry
This organisation
Netblocks9
IPv6 5 prefixes (largest 2001:7f8:12a::77/128)
Also registered under this name 10 netblocks across 2 separate records
Record ID261109411
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.249.208.169/32 PixelHosting PEERINGDB ASSIGNED ● high
185.1.240.77/32 PixelHosting PEERINGDB ASSIGNED ● high
193.201.157.136/32 PixelHosting PEERINGDB ASSIGNED ● high
193.239.117.12/32 PixelHosting PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:21:5085:1/128 PixelHosting PEERINGDB ASSIGNED ● high
2001:7f8:13::a521:5085:1/128 PixelHosting PEERINGDB ASSIGNED ● high
2001:7f8:12a::77/128 PixelHosting PEERINGDB ASSIGNED ● high
2001:7f8:160::21:5085:1/128 PixelHosting PEERINGDB ASSIGNED ● high
2001:7f8:160::21:5085:2/128 PixelHosting PEERINGDB ASSIGNED ● high

IPv6 ranges (5)

Footprint over time

17 weekly snapshots · JSON
9 +3 netblocks since 2026-07-05
2026-07-05 peak 9 2026-11-01

Network trust

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

NIC Handles

AS215085