ixreport

ORIENT TELECOMS

AS38278 · Orient Telecoms Malaysia

ORIENT TELECOMS MALAYSIA

3Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
1Using the route servers
1To fix in PeeringDB
5Facilities in PeeringDB

Tools: Where can I peer with ORIENT TELECOMS? · Where should ORIENT TELECOMS peer next? · Compare ORIENT TELECOMS with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in ORIENT TELECOMS's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 12:40 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.

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where ORIENT TELECOMS's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 22G across 3 exchanges.

Singapore Equinix Singapore Singapore, Singapore 27.111.228.100 2001:de8:4::13:2837:2 10G PeeringDB
Malaysia MyIX Kuala Lumpur, Malaysia 218.100.44.74
218.100.44.222
2001:de8:10::a
2001:de8:10::b7
10G + 1G PeeringDB only
Singapore SGIX Singapore, Singapore 103.16.102.90 2001:de8:12:100::90 1G Yes Both

Exchanges in its buildings that it isn't on (12)

These exchanges have a switch in a facility where ORIENT TELECOMS lists itself in PeeringDB, but don't have ORIENT TELECOMS as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Facilities (5)

The buildings ORIENT TELECOMS lists in PeeringDB, and how many of the exchanges in each it's on.

Singapore Equinix SG1 - SingaporeSingapore 2 of 11
Malaysia AIMS Kuala LumpurKuala Lumpur 1 of 6
Malaysia CSF CX1 / TelcoHub1 Kuala LumpurCyberjaya 1 of 5
Malaysia CX2 / MY01 Cyberjaya MalaysiaCyberjaya 0 of 3
Malaysia TM ONE, Plaza VADSKuala Lumpur No exchange