MegaIX Toronto and Montreal Route Servers
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 8 |
| IPv6 | 4 prefixes (largest 2606:a980:0:1::1/128) |
| Cluster ID | 214586437 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-26
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 206.53.168.193/32 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 206.53.168.194/32 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 206.53.203.1/32 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 206.53.203.2/32 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:1::1/128 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:1::2/128 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:8::1/128 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:8::2/128 | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (4)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(6 of 8)
No discrepancies found among checked blocks.
NIC Handles
AS395081