IXMidlands: operator report
Wolverhampton, United Kingdom · PeeringDB 4912 · ixreport.com/ix/4912/report/
Members of IXMidlands that PeeringDB has wrong, from its website members list (7 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 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.
On your lists, missing from PeeringDB (3)
These networks could add IXMidlands to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS22359 NETSKRTSYSTEMS-UK | website | 195.13.37.204 2001:7f8:ec::cc |
No public contact |
| AS48628 CoreISP | website | 195.13.37.205 2001:7f8:ec::cd |
Policy: email address (needs JavaScript) +443307881234 |
| AS200681 AS200681 | website | 195.13.37.193 2001:7f8:ec::1 |
No PeeringDB record |
Addresses or port speeds that differ (0)
IXMidlands 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.