PRIVATECOFFEE

Data as of 2026-09-13
Unresolved
This organisation
Netblocks5
IPv6 3 prefixes (largest 2001:7f8:f2:e1:a5:21:4139:1/128)
Record ID242146427
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution unresolved
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 (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.155.146/32 PRIVATECOFFEE PEERINGDB ASSIGNED ● high
185.1.166.83/32 PRIVATECOFFEE PEERINGDB ASSIGNED ● high
2001:7f8:f2:e1:a5:21:4139:1/128 PRIVATECOFFEE PEERINGDB ASSIGNED ● high
2a0c:b641:701:0:a5:21:4139:1/128 PRIVATECOFFEE PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:46::1af/128 PRIVATECOFFEE PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Network trust

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

NIC Handles

AS214139