TIME DotCom Berhad
AS9930 · TTDotCom
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.
-
Problem PeeringDB has The export has Port speed differs 10G 400G - In the entry with IPv4 80.81.196.226: set Speed to 400000 (400G) (now 10000).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 8 |
| Nov 15, 2026 | 8 |
| Nov 14, 2026 | 8 |
| Nov 13, 2026 | 8 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 8 |
| Nov 9, 2026 | 8 |
| Nov 8, 2026 | 8 |
| Nov 7, 2026 | 8 |
| Nov 6, 2026 | 8 |
| Nov 5, 2026 | 8 |
| Nov 4, 2026 | 8 |
| Nov 3, 2026 | 8 |
| Nov 2, 2026 | 8 |
| Nov 1, 2026 | 8 |
| Oct 31, 2026 | 8 |
| Oct 30, 2026 | 8 |
| Oct 29, 2026 | 8 |
| Oct 28, 2026 | 8 |
| Oct 27, 2026 | 8 |
| Oct 26, 2026 | 8 |
| Oct 25, 2026 | 8 |
| Oct 24, 2026 | 8 |
| Oct 23, 2026 | 8 |
| Oct 22, 2026 | 8 |
| Oct 21, 2026 | 8 |
| Oct 20, 2026 | 8 |
| Oct 19, 2026 | 8 |
| Oct 18, 2026 | 8 |
| Oct 17, 2026 | 8 |
| Oct 16, 2026 | 8 |
| Oct 15, 2026 | 8 |
| Oct 14, 2026 | 8 |
| Oct 13, 2026 | 8 |
| Oct 12, 2026 | 8 |
| Oct 11, 2026 | 8 |
| Oct 10, 2026 | 8 |
| Oct 9, 2026 | 8 |
| Oct 8, 2026 | 8 |
| Oct 7, 2026 | 8 |
| Oct 6, 2026 | 8 |
| Oct 5, 2026 | 8 |
| Oct 4, 2026 | 8 |
| Oct 3, 2026 | 8 |
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.
| AMS-IX Amsterdam, Netherlands | 10G | Both | |
| DE-CIX Frankfurt Frankfurt, Germany | 10G | Both Speed differs | |
| Equinix Hong Kong Hong Kong, Hong Kong | 20G + 10G | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 2 × 100G | PeeringDB | |
| HKIX Hong Kong, Hong Kong | 20G | Both | |
| LINX LON1 London, United Kingdom | 10G | Both | |
| MyIX Kuala Lumpur, Malaysia | 100G + 20G | Both | |
| SGIX Singapore, Singapore | 30G | Both |
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.
| NetIXSofia, Bulgaria | 204 | |
| BBIX SingaporeSingapore, Singapore | 169 | |
| DE-CIX ASEANSingapore, Singapore | 140 | |
| BBIX Hong KongHong Kong, Hong Kong | 104 | |
| Transhybrid IX NetworkJakarta, Indonesia | 63 | |
| MegaIX SingaporeSingapore, Singapore | 46 | |
| DE-CIX Kuala LumpurKuala Lumpur, Malaysia | 45 | |
| IAIXHong Kong, Hong Kong | 20 | |
| DE-CIX MalaysiaKuala Lumpur, Cyberjaya, Johor Bahru, Malaysia | 15 | |
| GNM-IX SGSingapore, Singapore | 15 | |
| AMS-IX SingaporeSingapore, Singapore | 14 | |
| CSL Thai-IX MalaysiaBangkok, Thailand | 13 | |
| Impart IXSingapore, Singapore | 7 | |
| Global Peer ExchangeWashington, United States | 6 |
Facilities (7)
The buildings TIME DotCom Berhad lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix SG1 - SingaporeSingapore | 2 of 11 | |
| Equinix SG3 - SingaporeSingapore | 2 of 7 | |
| AIMS Kuala LumpurKuala Lumpur | 1 of 6 | |
| CSF CX1 / TelcoHub1 Kuala LumpurCyberjaya | 1 of 5 | |
| MEGA-i (iAdvantage Hong Kong)Hong Kong | 1 of 4 | |
| AIMS CJ1 CyberjayaCyberjaya | No exchange | |
| AIMS CyberjayaCyberjaya | No exchange |