ixreport

WEBCONEX

AS211448 · Webconex

SAS WEBCONEX

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
5Using the route servers
2To fix in PeeringDB
3Facilities in PeeringDB

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

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in WEBCONEX's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on WEBCONEX'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 (2)

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. ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.125.184none
    • In the entry with IPv4 185.1.125.184: set IPv4 to (empty) (now 185.1.125.184).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 178.18.237.107: set Speed to 10000 (10G) (now 1000).

    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

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

Map

Where WEBCONEX'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 104G across 5 exchanges.

Switzerland 4b42 Internet Exchange Point Zurich, Switzerland 185.1.125.184 2001:7f8:d0::3:39f8:1 1G Yes Both IPv4 not in export
France France-IX Paris Paris, France 37.49.238.61 2001:7f8:54::2:61 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.237.107 2a03:5f80:4:2::237:107 1G Yes Both Speed differs
Germany LOCIX DUSSELDORF Dusseldorf, Germany 185.1.155.85 2a0c:b641:701:0:a5:21:1448:1 1G Yes PeeringDB
Switzerland SBIX Zurich Lupfig, Switzerland 185.1.135.51 2001:7f8:d9:5b:0:3:39f8:1 1G Yes PeeringDB

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

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

Facilities (3)

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

Germany WIIT Datacenter DUS1, DUS2, DUS3, DUS4, DUS6, DUS7Düsseldorf 1 of 6
France dc2scale PAR2 (Vélizy-Villacoublay)Vélizy-Villacoublay No exchange
France DyjixVélizy-Villacoublay No exchange