SI-T2-NETWORK
Cluster stats
| Netblocks | 19 |
| All fragments | 360 blocks across 308 clusters |
| Cluster ID | 195475586 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a01:260::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a01:261::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a01:261::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:200::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:300::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:400::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:500::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:600::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:700::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:900::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:b00::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:c00::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:261:d00::/40 | SI-T2-NETWORK | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:262::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a01:263::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a01:264::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a01:265::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a01:266::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a01:267::/32 | SI-T2-NETWORK | RIPE | ALLOCATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(19 of 19)
RPKI-inferred operator
T-2, d.o.o.
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
DUMY-RIPE
DUMY-RIPE
MNT-T-2