care to report for ipv6?

nvm looks fixed.


This post has been edited by zerorating: Nov 27 2025, 12:04 AM

How about routing to China sites and international routing?

So far so good, I have nothing to complain

How to complain to TM NOC? Does their live chat helps?

unless you are enterprise user, your ticket will get discarded by the first line or technical support. your best bet is report a case, being informed that the ticket is closed and you create a report via cfm telling that your case is closed without a solution.

of course they best way to reach them is you personally know them, someone like anime4000 for example.

Its just the ip range you using no issue, TM doesn't fixed it at all, still the same routing path given.

Its been ages since this issue started, and no solution has been reached by either side

then complain for your IP range.
mine always connected to the same IP subnet. so it may remain fixed. i think the problem that we had is more on fiber pair being down or the link auto-negotiated with slower link speed, not much on route problem.



This post has been edited by zerorating: Nov 30 2025, 09:45 PM

The issue is not day 1, been complaining for years the feedback always the same copy and paste script. And also because TM ingress using on HE.net for Cloudflare, so you know what i mean. Once TM or He.net do traffic sharping for their incoming traffic it will exploded (high latency or keep loss packet) especially on night time.

I dont know why both parties not willingness to do PNI, since most of website are using Cloudflare.

TM dont use hurricane electric hops here for local cloudflare pop. yeah i agree that many websites are not locally cache here.

also if you realized TM dont rely much on hurricane electric links either. they moved to the like of telstra or tata. for singapore cloudflare resource, they can use equinix public peering instead.

Cloudflare KUL and SG are using HE.net, i already checked their ingress to TM.

As far i know TM already dropped Telstra peering long ago. Anyway the best is using PNI rather then using any IX or upstream because always having limitation on the traffic.

not true for egress.
Target Name: lowyat.net
IP: 2606:4700:20::ac43:4a59
Date/Time: 12/1/2025 11:45:39 PM - 12/1/2025 11:55:39 PM

Hop Sent PL% Min Max Avg Host Name / [IP]
1 3 0 1.10 4.67 3.24 2001:e68:542c:87x::1 [2001:e68:542c:87x::1]
2 2 0 5.61 7.68 6.65 2001:e68:402c:8001::71 [2001:e68:402c:8001::71]
3 2 0 10.93 13.08 12.01 2001:e68::b:22 [2001:e68::b:22]
4 2 50 21.45 21.45 21.45 2403:e800:e804:c::1 [2403:e800:e804:c::1]
5 2 0 15.51 17.44 16.48 2403:e800:57f:2::2 [2403:e800:57f:2::2]
6 2 0 16.39 27.15 21.77 2400:cb00:741:3:: [2400:cb00:741:3::]
7 2 0 14.14 17.77 15.95 lowyat.net [2606:4700:20::ac43:4a59]

no point on using Hurricane electric for servers located in menara aims, KL. TM have private peering with cloudflare anyway. myix can be used as a fallback.

This post has been edited by zerorating: Dec 1 2025, 11:59 PM

how about IPv4 for Telstra, i tried providers that using single Telstra none of them can route their ingress for Telstra back to TM.

Yes, they do have PNI with Cloudflare but is only Egress traffic to Cloudflare which is useless(main issue we had on is ingress traffic itself). FYI, Cloudflare MYIX sometime is congested during night time ( i did test with local provider which using MYIX to cloudflare)

connection via ipv4 to cloudflare singapore uses equinix public peering, not sure what between TM and equinix as icmp forwarding is disable on those appliance, but there is possibility of TM own node. myix are no longer being prioritized when TM left and right making private peering with other organization locally.

if you have private peering with someone, it is most likely that private link will be prioritized first both way even-though utilization were high. ipv6 seems to work great for cf-ray-kl and cf-ray-sg at the moment. why you want to bother with ipv4 anyway?

anyway hurricane electric link(ipv4) is crap at the moment, long time already they havent fix their circuit. though ipv6 seems to be fine.



looking on telstra looking glass, yeah ipv4 is messed up. but sg to kl pop is fine, and KL pop can reach TM's IP. so someone need to fix their internal routing table. it is most likely your provider are the one need to talk with their ISP, telstra to fix it.

This post has been edited by zerorating: Dec 2 2025, 01:10 AM

I also noticed high PL recently, been like this for a while now
However, last night even Allo feels a bit off