ixreport

XMT Technologies

AS134152 · XMT

XMT Technologies Sdn Bhd

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
4Using the route servers
3To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with XMT Technologies? · Where should XMT Technologies peer next? · Compare XMT Technologies with another network

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

PeeringDB fix list Printable page · CSV

3 things to fix in XMT Technologies's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 UTC.

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

Correct these entries (3)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472
    ProblemPeeringDB hasThe export has
    Port speed differs2G10G
    • In the entry with IPv4 103.162.254.9: set Speed to 10000 (10G) (now 2000).
  2. Malaysia DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia · PeeringDB 3473
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 103.119.234.9: set Speed to 10000 (10G) (now 1000).
  3. Malaysia DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia · PeeringDB 3474
    ProblemPeeringDB hasThe export has
    Port speed differs100M10G
    • In the entry with IPv4 103.119.232.1: set Speed to 10000 (10G) (now 100).

Exchanges over time

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

Map

Where XMT Technologies'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 13.1G across 4 exchanges.

Singapore DE-CIX ASEAN Singapore, Singapore 103.162.254.9 2001:df6:480:0:2:c08:0:1 2G 6 routes Both Speed differs
Malaysia DE-CIX Kuala Lumpur Kuala Lumpur, Malaysia 103.119.234.9 2403:4ac0:1:0:2:c08:0:1 1G 7 routes Both Speed differs
Malaysia DE-CIX Malaysia Kuala Lumpur, Cyberjaya, Johor Bahru, Malaysia 103.119.232.1 2403:4ac0::2:c08:0:1 100M 6 routes Both Speed differs
Malaysia MyIX Kuala Lumpur, Malaysia 218.100.44.66 2001:de8:10::e7 10G Yes Both

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

These exchanges have a switch in a facility where XMT Technologies lists itself in PeeringDB, but don't have XMT Technologies 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.

Bulgaria NetIXSofia, Bulgaria 204 AIMS Kuala Lumpur
Thailand CSL Thai-IX MalaysiaBangkok, Thailand 13 AIMS Kuala Lumpur
Facilities (1)

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

Malaysia AIMS Kuala LumpurKuala Lumpur 4 of 6