ixreport

TIME DotCom Berhad

AS9930 · TTDotCom

8Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
6Using the route servers
1To fix in PeeringDB
7Facilities in PeeringDB

Tools: Where can I peer with TIME DotCom Berhad? · Where should TIME DotCom Berhad peer next? · Compare TIME DotCom Berhad with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in TIME DotCom Berhad's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on TIME DotCom Berhad'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 (1)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G400G
    • In the entry with IPv4 80.81.196.226: set Speed to 400000 (400G) (now 10000).

Exchanges over time

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

Map

Where TIME DotCom Berhad'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 430G across 8 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.214.40 2001:7f8:1::a500:9930:1 10G 1,143 routes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.196.226 2001:7f8::26ca:0:1 10G 1,085 routes Both Speed differs
Hong Kong Equinix Hong Kong Hong Kong, Hong Kong 36.255.56.148
36.255.57.210
2001:de8:7::9930:1
2001:de8:7::9930:2
20G + 10G Yes PeeringDB
Singapore Equinix Singapore Singapore, Singapore 27.111.229.2
27.111.229.117
2001:de8:4::9930:1
2001:de8:4::9930:3
2 × 100G PeeringDB
Hong Kong HKIX Hong Kong, Hong Kong 123.255.90.138 2001:7fa:0:1::ca28:a08a 20G Yes Both
United Kingdom LINX LON1 London, United Kingdom 195.66.231.47 2001:7f8:4::26ca:1 10G 1,133 routes Both
Malaysia MyIX Kuala Lumpur, Malaysia 218.100.44.112
218.100.44.195
2001:de8:10::2
2001:de8:10::97
100G + 20G Both
Singapore SGIX Singapore, Singapore 103.16.102.39 2001:de8:12:100::39 30G Yes Both

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

These exchanges have a switch in a facility where TIME DotCom Berhad lists itself in PeeringDB, but don't have TIME DotCom Berhad 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 (7)

The buildings TIME DotCom Berhad lists in PeeringDB, and how many of the exchanges in each it's on.

Singapore Equinix SG1 - SingaporeSingapore 2 of 11
Singapore Equinix SG3 - SingaporeSingapore 2 of 7
Malaysia AIMS Kuala LumpurKuala Lumpur 1 of 6
Malaysia CSF CX1 / TelcoHub1 Kuala LumpurCyberjaya 1 of 5
Hong Kong MEGA-i (iAdvantage Hong Kong)Hong Kong 1 of 4
Malaysia AIMS CJ1 CyberjayaCyberjaya No exchange
Malaysia AIMS CyberjayaCyberjaya No exchange