MEGACABLE NETWORK SAC
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 26 blocks across 2 clusters |
| Cluster ID | 204420776 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| 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 |
|---|---|---|---|---|
| 201.218.146.0/24 | AS274912 | BGP | ANNOUNCED | ● medium |
| 206.62.104.0/24 | AS274912 | BGP | ANNOUNCED | ● medium |
| 206.62.105.0/24 | AS274912 | BGP | ANNOUNCED | ● medium |
| 2803:3e30::/32 | AS274912 | BGP | ANNOUNCED | ● medium |
| 2803:b0e0:9989::/48 | MEGACABLE NETWORK SAC | BGP | ANNOUNCED | ● medium |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (5)
These blocks are registered to MEGACABLE NETWORK SAC but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2803:3e30::/32 /32 | authorized for AS274912 — AS274912 |
| 2803:b0e0:9989::/48 /48 | authorized for AS269862 — AS269862 |
| 201.218.146.0/24 /24 | authorized for AS269862 — AS269862 |
| 206.62.104.0/24 /24 | authorized for AS274912 — AS274912 |
| 206.62.105.0/24 /24 | authorized for AS274912 — AS274912 |
NIC Handles
AS274912