Equinix as15830
AS15830 · Equinix Internet Access (EIA), Equinix Connect (EC)
Equinix, Inc.
Tools: Where can I peer with Equinix as15830? · Where should Equinix as15830 peer next? · Compare Equinix as15830 with another network
This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report
PeeringDB fix list Printable page · CSV
12 things to fix in Equinix as15830's PeeringDB record, from what its exchanges publish: 3 to add, 6 to correct, 1 to check, 2 at exchanges that look shut down. As of 2026-11-19 12:40 UTC.
Make the changes on Equinix as15830'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 (3)
On the exchange's own member list, but not in Equinix as15830's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.69.119.218 IPv6 2001:7f8:d:fb::218 Speed Not published RS peer Yes -
IPv4 194.68.123.218 IPv6 2001:7f8:d:ff::218 Speed Not published RS peer Yes -
IPv4 195.245.240.218 IPv6 2001:7f8:d:fc::218 Speed Not published RS peer Yes
Correct these entries (6)
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 Port speed differs 2 × 20G 2 × 100G - In the entry with IPv4 185.1.210.53: set Speed to 100000 (100G) (now 20000).
- In the entry with IPv4 185.1.210.8: set Speed to 100000 (100G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 2 × 20G 2 × 100G - In the entry with IPv4 185.1.208.225: set Speed to 100000 (100G) (now 20000).
- In the entry with IPv4 185.1.208.4: set Speed to 100000 (100G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 20G + 10G 2 × 20G - In the entry with IPv4 185.6.36.124: set Speed to 20000 (20G) (now 10000).
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 Port speed differs 2 × 100G 2 × 50G - In the entry with IPv4 195.66.224.187: set Speed to 50000 (50G) (now 100000).
- In the entry with IPv4 195.66.224.82: set Speed to 50000 (50G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 20G 100G + 20G - In the entry with IPv4 195.66.244.18: set Speed to 100000 (100G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 2 × 40G - In the entry with IPv4 5.57.80.187: set Speed to 40000 (40G) (now 100000).
- In the entry with IPv4 5.57.80.95: set Speed to 40000 (40G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Equinix as15830 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 192.65.185.242 IPv6 2001:7f8:1c:24a::3dd6:1 Speed 20000 Mbps (20G) IPv4 192.65.185.243 IPv6 2001:7f8:1c:24a::3dd6:2 Speed 20000 Mbps (20G)
Exchanges that look shut down (2)
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 the operator's own networks
IPv4 202.50.242.1 IPv6 2001:def:4000::1:5830:1 Speed 20000 Mbps (20G) IPv4 202.50.242.2 IPv6 2001:def:4000::1:5830:2 Speed 20000 Mbps (20G) -
Only one outside network
IPv4 206.223.115.12 IPv6 2001:504:0:b:0:1:5830:1 Speed 10000 Mbps (10G) IPv4 206.223.115.13 IPv6 2001:504:0:b:0:1:5830:2 Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 77 |
| Nov 18, 2026 | 77 |
| Nov 17, 2026 | 77 |
| Nov 16, 2026 | 77 |
| Nov 15, 2026 | 77 |
| Nov 14, 2026 | 77 |
| Nov 13, 2026 | 77 |
| Nov 12, 2026 | 77 |
| Nov 11, 2026 | 77 |
| Nov 10, 2026 | 77 |
| Nov 9, 2026 | 77 |
| Nov 8, 2026 | 77 |
| Nov 7, 2026 | 77 |
| Nov 6, 2026 | 77 |
| Nov 5, 2026 | 77 |
| Nov 4, 2026 | 77 |
| Nov 3, 2026 | 77 |
| Nov 2, 2026 | 77 |
| Nov 1, 2026 | 77 |
| Oct 31, 2026 | 77 |
| Oct 30, 2026 | 77 |
| Oct 29, 2026 | 77 |
| Oct 28, 2026 | 77 |
| Oct 27, 2026 | 77 |
| Oct 26, 2026 | 77 |
| Oct 25, 2026 | 77 |
| Oct 24, 2026 | 77 |
| Oct 23, 2026 | 77 |
| Oct 22, 2026 | 77 |
| Oct 21, 2026 | 77 |
| Oct 20, 2026 | 77 |
| Oct 19, 2026 | 77 |
| Oct 18, 2026 | 77 |
| Oct 17, 2026 | 77 |
| Oct 16, 2026 | 77 |
| Oct 15, 2026 | 77 |
| Oct 14, 2026 | 77 |
| Oct 13, 2026 | 77 |
| Oct 12, 2026 | 77 |
| Oct 11, 2026 | 77 |
| Oct 10, 2026 | 77 |
| Oct 9, 2026 | 77 |
| Oct 8, 2026 | 77 |
| Oct 7, 2026 | 77 |
| Oct 6, 2026 | 75 |
| Oct 5, 2026 | 75 |
| Oct 4, 2026 | 75 |
| Oct 3, 2026 | 75 |
Map
Where Equinix as15830'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.
| AMS-IX Amsterdam, Netherlands | 2 × 100G | Both | |
| BBIX Tokyo Tokyo, Japan | 2 × 100G | Both | |
| CANIX Montreal Montreal, Canada | 100G | Both | |
| CATNIX Barcelona, Spain | 2 × 10G | Both | |
| CIXP Geneva, Switzerland | 2 × 20G | PeeringDB only | |
| DE-CIX Frankfurt Frankfurt, Germany | 2 × 100G | Both | |
| DE-CIX Hamburg Hamburg, Germany | 2 × 20G | Both Speed differs | |
| DE-CIX Munich Munich, Germany | 2 × 20G | Both Speed differs | |
| Equinix Amsterdam Amsterdam, Netherlands | 2 × 100G | PeeringDB | |
| Equinix Ashburn Ashburn, United States | 2 × 100G | PeeringDB | |
| Equinix Atlanta Atlanta, United States | 2 × 20G | PeeringDB | |
| Equinix Barcelona Barcelona, Spain | 2 × 20G | PeeringDB | |
| Equinix Bogota Bogota, Colombia | 2 × 100G | PeeringDB | |
| Equinix Chicago Chicago, United States | 2 × 100G | PeeringDB | |
| Equinix Dallas Dallas, United States | 2 × 100G | PeeringDB | |
| Equinix Dublin Dublin, Ireland | 2 × 20G | PeeringDB | |
| Equinix Frankfurt Frankfurt, Germany | 2 × 100G | PeeringDB | |
| Equinix Helsinki Helsinki, Finland | 2 × 20G | PeeringDB | |
| Equinix Hong Kong Hong Kong, Hong Kong | 2 × 200G | PeeringDB | |
| Equinix Jakarta Jakarta, Indonesia | 2 × 20G | PeeringDB | |
| Equinix Kuala Lumpurghost Kuala Lumpur, Malaysia | 2 × 20G | PeeringDB | |
| Equinix Lisbon Lisbon, Portugal | 2 × 20G | PeeringDB | |
| Equinix London London, United Kingdom | 2 × 100G | PeeringDB | |
| Equinix Los Angeles Los Angeles, United States | 2 × 20G | PeeringDB | |
| Equinix Madrid Madrid, Spain | 20G | PeeringDB | |
| Equinix Manchester Manchester, United Kingdom | 2 × 20G | PeeringDB | |
| Equinix Melbourne Melbourne, Australia | 2 × 200G | PeeringDB | |
| Equinix Mexico Mexico City, Mexico | 2 × 20G | PeeringDB | |
| Equinix Miami Miami, United States | 2 × 20G | PeeringDB | |
| Equinix Milan Milan, Italy | 2 × 20G | PeeringDB | |
| Equinix Montrealghost Montreal, Canada | 2 × 10G | PeeringDB | |
| Equinix Mumbai Mumbai, India | 2 × 20G | PeeringDB | |
| Equinix New York New York, United States | 2 × 100G | PeeringDB | |
| Equinix Osaka Osaka, Japan | 2 × 20G | PeeringDB | |
| Equinix Paris Paris, France | 2 × 100G | PeeringDB | |
| Equinix Perth Perth, Australia | 2 × 100G | PeeringDB | |
| Equinix Rio de Janeiro Rio de Janeiro, Brazil | 100G | PeeringDB | |
| Equinix San Jose San Jose, United States | 2 × 100G | PeeringDB | |
| Equinix Seattle Seattle, United States | 2 × 20G | PeeringDB | |
| Equinix Seoul Seoul, South Korea | 2 × 20G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 2 × 200G | PeeringDB | |
| Equinix Stockholm Stockholm, Sweden | 2 × 20G | PeeringDB | |
| Equinix Sydney Sydney, Australia | 2 × 200G | PeeringDB | |
| Equinix São Paulo São Paulo, Brazil | 100G | PeeringDB | |
| Equinix Tokyo Tokyo, Japan | 2 × 200G | PeeringDB | |
| Equinix Toronto Toronto, Canada | 2 × 100G | PeeringDB | |
| Equinix Warsaw Warsaw, Poland | 2 × 20G | PeeringDB | |
| Equinix Zurich Zurich, Switzerland | 2 × 20G | PeeringDB | |
| ESpanix Madrid Lower LAN Madrid, Spain | 2 × 100G | PeeringDB | |
| ESpanix Madrid Upper LAN Madrid, Spain | 100G | PeeringDB | |
| FICIX 1 (Espoo) Espoo, Finland | 10G | PeeringDB | |
| FICIX 2 (Helsinki) Helsinki, Finland | 10G | Both | |
| France-IX Paris Paris, France | 2 × 100G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 2 × 10G | Both | |
| INEX LAN1 Dublin, Ireland | 20G + 10G | Both Speed differs | |
| INEX LAN2 Dublin, Ireland | 10G | Both | |
| IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil | 2 × 100G | PeeringDB only | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 2 × 100G | PeeringDB only | |
| JINX Johannesburg, South Africa | 2 × 100G | Both | |
| JPIX TOKYO Tokyo, Japan | 100G | Both | |
| JPNAP Tokyo Tokyo, Japan | 100G | PeeringDB | |
| LINX LON1 London, United Kingdom | 2 × 100G | Both Speed differs | |
| LINX LON2 London, United Kingdom | 2 × 100G | Both | |
| LINX Manchester Manchester, United Kingdom | 2 × 20G | Both Speed differs | |
| LONAP London, United Kingdom | 2 × 100G | Both Speed differs | |
| MIX-IT Milan, Italy | 2 × 100G | Both | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 10G | Both | |
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | Not in PeeringDB | ||
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | Not in PeeringDB | ||
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 2 × 100G | Both | |
| PIT - Peru - Lima Lima, Peru | 2 × 10G | PeeringDB | |
| PIT Santiago - PIT Chile Santiago, Chile | 2 × 10G | PeeringDB | |
| STHIX - Stockholm Stockholm, Sweden | 2 × 10G | PeeringDB | |
| SwissIX Zurich, Switzerland | 10G | Both | |
| TorIX Toronto, Canada | 2 × 20G | PeeringDB | |
| YYCIX Calgary, Canada | 2 × 100G | Both |
Equinix as15830 lists no facilities in PeeringDB.
Recent changes Search them
- Nov 6, 2026 [PDB] AS15830 Equinix as15830 no longer in PeeringDB at CATNIX (still on its IX-F list)
- Oct 5, 2026 [PDB] AS15830 Equinix as15830 now in PeeringDB at JINX