PPPOE_NAT
Data as of 2026-10-04
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
This organisation
| Netblocks | 3 · 264 IPv4 addresses |
| Record ID | 246184857 |
| Registry | AFRINIC |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 85.93.49.0/24 | PPPoE-NAT | RIPE | ASSIGNED PA | ● low |
| 102.211.122.244/30 | PPPOE_NAT | AFRINIC | ASSIGNED PA | ● low |
| 102.211.122.248/30 | PPPOE_NAT | AFRINIC | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(1 of 3)
RPKI-inferred operator
PJSC Rostelecom
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
CAIT-MNT
DUMY-RIPE
DUMY-RIPE
VA23-AFRINIC
VA23-AFRINIC
VTL3-MNT