TNF-PUBLIC-SERVERS1
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 206193781 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 83.137.137.32 – 83.137.137.127 | TNF-PUBLIC-SERVERS1 | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TNF PUBLIC” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- TNF-PUBLIC-SERVICES 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- PSCPUBLICSOF-HWY-AT via A1 Telekom Austria AG sub-allocation
- Publicis Ia via COLT Technology Services Group Limited sub-allocation
- Public_Services_Department via JT (Jersey) Limited sub-allocation
- ONCEPUBLIC via AYESA IBERMATICA, SAU sub-allocation
- PUBLICIS-LL via Vodafone-panafon Hellenic Telecommunications Company SA sub-allocation
- Publictelevision via Viva Armenia CJSC sub-allocation
- PUBLIC-DMZ-DIADEMYS via Claranet Limited sub-allocation
- WISP-CORE-PUBLIC01 via iunxi B.V. sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
TNF-MNT