Stuttgart-IX: operator report
Stuttgart, Germany · PeeringDB 212 · ixreport.com/ix/212/report/
Members of Stuttgart-IX that PeeringDB has wrong, from its IX-F export (37 networks, read 2026-10-08 22:05 UTC), against PeeringDB as of 2026-10-08 22:13 UTC. 8 networks to follow up; 2 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 Stuttgart-IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
Addresses or port speeds that differ (6)
PeeringDB against your IX-F export, for the 35 networks in both. Either the network's PeeringDB record or the export is out of date.
| Network | Problem | PeeringDB has | Your export has | Contact |
|---|---|---|---|---|
| AS6735 TNG Stadtnetz GmbH (ex sdt.net) | Port speed differs | 10G | 100G + 10G | No public contact |
| AS25058 CMO Internet Dienstleistungen | Port speed differs | 1.024G | 10G | No public contact |
| AS198818 ISP Service eG | Port speed differs | 1G | 10G | Technical: email address (needs JavaScript) +491713101372 |
| AS200924 Stiegeler Internet Service | Port speed differs | 10G | 110G | Policy: email address (needs JavaScript) |
| AS202707 omnidat | Port speed differs | 1G | 10G | No public contact |
| AS212522 Stuttgart-IX Infrastructure | Port speed differs | 100G | 200G | No public contact |
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.