MSR IX: operator report
shibuya, Japan · PeeringDB 4499 · ixreport.com/ix/4499/report/
Members of MSR IX that PeeringDB has wrong, from its website members list (13 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 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.
On your lists, missing from PeeringDB (4)
These networks could add MSR IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS44324 MoeDove Global | website | 2602:f919:90f:fffa::4432:4 | NOC: email address (needs JavaScript) |
| AS51087 Bling Network | website | 2602:f919:90f:fffa::5108:7 | No public contact |
| AS138435 YuetAu Network | website | 2602:f919:90f:fffa::1384:35 | NOC: email address (needs JavaScript) |
| AS401009 JSMSR Servers | website | 2602:f919:90f:fffa::2 | NOC: email address (needs JavaScript) |
Addresses or port speeds that differ (0)
MSR IX 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.