GrunIX: operator report

Groningen, Netherlands · PeeringDB 3288 · ixreport.com/ix/3288/report/

Download CSV

Members of GrunIX that PeeringDB has wrong, from its website members list (9 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 5 networks to follow up.

Contacts are the networks' public PeeringDB contacts: the peering (policy) contact where there is one, else technical, then NOC. Networks keep these themselves on PeeringDB.

On your lists, missing from PeeringDB (3)

These networks could add GrunIX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.

NetworkOn yourAddressesContact
AS41038 AS41038website – No PeeringDB record
AS41153 gnTel PeeringDBwebsite – No public contact
AS44439 2Hip Consultancy PeeringDBwebsite – No public contact

Addresses or port speeds that differ (0)

GrunIX publishes no IX-F export we could read, so addresses and port speeds can't be compared.

In PeeringDB, not on your lists (2)

Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.

NetworkIn PeeringDBContact
AS210882 TiZu Tech PeeringDB 185.1.190.213
2001:7f8:104:0:a500:21:882:1
10G
No public contact
AS218980 GrunIX Route Servers PeeringDB 185.1.190.1
185.1.190.254
2001:7f8:104::a521:8980:1
2001:7f8:104::a521:8980:254
2 × 1G
No public contact