Of course they're holding the admin account access secretly behind your knowledge. It allows them full access into your router's full features/functions while doing it remotely.

I think as honest ISP, their customers demand the right to be aware of it. Someone who gains access to it can play around with the advance features in the router and observe all the connections/activities you do on your line with the logging function in it.

Maxis has recently added Tata Communications (AMERICA) and Hurricane Electric to their existing upstream peering list as of 20/04/2021.



Noticed that latency to Amsterdam/Netherlands & UK improved tremendously with pings between 170ms-190ms but the changes also messed up their routes to other continental Western European countries which saw latency shot up as high as 100ms to countries such as Belgium, Luxembourg and Switzerland.

Here are a few examples:

M247 Ltd Belgium
speed.be.m247.ro


Broadcast Center Europe, Luxembourg
speedtest1.bce.lu


31173 Services AB Switzerland
zur-ix1-tptest1.31173.se


Please take note Maxis, your routing went bad again for Europe.

Appreciate the improvements made to routes connecting London(UK), Amsterdam(NL) & Vienna(AT), but the efforts were negated by the bad routes to Belgium(BE), Luxembourg(LU) and Switzerland(CH).

It seems these routes are now routed across the Pacific spanning America -> Paris -> Continental Europe/Benelux countries. As you can see through the MTR results, Cogent route is the source of the bad routing.

HE/NTT Europe/GTT did an excellent job on their part reaching Europe via main IXs within latency 170-190ms range. So it should be around that range for latency connecting Belgium, France, Luxembourg and Switzerland from Malaysia. This was before Tata Communications/HE was added to the upstream peering list.

After they were added, we observed that the latency before this from 170-190ms spiked to almost 100ms more and now everaging close to 300ms between 260ms-290ms.

This post has been edited by Candy12: Apr 20 2021, 05:28 PM

TMnet has AS6661 POST Luxembourg

Time Global Transit Carrier has:
AS6661 POST Luxembourg
AS56665 Proximus Luxembourg S.A.

Even a small ISP such as Allo guess what? They have peering with:
AS6774 Belgacom International Carrier Services SA
AS56665 Proximus Luxembourg S.A

Maxis has NONE in the following Benelux countries and WORST it doesn't have good peering partners in Switzerland and even France(except ACORUS NETWORKS SAS AS35280) which is insignificant.

What's the use of having good Tier-1 upstream providers such as NTT, TI-Sparkle, GTT and now Tata when upon handover to the receiving EU ISP, it doesn't want to prioritize the reception of the packets originating from Maxis?

The 2 BIGGEST Issue Maxis has to solve now is:

I suggest:

For Belgium
Orange Belgium SA (AS47377), Belgacom International Carrier Services SA (AS6774), Interxion Belgium NV. (AS31651)

For Luxembourg
POST Luxembourg(AS6661), Proximus Luxembourg(AS56665), Datacenter Luxembourg(DataLux) S.A. (AS24611), root SA Luxembourg (AS5577)

For Switzerland
Swisscom AG aka IP-Plus (AS3303), Init7 (Switzerland) Ltd. (AS13030), AlpineDC SA (AS198385), Salt Mobile SA (AS15796), Sunrise Communications AG (AS6730)

For France
Orange S.A. (AS5511), AS12876 ONLINE S.A.S. aka Scaleway, OVH SAS (AS16276), Bouygues Telecom SA (AS5410)

For China
China Mobile International Limited (AS58453), China Telecom Next Generation Carrier Network (AS4809), China Unicom Backbone (AS4837)

If you look at this MTR results, you will noticed that NTT Europe did a good job routing to Belgium at around 197ms but at handover to the destination's server, the ping shot up by almost 100ms extra to as high as >330ms because the receiving ISP has no peering agreement with Maxis and thus de-prioritizes the receiving packet.



This post has been edited by Candy12: Apr 20 2021, 11:57 PM

Upon further check, I found that something's up with NTT. It affects not just Maxis but all ISPs who are now using them as their main upstream carrier.

They are now routing ALL their Europe bound traffic across the Pacific to America then via the Atlantic ocean to reach Europe.

Maxis to FDC-Frankfurt
lg.fra2-c.fdcservers.net


Maxis to FDC-Zurich
lg-zur.fdcservers.net


Maxis to FDC-London
lg.lon-c.fdcservers.net


It makes SENSE for countries in the Far East like Japan to take the Pacific->USA->Atlantic Route to reach Europe because they save on the 75-80ms return trip connecting to Singapore first then head West through the Egyptian Gulf before exiting through the Mediterranean sea entering South Italy/Toulon France into Europe Mainland.



For Japan the trip across the Pacific is just around 100-110ms and to London is about 230ms.
If we use Singapore via the ME route using the Egyptian Gulf we might experience faster latency somewhere between 170-180ms but not for the Japanese and Far East countries such as North China/South Korea/Taiwan, they have an additional distance to travel southwest bound before taking the same route so it's not quite an advantage to them compared to taking the Pacific-Atlantic route to reach Europe landing points.

I forsee that eventually Maxis will have to find another alternative upstream carrier to serve its Europe bound traffic needs if they want to take further advantage of the shorter distance/faster latency via ME.
That is why TI-Sparkle, Tata, GTT and even HE Europe optimized routes via SG now comes into the picture.

NTT has never been a major player in the EMEA submarine route due to stiff competition from rivals.
They are a major force in East Asia and Trans Pacific routes though to US which makes them formidable in Asia-US markets.

So far so good with most Asian sites and US.

Only ongoing issues involving high latency due to un-optimized routing to Europe via NTT carrier.
Most Asian and US links seems fine.

It's not just Maxis having trouble with bad routes, I believe TM has a bigger headache managing their upstream carriers and routes because they have so many of them. If you head over to their topic, you will fins some of their users getting as high as >300ms pings to Seattle US. Their bad routing will take them through Amsterdam EU then across the Atlantic to reach NYC->Across US to West Coast Seattle which is crazy.

More interested to know how is it going for Celcom, DiGi and Time.

That's not true. Even using TM HSBB wholesale network your Maxis traffic from your end will only use probably the 1st 2 hops and it'l handover to Maxis's own national backbone.

Different ISPs have their own sets of international gateways and routing setups.

We're talking about international Tier-1 carrier ISPs and BGP routing here.

What do you mean by fibre backbone solely own by TM?

That's not Maxis salesman, it's one of their resident customer support based on this forum lah.