MegaIX
Aggregated across every cluster whose name starts with "MegaIX" — a single company can be split across many separate clusters (per-datacenter, per-country, or per-subsidiary naming), so this view sums the true total rather than understating it with a single cluster's count.
140
Total ranges
15
Matched clusters
Matched clusters
MegaIX Europe Route Servers
MegaIX North America Route Servers
MegaIX Sydney, Perth & Adelaide Route Servers
MegaIX Singapore & Osaka Route Servers
MegaIX Toronto and Montreal Route Servers
MegaIX Brisbane Route Servers
MegaIX Dallas Route Servers
MegaIX Melbourne Route Servers
MegaIX Seattle Route Servers
MegaIX Auckland Route Servers
MegaIX Sofia Route Servers
MegaIX Ashburn Route Servers
MegaIX New York Route Servers
MegaIX Chicago Route Servers
MegaIX Bay Area Route Servers
Ranges (140)
showing 101–140 of 140 — ⬇ export CSV| CIDR | Org name | Cluster | Registry | Status | Confidence |
|---|---|---|---|---|---|
| 2001:ded::1/128 | MegaIX Singapore & Osaka Route Servers | MegaIX Singapore & Osaka Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:ded::2/128 | MegaIX Singapore & Osaka Route Servers | MegaIX Singapore & Osaka Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:ded:1::1/128 | MegaIX Singapore & Osaka Route Servers | MegaIX Singapore & Osaka Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2001:ded:1::2/128 | MegaIX Singapore & Osaka Route Servers | MegaIX Singapore & Osaka Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:1::1/128 | MegaIX Toronto and Montreal Route Servers | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:1::2/128 | MegaIX Toronto and Montreal Route Servers | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:2::1/128 | MegaIX New York Route Servers | MegaIX New York Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:2::2/128 | MegaIX New York Route Servers | MegaIX New York Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:3::1/128 | MegaIX Ashburn Route Servers | MegaIX Ashburn Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:3::2/128 | MegaIX Ashburn Route Servers | MegaIX Ashburn Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:4::1/128 | MegaIX Seattle Route Servers | MegaIX Seattle Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:4::2/128 | MegaIX Seattle Route Servers | MegaIX Seattle Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:5::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:5::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:6::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:6::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:7::1/128 | MegaIX Dallas Route Servers | MegaIX Dallas Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:7::2/128 | MegaIX Dallas Route Servers | MegaIX Dallas Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:8::1/128 | MegaIX Toronto and Montreal Route Servers | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:8::2/128 | MegaIX Toronto and Montreal Route Servers | MegaIX Toronto and Montreal Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:9::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:9::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:a::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:a::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:b::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:b::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:c::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:c::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:d::1/128 | MegaIX Chicago Route Servers | MegaIX Chicago Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:d::2/128 | MegaIX Chicago Route Servers | MegaIX Chicago Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:e::1/128 | MegaIX Bay Area Route Servers | MegaIX Bay Area Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:e::2/128 | MegaIX Bay Area Route Servers | MegaIX Bay Area Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:f::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:f::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:10::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:10::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:11::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:11::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:12::1/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:12::2/128 | MegaIX North America Route Servers | MegaIX North America Route Servers | PEERINGDB | ASSIGNED | ● high |
No ranges on this page match your filter.
← Previous
Next →
Uses the REST API.