ORIENT TELECOMS: PeeringDB fix list

AS38278 · peeringdb.com/net/4354

PeeringDB

One thing to fix in ORIENT TELECOMS's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on ORIENT TELECOMS's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If ORIENT TELECOMS has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Malaysia MyIX Kuala Lumpur, Malaysia · PeeringDB 250Not on its website members list
    IPv4218.100.44.222
    IPv62001:de8:10::b7
    Speed1000 Mbps (1G)
    IPv4218.100.44.74
    IPv62001:de8:10::a
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

From ixreport.com/net/38278/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.