ixreport

NOVOSYSTEM

AS34832

NOVOSYSTEM Ltd.

PeeringDB Follow changes
1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with NOVOSYSTEM? · Where should NOVOSYSTEM peer next?

PeeringDB fix list Printable page

One thing to fix in NOVOSYSTEM's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-12 12:37 UTC.

Make the changes on NOVOSYSTEM'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 NOVOSYSTEM's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.227.115
    IPv62a03:5f80:4::227:115
    Speed40000 Mbps (40G)
    RS peerYes
    IPv4178.18.227.124
    IPv62a03:5f80:4::227:124
    Speed40000 Mbps (40G)
    RS peerYes

    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

This chart fills in as daily counts build up; the first was Oct 12, 2026.

Exchanges
Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.115
178.18.227.124		 2a03:5f80:4::227:115
2a03:5f80:4::227:124		 40G Yes Not in PeeringDB

NOVOSYSTEM lists no facilities in PeeringDB.

Recent changes Search them

  • Oct 12, 2026 [IXF] AS34832 NOVOSYSTEM added to GNM-IX