NeverIX Velbert: operator report
Velbert, Germany · PeeringDB 5124 · ixreport.com/ix/5124/report/
Members of NeverIX Velbert that PeeringDB has wrong, from its IX-F export (22 networks, read 2026-11-12 18:21 UTC), against PeeringDB as of 2026-11-12 18:41 UTC. 4 networks to follow up; 3 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 NeverIX Velbert's own member lists. Report by IX Report (ixreport.com).
On your lists, missing from PeeringDB (4)
These networks could add NeverIX Velbert to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS23507 AVINTERNET | IX-F | 2602:fa86:ffe::a 10G |
NOC: email address (needs JavaScript) |
| AS210464 AVS ISP | IX-F | 2602:fa86:ffe::b 100G |
Technical: email address (needs JavaScript) |
| AS214976 API VERSA OU | IX-F | 2602:fa86:ffe::c 10G |
Technical: email address (needs JavaScript) |
| AS219451 justinbrugmann | IX-F | 2602:fa86:ffe::14 10G |
No public contact |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 18 networks in both. Either the network's PeeringDB record or the export is out of date.
None: every network's addresses and port speed match.
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.