Nevalink
AS42668 · Nevalink LTD
Nevalink LTD
Tools: Where can I peer with Nevalink? · Where should Nevalink peer next? · Compare Nevalink with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
2 things to fix in Nevalink's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on Nevalink'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 Nevalink's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (1)
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 2a03:5f80:4::224:54 Port speed differs 40G 200G - In the entry with IPv4 178.18.224.54: set IPv6 to 2a03:5f80:4::224:54 (now empty); set Speed to 200000 (200G) (now 40000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 5 |
| Oct 24, 2026 | 5 |
| Oct 23, 2026 | 5 |
| Oct 22, 2026 | 5 |
| Oct 21, 2026 | 5 |
| Oct 20, 2026 | 5 |
| Oct 19, 2026 | 5 |
| Oct 18, 2026 | 5 |
| Oct 17, 2026 | 5 |
| Oct 16, 2026 | 5 |
| Oct 15, 2026 | 5 |
| Oct 14, 2026 | 5 |
| Oct 13, 2026 | 5 |
| Oct 12, 2026 | 5 |
| Oct 11, 2026 | 5 |
| Oct 10, 2026 | 5 |
| Oct 9, 2026 | 5 |
| Oct 8, 2026 | 5 |
| Oct 7, 2026 | 5 |
| Oct 6, 2026 | 5 |
| Oct 5, 2026 | 5 |
| Oct 4, 2026 | 5 |
| Oct 3, 2026 | 5 |
Map
Where Nevalink'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.
| GNM-IX Amsterdam, Netherlands | 40G | Both IPv6 not in PeeringDBSpeed differs | |
| MSK-IX Moscow Moscow, Russia | Website list only | ||
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 2 × 20G | Both | |
| PITER-IX Helsinki Helsinki, Finland | 40G | PeeringDB | |
| PITER-IX Moscow Moscow, Russia | 40G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 40G | PeeringDB |
These exchanges have a switch in a facility where Nevalink lists itself in PeeringDB, but don't have Nevalink 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.
| Global-IXAmsterdam, Netherlands | 138 | |
| W-IXMoscow, Russia | 66 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| CLOUD-IX SPBSt. Petersburg, Russia | 25 | |
| PIRIXSt.Petersburg, Russia | 6 |
Facilities (3)
The buildings Nevalink lists in PeeringDB, and how many of the exchanges in each it's on.
| Bolshaya Morskaya 18St. Petersburg | 4 of 9 | |
| Raduga-2St. Petersburg | 4 of 8 | |
| Tsvetochnaya Data CenterSt. Petersburg | 4 of 8 |