Poema IX: operator report
Taipei City, Taiwan · PeeringDB 3792 · ixreport.com/ix/3792/report/
Members of Poema IX that PeeringDB has wrong, from its IX-F export (2 networks, read 2026-10-08 20:54 UTC) and its website members list (66 networks, read 2026-10-08 20:54 UTC), against PeeringDB as of 2026-10-08 20:58 UTC. 7 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 (7)
These networks could add Poema IX to their PeeringDB record. Networks with no PeeringDB record would need to create one first.
| Network | On your | Addresses | Contact |
|---|---|---|---|
| AS27010 MQNET | website | – | No public contact |
| AS33622 NEXET LLC | website | – | No public contact |
| AS51087 Bling Network | website | – | No public contact |
| AS60539 Huicast Telecommunications | website | – | Technical: email address (needs JavaScript) |
| AS139888 AS139888 | website | – | No PeeringDB record |
| AS202881 MTS Network | website | – | No public contact |
| AS204244 AS204244 | website | – | No PeeringDB record |
Addresses or port speeds that differ (0)
PeeringDB against your IX-F export, for the 2 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.