IP-STAR SAS
BGP inherited
Cluster stats
| Netblocks | 5 · 2,811 IPv4 addresses |
| Cluster ID | 204407665 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.93.40.0/24 | IP-STAR SAS | BGP | ANNOUNCED | ● high |
| 193.93.40.0/22 | IP-STAR SAS | RIPE | ASSIGNED PI | ● high |
| 193.93.40.0/22 | IP-STAR SAS | BGP | ANNOUNCED | ● high |
| 193.93.41.0/24 | IP-STAR SAS | BGP | ANNOUNCED | ● high |
| 193.93.42.0/24 | IP-STAR SAS | BGP | ANNOUNCED | ● high |
Possibly related to this organisation
what's this?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.
- ARH-IP-STARCEV-LAN via PJSC MegaFon sub-allocation
- Starcev New via PJSC MegaFon sub-allocation
- NET-IN2IP-STARBYTES via in2ip B.V. sub-allocation
- Starodubov Dmitriy Evgenievich sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
No discrepancies found among checked blocks.
NIC Handles
AS214232
DUMY-RIPE
DUMY-RIPE
JAGUAR-MNT
JAGUAR-MNT
ORG-NA1535-RIPE
RIPE-NCC-END-MNT