TMW-iX: operator report
Frankfurt am Main, Germany · PeeringDB 4401 · ixreport.com/ix/4401/report/
Members of TMW-iX that PeeringDB has wrong, from its website members list (5 networks, read 2026-11-19 12:22 UTC), against PeeringDB as of 2026-11-19 12:40 UTC. 3 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.
Data: PeeringDB (peeringdb.com), and TMW-iX's own member lists. Report by IX Report (ixreport.com).
On your lists, missing from PeeringDB (2)
These networks could add TMW-iX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS23506 AVS-ISP | website | – | NOC: email address (needs JavaScript) |
| AS216390 AS216390 | website | – | No PeeringDB record |
Addresses or port speeds that differ (0)
TMW-iX publishes no IX-F export we could read, so addresses and port speeds can't be compared.
In PeeringDB, not on your lists (1)
Either your lists are missing these networks, or they've left and their PeeringDB record is out of date.
| Network | In PeeringDB | Contact |
|---|---|---|
| AS59449 Konzola | 2a0e:b107:2888:0:1:5944:9:1 10G |
No public contact |