ixreport

Novso

AS25358

Novso SARL

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
1Using the route servers
2To fix in PeeringDB
7Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Novso'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 Novso'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 Novso's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
    IPv4193.239.117.175
    IPv62001:7f8:13::a502:5358:1
    SpeedNot published
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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. France nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France · PeeringDB 4705
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 185.1.14.97: set Speed to 10000 (10G) (now 100000).

    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

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

Map

Where Novso'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 300G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

France Equinix Paris Paris, France 195.42.144.3
195.42.145.80
2001:7f8:43::2:5358:1
2001:7f8:43::2:5358:2
2 × 100G PeeringDB
France nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 185.1.14.97 2001:7f8:12e::2:5358:1 100G Both Speed differs
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.117.175 2001:7f8:13::a502:5358:1 Yes Not in PeeringDB

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

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

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