ixreport

Flex

AS21453

Flex Ltd.

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
8Using the route servers
1To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Flex? · Where should Flex peer next? · Compare Flex with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Flex's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Flex's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 178.18.226.39: set Speed to 100000 (100G) (now 30000).

    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

02468Oct 3, 2026Nov 19, 20268
Show as a table
DateExchanges
Nov 19, 20268
Nov 18, 20268
Nov 17, 20268
Nov 16, 20268
Nov 15, 20268
Nov 14, 20268
Nov 13, 20268
Nov 12, 20268
Nov 11, 20268
Nov 10, 20268
Nov 9, 20268
Nov 8, 20268
Nov 7, 20268
Nov 6, 20268
Nov 5, 20268
Nov 4, 20268
Nov 3, 20268
Nov 2, 20268
Nov 1, 20268
Oct 31, 20268
Oct 30, 20268
Oct 29, 20268
Oct 28, 20268
Oct 27, 20268
Oct 26, 20268
Oct 25, 20268
Oct 24, 20268
Oct 23, 20268
Oct 22, 20268
Oct 21, 20268
Oct 20, 20268
Oct 19, 20268
Oct 18, 20268
Oct 17, 20268
Oct 16, 20268
Oct 15, 20268
Oct 14, 20268
Oct 13, 20268
Oct 12, 20268
Oct 11, 20268
Oct 10, 20268
Oct 9, 20268
Oct 8, 20268
Oct 7, 20268
Oct 6, 20268
Oct 5, 20268
Oct 4, 20268
Oct 3, 20268

Map

Where Flex'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.

Exchanges

Total port capacity 610G across 8 exchanges.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.39 2a03:5f80:4::226:39 30G Yes Both Speed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.210.7 2001:7f8:20:101::210:7 100G Yes Both
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.130 80G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.88 80G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.12.159 2001:7f8:eb::53cd:1 80G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.158 80G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.118 2001:7f8:e6::53cd:1 80G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.126 80G Yes PeeringDB

Exchanges in its buildings that it isn't on (5)

These exchanges have a switch in a facility where Flex lists itself in PeeringDB, but don't have Flex 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.

Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9; Moscow TehnoGorod
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; Moscow TehnoGorod
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (2)

The buildings Flex lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 4 of 9
Russia Moscow TehnoGorodMoscow 1 of 3