NCL-IX: operator report
Newcastle, United Kingdom · PeeringDB 3373 · ixreport.com/ix/3373/report/
Members of NCL-IX that PeeringDB has wrong, from its IX-F export (7 networks, read 2026-10-08 21:25 UTC) and its website members list (11 networks, read 2026-10-08 21:25 UTC), against PeeringDB as of 2026-10-08 21:35 UTC. 5 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 (5)
These networks could add NCL-IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS112 DNS-OARC-112 | website | 185.1.195.6 2001:7f8:34::6 |
Technical: email address (needs JavaScript) |
| AS42010 ITPS | website | – | No public contact |
| AS43531 IX Reach | website | 185.1.195.12 2001:7f8:34::12 |
Policy: email address (needs JavaScript) |
| AS212265 NCL-IX | IX-F and website | 185.1.195.254 2001:7f8:34::254 1G |
No public contact |
| AS212655 YouFibre | website | 185.1.195.18 2001:7f8:34::18 |
No public contact |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 6 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.