TRANSIT-CORE
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 208482947 |
| 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 |
|---|---|---|---|---|
| 77.91.255.128/25 | TRANSIT-CORE | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “TRANSIT CORE” — 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.
- TRANSIT-CORE-ACCESS 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.
- IBH-L3CORE-TRANSIT via IBH connect GmbH sub-allocation
- IBH-CORE-TRANSIT1 via IBH connect GmbH sub-allocation
- IBH-CORE-TRANSIT2 via IBH connect GmbH sub-allocation
- Nbg1 Core Transits via noris network AG sub-allocation
- Transit Core 2 via XINON GmbH sub-allocation
- TRANSIT-CORE-ACCESS sub-allocation
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-GUARDIAN