Rheintal IX: operator report
Eschen, Liechtenstein · PeeringDB 543 · ixreport.com/ix/543/report/
Members of Rheintal IX that PeeringDB has wrong, from its website members list (39 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 2 networks to follow up; 1 with a public PeeringDB contact.
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 (2)
These networks could add Rheintal IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS58171 Rheintal IX Route Servers | website | 91.232.229.253 91.232.229.254 2001:7f8:66::253 2001:7f8:66::254 |
NOC: email address (needs JavaScript) |
| AS59748 Kaiser Partner | website | 91.232.229.7 2001:7f8:66::7 |
No public contact |
Addresses or port speeds that differ (0)
Rheintal IX publishes no IX-F export we could read, so addresses and port speeds can't be compared.
In PeeringDB, not on your lists (0)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
None.