RouteViews
AS6447
Tools: Where can I peer with RouteViews? · Where should RouteViews peer next? · Compare RouteViews with another network
This network elsewhere: its registry history on RIR Tracker
PeeringDB fix list Printable page · CSV
21 things to fix in RouteViews's PeeringDB record, from what its exchanges publish: 1 to add, 15 to correct, 5 to check. As of 2026-11-19 12:40 UTC.
Make the changes on RouteViews'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 (1)
On the exchange's own member list, but not in RouteViews's PeeringDB record. Add one entry per connection with these values.
-
IPv4 206.72.210.169 IPv6 2001:504:13::210:169 Speed Not published RS peer Not published
Correct these entries (15)
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 10G 100M - In the entry with IPv4 80.249.213.84: set Speed to 100 (100M) (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 10G 1G - In the entry with IPv4 203.159.68.20: set Speed to 1000 (1G) (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 1G 10G - In the entry with IPv4 80.81.192.19: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 206.82.105.7: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 1M - In the entry with IPv4 218.100.54.2: set Speed to 1 (1M) (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 10G 1M - In the entry with IPv4 218.100.76.18: set Speed to 1 (1M) (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 10G 1M - In the entry with IPv4 218.100.54.130: set Speed to 1 (1M) (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 10G 1M - In the entry with IPv4 218.100.78.37: set Speed to 1 (1M) (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 10G 1M - In the entry with IPv4 27.106.192.97: set Speed to 1 (1M) (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 10G 200G - In the entry with IPv4 218.100.52.52: set Speed to 200000 (200G) (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 IPv4 address in PeeringDB, not in the export 196.223.21.54 none IPv6 address in PeeringDB, not in the export 2001:43f8:60:1::54 none Port speed differs 10G 1G - The entry with IPv4 196.223.21.54, IPv6 2001:43f8:60:1::54 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 195.66.225.222: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 195.66.237.222: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 206.197.187.28: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 10G 200G - In the entry with IPv4 185.1.8.105: set Speed to 200000 (200G) (now 10000).
Check these entries (5)
In PeeringDB, but on none of the exchange's own lists. If RouteViews has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 196.201.2.119 IPv6 – Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 194.68.128.32 IPv6 2001:7f8:d:fe::32 Speed 10000 Mbps (10G) -
IPv4 195.69.119.32 IPv6 2001:7f8:d:fb::32 Speed 10000 Mbps (10G) -
IPv4 194.68.123.32 IPv6 2001:7f8:d:ff::32 Speed 10000 Mbps (10G) -
IPv4 195.245.240.32 IPv6 2001:7f8:d:fc::32 Speed 10000 Mbps (10G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 66 |
| Nov 18, 2026 | 66 |
| Nov 17, 2026 | 66 |
| Nov 16, 2026 | 66 |
| Nov 15, 2026 | 66 |
| Nov 14, 2026 | 66 |
| Nov 13, 2026 | 66 |
| Nov 12, 2026 | 66 |
| Nov 11, 2026 | 66 |
| Nov 10, 2026 | 66 |
| Nov 9, 2026 | 66 |
| Nov 8, 2026 | 66 |
| Nov 7, 2026 | 66 |
| Nov 6, 2026 | 66 |
| Nov 5, 2026 | 66 |
| Nov 4, 2026 | 66 |
| Nov 3, 2026 | 66 |
| Nov 2, 2026 | 66 |
| Nov 1, 2026 | 66 |
| Oct 31, 2026 | 66 |
| Oct 30, 2026 | 66 |
| Oct 29, 2026 | 66 |
| Oct 28, 2026 | 66 |
| Oct 27, 2026 | 66 |
| Oct 26, 2026 | 66 |
| Oct 25, 2026 | 66 |
| Oct 24, 2026 | 66 |
| Oct 23, 2026 | 66 |
| Oct 22, 2026 | 63 |
| Oct 21, 2026 | 63 |
| Oct 20, 2026 | 63 |
| Oct 19, 2026 | 63 |
| Oct 18, 2026 | 63 |
| Oct 17, 2026 | 63 |
| Oct 16, 2026 | 63 |
| Oct 15, 2026 | 63 |
| Oct 14, 2026 | 63 |
| Oct 13, 2026 | 63 |
| Oct 12, 2026 | 63 |
| Oct 11, 2026 | 63 |
| Oct 10, 2026 | 63 |
| Oct 9, 2026 | 63 |
| Oct 8, 2026 | 63 |
| Oct 7, 2026 | 63 |
| Oct 6, 2026 | 62 |
| Oct 5, 2026 | 62 |
| Oct 4, 2026 | 62 |
| Oct 3, 2026 | 62 |
Map
Where RouteViews'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 | 10G | Both Speed differs | |
| Any2West Los Angeles and Silicon Valley, United States | Website list only | ||
| BDIX Dhaka, Bangladesh | 1G | PeeringDB | |
| BKNIX (Thailand) Bangkok, Thailand | 10G | Both Speed differs | |
| CIX-ATL Atlanta, United States | 100G | Both | |
| CRIX San Jose, Costa Rica | 10G | Both | |
| DE-CIX ASEAN Singapore, Singapore | 1G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 1G | Both Speed differs | |
| DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia | 1G | Both | |
| DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia | 1G | Both | |
| DE-CIX New York New York, United States | 10G | Both Speed differs | |
| Digital Realty Atlanta Atlanta, United States | 10G | PeeringDB | |
| DIX-IE Tokyo, Japan | 100M | PeeringDB | |
| DRF IX Honolulu, United States | 10G | PeeringDB | |
| Equinix Ashburn Ashburn, United States | 1G | PeeringDB | |
| Equinix Chicago Chicago, United States | 10G | PeeringDB | |
| Equinix Palo Alto Palo Alto, United States | 10G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 1G | PeeringDB | |
| Equinix Sydney Sydney, Australia | 1G | PeeringDB | |
| FD-IX - Indianapolis Indianapolis, Indiana, United States | 10G | Both | |
| FL-IX Miami, United States | 100G | Both | |
| France-IX AURA Lyon and Grenoble, France | 20G | PeeringDB | |
| France-IX Marseille Marseille, France | 20G | PeeringDB | |
| France-IX Paris Paris, France | 20G | PeeringDB | |
| GetaFIX Cebu Cebu, Philippines | 1G | PeeringDB | |
| GetaFIX Davao Davao, Philippines | 1G | PeeringDB | |
| GetaFIX Manila Manila, Philippines | 1G | PeeringDB | |
| GIXA Accra, Ghana | 1G | PeeringDB only | |
| GOREX Piti, Guam | 1G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 10G | Both | |
| IIX-Jakarta Jakarta, Indonesia | 10G | Both | |
| InterLAN-IX Bucharest, Romania | 10G | Both | |
| IRAQ-IXP Baghdad, Iraq | 1G | PeeringDB | |
| IX Australia Adelaide (SA-IX) Adelaide, Australia | 10G | Both Speed differs | |
| IX Australia Brisbane (QLD-IX) Brisbane, Australia | 10G | Both Speed differs | |
| IX Australia Canberra (ACT-IX) Canberra, Australia | 10G | Both Speed differs | |
| IX Australia Melbourne (VIC-IX) Melbourne, Australia | 10G | Both Speed differs | |
| IX Australia Perth (WA-IX) Perth, Australia | 10G | Both Speed differs | |
| IX Australia Sydney (NSW-IX) Sydney, Australia | 10G | Both Speed differs | |
| IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil | 1G | Both | |
| IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil | 1G | Both | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 2 × 1G | Both | |
| IXPN Lagos Lagos, Nigeria | 1G | Both | |
| KINX Seoul, South Korea | 1G | PeeringDB | |
| KIXP - Nairobi Nairobi, Kenya | 10G | Both IPv4 not in exportIPv6 not in exportSpeed differs | |
| LINX LON1 London, United Kingdom | 1G | Both Speed differs | |
| LINX LON2 London, United Kingdom | 1G | Both Speed differs | |
| LOCIX FRANKFURT Frankfurt am Main, Germany | 10G | PeeringDB | |
| MARIIX Mangilao, Guam | 1G | Both | |
| Namex Rome Rome, Italy | 1G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 10G | Both | |
| Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark | 10G | Both | |
| Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark | 10G | Both | |
| Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden | 10G | PeeringDB only | |
| Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden | 10G | PeeringDB only | |
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 10G | PeeringDB only | |
| Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden | 10G | PeeringDB only | |
| NWAX Portland, United States | 1G | Both | |
| Pacific Wave West Coast, United States | 6 × 10G | PeeringDB | |
| PhOpenIX-Manila Manila, Philippines | 1G | PeeringDB | |
| PIT - Peru - Lima Lima, Peru | 1G | PeeringDB | |
| PIT MX Queretaro, Mexico | 10G | PeeringDB | |
| PIT Santiago - PIT Chile Santiago, Chile | 10G | PeeringDB | |
| SFMIX San Francisco, United States | 1G | Both Speed differs | |
| SOX Serbia Belgrade/Serbia, Serbia | 1G | PeeringDB | |
| UAE-IX Dubai, United Arab Emirates | 10G | Both Speed differs |
RouteViews lists no facilities in PeeringDB.
Recent changes Search them
- Oct 23, 2026 [PDB] AS6447 RouteViews added to France-IX AURA
- Oct 23, 2026 [PDB] AS6447 RouteViews added to France-IX Paris
- Oct 23, 2026 [PDB] AS6447 RouteViews added to France-IX Marseille