Cato Networks
AS13150
CATO NETWORKS LTD
Tools: Where can I peer with Cato Networks? · Where should Cato Networks peer next? · Compare Cato Networks with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
38 things to fix in Cato Networks's PeeringDB record, from what its exchanges publish: 4 to add, 33 to correct, 1 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.
Make the changes on Cato Networks's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (4)
On the exchange's own member list, but not in Cato Networks's PeeringDB record. Add one entry per connection with these values.
-
IPv4 123.108.9.184 IPv6 2001:7fa:2:5::1b8 Speed 1000 Mbps (1G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 5.57.82.74 IPv6 – Speed 5000 Mbps (5G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 195.69.119.113 IPv6 2001:7f8:d:fb::113 Speed Not published RS peer Yes -
IPv4 195.245.240.113 IPv6 2001:7f8:d:fc::113 Speed Not published RS peer Yes
Correct these entries (33)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:11:6:0:335e:0:1 - In the entry with IPv4 43.243.21.117: set IPv6 to 2001:7fa:11:6:0:335e:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:1::a501:3150:1 - In the entry with IPv4 80.249.210.159: set IPv6 to 2001:7f8:1::a501:3150:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:df5:b881::157 - In the entry with IPv4 203.159.68.157: set IPv6 to 2001:df5:b881::157 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:26::a501:3150:1 - In the entry with IPv4 194.53.172.85: set IPv6 to 2001:7f8:26::a501:3150:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:504:2d::18:10 - In the entry with IPv4 198.179.18.10: set IPv6 to 2001:504:2d::18:10 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2400:d180:68::60 - In the entry with IPv4 103.228.174.60: set IPv6 to 2400:d180:68::60 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8::335e:0:1 2001:7f8::335e:0:2 - In the entry with IPv4 80.81.197.55: set IPv6 to 2001:7f8::335e:0:1 (now empty).
- In the entry with IPv4 80.81.197.82: set IPv6 to 2001:7f8::335e:0:2 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d5::335e:0:1 - In the entry with IPv4 185.1.131.67: set IPv6 to 2001:7f8:d5::335e:0:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2401:7500:fff6::5f Port speed differs 5G 10G - In the entry with IPv4 103.27.170.248: set IPv6 to 2401:7500:fff6::5f (now empty); set Speed to 10000 (10G) (now 5000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:44::335e:0:1 - In the entry with IPv4 185.1.208.14: set IPv6 to 2001:7f8:44::335e:0:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:504:116::335e:0:1 - In the entry with IPv4 149.112.27.42: set IPv6 to 2001:504:116::335e:0:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:504:40:108::1:114 - In the entry with IPv4 206.41.108.114: set IPv6 to 2001:504:40:108::1:114 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:64:225:0:1:3150:1 - In the entry with IPv4 86.104.125.167: set IPv6 to 2001:7f8:64:225:0:1:3150:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:11:1:0:335e:0:1 - In the entry with IPv4 218.100.78.29: set IPv6 to 2001:7fa:11:1:0:335e:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:11::335e:0:1 - In the entry with IPv4 27.106.192.4: set IPv6 to 2001:7fa:11::335e:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7fa:11:4:0:335e:0:1 - In the entry with IPv4 218.100.52.63: set IPv6 to 2001:7fa:11:4:0:335e:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:43f8:bb1::177 - In the entry with IPv4 196.216.148.177: set IPv6 to 2001:43f8:bb1::177 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:43f8:60:1::174 - In the entry with IPv4 196.223.21.174: set IPv6 to 2001:43f8:60:1::174 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4::335e:1 2001:7f8:4::335e:2 Port speed differs 100G + 50G 2 × 100G - In the entry with IPv4 195.66.227.252: set IPv6 to 2001:7f8:4::335e:1 (now empty).
- In the entry with IPv4 195.66.228.135: set IPv6 to 2001:7f8:4::335e:2 (now empty); set Speed to 100000 (100G) (now 50000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4:2::335e:1 - In the entry with IPv4 195.66.244.84: set IPv6 to 2001:7f8:4:2::335e:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:dea:0:20::40 - In the entry with IPv4 103.26.70.64: set IPv6 to 2001:dea:0:20::40 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:504:27::335e:0:1 - In the entry with IPv4 206.108.255.9: set IPv6 to 2001:504:27::335e:0:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:10::1:3150 - In the entry with IPv4 193.201.29.31: set IPv6 to 2001:7f8:10::1:3150 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:43f8:6d1::71:161 - In the entry with IPv4 196.60.71.161: set IPv6 to 2001:43f8:6d1::71:161 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:43f8:6d0::11:8 - In the entry with IPv4 196.60.11.8: set IPv6 to 2001:43f8:6d0::11:8 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:202::113 - In the entry with IPv4 212.237.192.113: set IPv6 to 2001:7f8:d:202::113 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:203::113 - In the entry with IPv4 212.237.193.113: set IPv6 to 2001:7f8:d:203::113 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:fe::113 - In the entry with IPv4 194.68.128.113: set IPv6 to 2001:7f8:d:fe::113 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:d:ff::113 - In the entry with IPv4 194.68.123.113: set IPv6 to 2001:7f8:d:ff::113 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:14::1b:1 2001:7f8:14::1b:2 - In the entry with IPv4 91.210.17.32: set IPv6 to 2001:7f8:14::1b:1 (now empty).
- In the entry with IPv4 91.210.17.41: set IPv6 to 2001:7f8:14::1b:2 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2620:124:2000::25 - In the entry with IPv4 198.32.195.25: set IPv6 to 2620:124:2000::25 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:de8:12:100::131 - In the entry with IPv4 103.16.102.131: set IPv6 to 2001:de8:12:100::131 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:24::111 - In the entry with IPv4 91.206.53.17: set IPv6 to 2001:7f8:24::111 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 206.223.115.1 IPv6 – Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 86 |
| Nov 18, 2026 | 86 |
| Nov 17, 2026 | 86 |
| Nov 16, 2026 | 86 |
| Nov 15, 2026 | 86 |
| Nov 14, 2026 | 86 |
| Nov 13, 2026 | 86 |
| Nov 12, 2026 | 86 |
| Nov 11, 2026 | 86 |
| Nov 10, 2026 | 86 |
| Nov 9, 2026 | 86 |
| Nov 8, 2026 | 86 |
| Nov 7, 2026 | 86 |
| Nov 6, 2026 | 86 |
| Nov 5, 2026 | 86 |
| Nov 4, 2026 | 86 |
| Nov 3, 2026 | 86 |
| Nov 2, 2026 | 86 |
| Nov 1, 2026 | 86 |
| Oct 31, 2026 | 86 |
| Oct 30, 2026 | 86 |
| Oct 29, 2026 | 86 |
| Oct 28, 2026 | 86 |
| Oct 27, 2026 | 86 |
| Oct 26, 2026 | 86 |
| Oct 25, 2026 | 86 |
| Oct 24, 2026 | 86 |
| Oct 23, 2026 | 86 |
| Oct 22, 2026 | 86 |
| Oct 21, 2026 | 86 |
| Oct 20, 2026 | 86 |
| Oct 19, 2026 | 86 |
| Oct 18, 2026 | 86 |
| Oct 17, 2026 | 86 |
| Oct 16, 2026 | 86 |
| Oct 15, 2026 | 86 |
| Oct 14, 2026 | 86 |
| Oct 13, 2026 | 86 |
| Oct 12, 2026 | 86 |
| Oct 11, 2026 | 86 |
| Oct 10, 2026 | 86 |
| Oct 9, 2026 | 86 |
| Oct 8, 2026 | 86 |
| Oct 7, 2026 | 86 |
| Oct 6, 2026 | 84 |
| Oct 5, 2026 | 84 |
| Oct 4, 2026 | 84 |
| Oct 3, 2026 | 84 |
Map
Where Cato Networks's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| AKL-IX (Auckland NZ) Auckland, New Zealand | 10G | Both IPv6 not in PeeringDB | |
| AMS-IX Amsterdam, Netherlands | 100G | Both IPv6 not in PeeringDB | |
| Any2Denver Denver, United States | 10G | PeeringDB | |
| Any2West Los Angeles and Silicon Valley, United States | 2 × 100G | PeeringDB | |
| BBIX Manila Manila, Philippines | 10G | PeeringDB | |
| BBIX Osaka Osaka, Japan | 100G | PeeringDB | |
| BBIX Tokyo Tokyo, Japan | 3 × 100G | Both | |
| BKNIX (Thailand) Bangkok, Thailand | 10G | Both IPv6 not in PeeringDB | |
| BNIX Brussels, Belgium | 10G | Both IPv6 not in PeeringDB | |
| Boston Internet Exchange Boston, Massachusetts, United States | 10G | PeeringDB | |
| CANIX Montreal Montreal, Canada | 10G | Both IPv6 not in PeeringDB | |
| CRIX San Jose, Costa Rica | 1G | Both | |
| DE-CIX Chennai Chennai, India | 10G | Both IPv6 not in PeeringDB | |
| DE-CIX Frankfurt Frankfurt, Germany | 2 × 100G | Both IPv6 not in PeeringDB | |
| DE-CIX Lisbon Lisbon, Portugal | 100G | Both IPv6 not in PeeringDB | |
| DE-CIX Mumbai Mumbai, India | 5G | Both IPv6 not in PeeringDBSpeed differs | |
| DE-CIX Munich Munich, Germany | 10G | Both IPv6 not in PeeringDB | |
| DE-CIX Phoenix Phoenix, United States | 10G | Both IPv6 not in PeeringDB | |
| DET-iX Detroit, United States | 100G | PeeringDB | |
| Digital Realty Atlanta Atlanta, United States | 100G | PeeringDB | |
| DRF IX Honolulu, United States | 10G | PeeringDB | |
| Equinix Ashburn Ashburn, United States | 2 × 100G | PeeringDB | |
| Equinix Bogota Bogota, Colombia | 10G | PeeringDB | |
| Equinix Chicago Chicago, United States | 100G | PeeringDB | |
| Equinix Dallas Dallas, United States | 100G | PeeringDB | |
| Equinix Helsinki Helsinki, Finland | 10G | PeeringDB | |
| Equinix Hong Kong Hong Kong, Hong Kong | 10G | PeeringDB | |
| Equinix Miami Miami, United States | 10G | PeeringDB | |
| Equinix Montrealghost Montreal, Canada | 10G | PeeringDB | |
| Equinix New York New York, United States | 100G | PeeringDB | |
| Equinix Sydney Sydney, Australia | 10G | PeeringDB | |
| Equinix Warsaw Warsaw, Poland | 10G | PeeringDB | |
| ESpanix Madrid Lower LAN Madrid, Spain | 10G | PeeringDB | |
| Extreme IX Delhi Delhi, India | 10G | PeeringDB | |
| FL-IX Miami, United States | 100G | Both IPv6 not in PeeringDB | |
| France-IX Marseille Marseille, France | 10G | PeeringDB | |
| France-IX Paris Paris, France | 2 × 100G | PeeringDB | |
| GetaFIX Manila Manila, Philippines | 10G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 10G | Both | |
| IIX-Jakarta Jakarta, Indonesia | 1G | Not in PeeringDB | |
| INEX LAN1 Dublin, Ireland | 10G | Both | |
| InterLAN-IX Bucharest, Romania | 10G | Both IPv6 not in PeeringDB | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 10G | Both IPv6 not in PeeringDB | |
| IX Australia Perth (WA-IX) Perth, Australia | 10G | Both IPv6 not in PeeringDB | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 10G | Both IPv6 not in PeeringDB | |
| IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil | 10G | PeeringDB only | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 20G | PeeringDB only | |
| IXPN Lagos Lagos, Nigeria | 10G | Both IPv6 not in PeeringDB | |
| JKT-IX Jakarta, Indonesia | 10G | Both | |
| JPIX HOKKAIDO Sapporo, Japan | 10G | PeeringDB | |
| JPIX OSAKA Osaka, Japan | 2 × 100G | PeeringDB | |
| JPIX TOKYO Tokyo, Japan | 4 × 100G | Both | |
| JPNAP Osaka Osaka, Japan | 100G | PeeringDB | |
| JPNAP Tokyo Tokyo, Japan | 100G | PeeringDB | |
| KINX Seoul, South Korea | 10G | PeeringDB | |
| KIXP - Nairobi Nairobi, Kenya | 10G | Both IPv6 not in PeeringDB | |
| LINX LON1 London, United Kingdom | 100G + 50G | Both IPv6 not in PeeringDBSpeed differs | |
| LINX Manchester Manchester, United Kingdom | 100G | Both IPv6 not in PeeringDB | |
| LONAP London, United Kingdom | 5G | Not in PeeringDB | |
| MegaIX Brisbane Brisbane, Australia | 10G | Both IPv6 not in PeeringDB | |
| MICE Minneapolis, MN, United States | 10G | Both IPv6 not in PeeringDB | |
| MIX-IT Milan, Italy | 100G | Both | |
| MyIX Kuala Lumpur, Malaysia | 10G | Both | |
| Namex Rome Rome, Italy | 10G | Both IPv6 not in PeeringDB | |
| NAPAfrica IX Cape Town Cape Town, South Africa | 100G | Both IPv6 not in PeeringDB | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 100G | Both IPv6 not in PeeringDB | |
| Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark | 10G | Both IPv6 not in PeeringDB | |
| Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark | 10G | Both IPv6 not in PeeringDB | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 10G | Both IPv6 not in PeeringDB | |
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 10G | Both IPv6 not in PeeringDB | |
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| NIX.CZ Prague, Czechia | 2 × 10G | Both IPv6 not in PeeringDB | |
| NIX1 Oslo, Norway | 10G | PeeringDB | |
| NWAX Portland, United States | 10G | Both IPv6 not in PeeringDB | |
| Ohio IX Columbus, United States | 10G | Both | |
| PIT - Colombia - Bogota Bogota, Colombia | 10G | PeeringDB | |
| PIT - Peru - Lima Lima, Peru | 10G | PeeringDB | |
| PIT MX Queretaro, Mexico | 10G | PeeringDB | |
| PIT Santiago - PIT Chile Santiago, Chile | 10G | PeeringDB | |
| SGIX Singapore, Singapore | 10G | Both IPv6 not in PeeringDB | |
| SIX Seattle Seattle, United States | 100G | Both | |
| SwissIX Zurich, Switzerland | 20G | Both IPv6 not in PeeringDB | |
| TorIX Toronto, Canada | 10G | PeeringDB | |
| TPIX-TW Taipei/Taiwan, Taiwan | 10G | PeeringDB | |
| YYCIX Calgary, Canada | 10G | Both |
These exchanges have a switch in a facility where Cato Networks lists itself in PeeringDB, but don't have Cato Networks as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| GNM-IXAmsterdam, Netherlands | 741 | |
| NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 672 | |
| FogIXPAvers, Switzerland | 532 | |
| Equinix SingaporeSingapore, Singapore | 473 | |
| KleyReXFrankfurt, Germany | 471 | |
| Frys-IXFryslân, Netherlands | 338 | |
| LINX LON2London, United Kingdom | 315 | |
| 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland | 283 | |
| DE-CIX New YorkNew York, United States | 281 | |
| MegaIX SydneySydney, Australia | 267 | |
| INTERIXAmsterdam, Netherlands | 262 | |
| ERA-IX AmsterdamAmsterdam, Netherlands | 244 | |
| Equinix ParisParis, France | 239 | |
| EdgeIX - SydneySydney, Australia | 230 | |
| DE-CIX MadridMadrid, Spain | 224 | |
| KCIXKansas City, United States | 216 | |
| JINXJohannesburg, South Africa | 215 | |
| Peering.czPrague, Bratislava, Vienna, Frankfurt, Czechia | 207 | |
| LOCIX FRANKFURTFrankfurt am Main, Germany | 205 | |
| NetIXSofia, Bulgaria | 204 | |
| THINX WarsawWarsaw, Poland | 194 | |
| NYIIX New YorkNew York, United States | 186 | |
| BBIX SingaporeSingapore, Singapore | 169 | |
| Equinix São PauloSão Paulo, Brazil | 163 | |
| nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France | 160 | |
| MegaIX MelbourneMelbourne, Australia | 152 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| STUIXTaipei City, Taiwan | 131 | |
| Equinix TokyoTokyo, Japan | 127 | |
| BIXBudapest, Hungary | 122 | |
| CIX-ATLAtlanta, United States | 121 | |
| TOP-IXTurin, Italy | 118 | |
| MegaIX FrankfurtFrankfurt, Germany | 114 | |
| DE-CIX MarseilleMarseille, France | 112 | |
| LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands | 105 | |
| BBIX Hong KongHong Kong, Hong Kong | 104 | |
| SFMIXSan Francisco, United States | 100 | |
| IX-DenverDenver, United States | 96 | |
| MegaIX AucklandAuckland, New Zealand | 93 | |
| DE-CIX ChicagoChicago, United States | 86 | |
| ERA-IX FrankfurtFrankfurt, Germany | 85 | |
| STHIX - StockholmStockholm, Sweden | 84 | |
| SONIX StockholmStockholm, Sweden | 81 | |
| NVIXAshburn, United States | 78 | |
| B-IXSofia, Bulgaria | 77 | |
| ChIXChicago, United States | 73 | |
| EdgeIX - MelbourneMelbourne, Australia | 73 | |
| INEX LAN2Dublin, Ireland | 71 | |
| LINX NairobiNairobi, Kenya | 70 | |
| EdgeIX - PerthPerth, Australia | 69 | |
| SIX Seattle (Jumbo)Seattle, United States | 69 | |
| NIX.SKBratislava, Slovakia | 68 | |
| FogIXP FrankfurtFrankfurt, Germany | 67 | |
| THAILAND IX (TH-IX)Bangkok, Thailand | 67 | |
| CHIX-CHFrauenfeld, Switzerland | 66 | |
| MegaIX PerthPerth, Australia | 65 | |
| Transhybrid IX NetworkJakarta, Indonesia | 63 | |
| 1-NL FREEAmsterdam, Netherlands | 60 | |
| DE-CIX Sao PauloSao Paulo, Brazil | 58 | |
| HopusParis, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France | 58 | |
| SOLIX MTU1500Stockholm, Sweden | 58 | |
| ESpanix Madrid Upper LANMadrid, Spain | 57 | |
| LINX NoVAAshburn, Reston, Manassas, United States | 57 | |
| Equinix MelbourneMelbourne, Australia | 55 | |
| Equinix AmsterdamAmsterdam, Netherlands | 51 | |
| EdgeIX - AucklandAuckland, New Zealand | 50 | |
| MegaIX AshburnAshburn, United States | 49 | |
| PyramIXCairo, Egypt | 48 | |
| CXIX - Great LakesNewYork, United States | 46 | |
| MegaIX SingaporeSingapore, Singapore | 46 | |
| DE-CIX Kuala LumpurKuala Lumpur, Malaysia | 45 | |
| ixFabric - New YorkNew York, United States | 44 | |
| RoNIXBucharest, Romania | 43 | |
| Equinix ZurichZurich, Switzerland | 40 | |
| Equinix SeattleSeattle, United States | 36 | |
| Equinix MilanMilan, Italy | 35 | |
| MegaIX MunichMunich, Germany | 35 | |
| CIX-NoVAAshburn, Reston, Washington DC, United States | 34 | |
| BelgiumIXBrussels, Ghent, Leuven, Antwerp, Hasselt, Belgium | 32 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| MegaIX DallasDallas, United States | 30 | |
| Balcan-IXBucharest, Romania | 29 | |
| DIXCopenhagen, Denmark | 29 | |
| APEAuckland, New Zealand | 28 | |
| DE-CIX MexicoMexico City, Mexico | 28 | |
| 1-DE FREEFrankfurt, Germany | 27 | |
| Equinix PerthPerth, Australia | 27 | |
| JumboIX PeruLima, Peru | 27 | |
| MegaIX Los AngelesLos Angeles, United States | 27 | |
| Equinix OsakaOsaka, Japan | 26 | |
| Community-IXBerlin, Frankfurt, Germany | 25 | |
| nine - six in ParisParis, France | 24 | |
| IL-IXMultiple, Israel | 23 | |
| FOXTainan, Taiwan | 22 | |
| MegaIX New YorkNew York, United States | 22 | |
| TRUE-IXBangkok, Thailand | 22 | |
| Chile IX by PIT.netSantiago, Chile | 20 | |
| IAIXHong Kong, Hong Kong | 20 | |
| OpenCarrier OCIXDuesseldorf, Germany | 20 | |
| STHIX - CopenhagenCopenhagen, Denmark | 20 | |
| Equinix ManchesterManchester, United Kingdom | 19 | |
| Vitro Internet ExchangePasig, Philippines | 19 | |
| CSL Thai-IX BangkokBangkok, Thailand | 18 | |
| SOLIX MTU4470Stockholm, Sweden | 18 | |
| AMS-IX BangkokBangkok, Thailand | 17 | |
| CSL Thai-IX SingaporeBangkok, Thailand | 16 | |
| MegaIX TorontoToronto, Canada | 16 | |
| DACS-IX EastWashington DC, United States | 15 | |
| DE-CIX MalaysiaKuala Lumpur, Cyberjaya, Johor Bahru, Malaysia | 15 | |
| Equinix DublinDublin, Ireland | 15 | |
| GNM-IX SGSingapore, Singapore | 15 | |
| IIX IsraelPetach Tikva, Israel | 15 | |
| MegaIX SeattleSeattle, United States | 15 | |
| AMS-IX SingaporeSingapore, Singapore | 14 | |
| MAINPORT Peer-ExchangeFrankfurt am Main, Germany | 14 | |
| CSL Thai-IX MalaysiaBangkok, Thailand | 13 | |
| MegaIX ChicagoChicago, United States | 13 | |
| DE-CIX HoustonHouston, United States | 12 | |
| Equinix MadridMadrid, Spain | 12 | |
| PhIXManila, Philippines | 12 | |
| AKIXZurich, Switzerland | 11 | |
| DE-CIX CopenhagenCopenhagen, Denmark | 11 | |
| KeFF-IXStockholm, Gothenburg, Malmö, Amsterdam, Sweden | 11 | |
| MegaIX AtlantaAtlanta, United States | 11 | |
| CANIX TorontoToronto, Canada | 10 | |
| MegaIX MiamiMiami, United States | 10 | |
| Chicago Open PipesChicago, United States | 9 | |
| NIX.CZ FENIXPrague, Czechia | 8 | |
| City-IX FrankfurtFrankfurt, Germany | 7 | |
| Impart IXSingapore, Singapore | 7 | |
| IXP AndeSpark - PerúLima - Huancayo - Huanuco, Peru | 7 | |
| MegaIX CharlotteCharlotte, United States | 7 | |
| MegaIX DenverDenver, United States | 7 | |
| RapidIX LON1London, United Kingdom | 7 | |
| 1-CZ FREEPrague, Czechia | 6 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| FD-IX - OhioCleveland, Ohio, United States | 5 | |
| MegaIX OsakaOsaka, Japan | 5 | |
| PIT - LATAM InterconnectMiami, United States | 5 | |
| STACIXFrankfurt, Germany | 5 | |
| TMW-iXFrankfurt am Main, Germany | 5 | |
| FD-IX - ChicagoChicago, United States | 4 | |
| GNM-IX USNew York, United States | 4 | |
| JINX VoiceJohannesburg, South Africa | 4 | |
| MegaIX Las VegasLas Vegas, United States | 4 | |
| TievoluIXFrankfurt, Germany | 4 | |
| PIT Lima - PIT ChileLima, Peru | 3 | |
| SYMPHONY THAI - IX BANGKOK - 1Bangkok, Thailand | 3 | |
| Any2FloridaMiami/Orlando, United States | 2 | |
| ixFabricGlobal, Australia | 2 |
Facilities (61)
The buildings Cato Networks lists in PeeringDB, and how many of the exchanges in each it's on.
Recent changes Search them
- Nov 5, 2026 [PDB] AS13150 Cato Networks now in PeeringDB at MegaIX Brisbane