Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 TIME DNS Issue again?

views
     
blacktubi
post May 8 2024, 08:54 PM

-
Group Icon
Elite
8,409 posts

Joined: Jul 2008

QUOTE(zerorating @ May 8 2024, 08:18 PM)
and some people complaining high response time to twitter.
so much for so called superior routing.
https://forum.lowyat.net/topic/5456242

but question is which submarine cable pecah until NTT become badly impacted?
my office vpn also NTT send to japan gateway dunno for what reason? NTT gateway in cyberjaya jahanam meh?
CODE
Tracing the route to 104.244.42.129

1  ae-2.r22.kslrml02.my.bb.gin.ntt.net (129.250.3.224) 2 msec  *  2 msec
2   *  *
   ae-5.r27.tkokhk01.hk.bb.gin.ntt.net (129.250.2.195) [MPLS: Label 215797 Exp 0] 40 msec
3   *  *
   ae-13.r33.tokyjp05.jp.bb.gin.ntt.net (129.250.2.243) 72 msec
4   *
   ae-5.a01.tokyjp10.jp.bb.gin.ntt.net (129.250.6.35) 75 msec  83 msec
5  ae-1.a03.osakjp02.jp.bb.gin.ntt.net (129.250.4.219) 360 msec  350 msec
   ce-1-0-3.a01.tokyjp10.jp.ce.gin.ntt.net (120.88.53.154) 72 msec
6  ae-0.x-corp.osakjp02.jp.bb.gin.ntt.net (61.200.82.46) 340 msec  373 msec
   twitter.com (104.244.42.129) 72 msec

*
Kabel besar is just a marketing gimmick

TIME in 2024 is just not what it used to be

Nowadays Maxis / Unifi is better than TIME at EU, China, JP routing
blacktubi
post May 9 2024, 12:26 AM

-
Group Icon
Elite
8,409 posts

Joined: Jul 2008

QUOTE(MR_alien @ May 8 2024, 08:59 PM)
not from what i experience these few weeks
that bad routing is affect all ISP and telco

but the experience straight turn table after i turn on my warp...so it definitely confirms it's our problem
*
QUOTE(Quantum Geist @ May 8 2024, 09:00 PM)
unifi has been suffering intermittent lags at night almost every night for me, disconnect and reconnecting to get a different public ip range sometimes work to fix it, not sure of the reasoning though
*
QUOTE(zerorating @ May 8 2024, 09:01 PM)
cant said that, TM route to equinix US hop/gateway is kinda inconsistent, people over here complaining about imgur.com slow, but twitter via equinix US okay pulak? binggung
maybe equinix themself buat tahik, no give priority to our network packets. same can be said for cogent sometime.
*
While I agree that all ISPs are kinda affected by the SMW5 cable cut to EU, my TIME fibre is worst with much higher latency and comes with packet loss.

TM Unifi
CODE
ping ionos.de
PING ionos.de (217.160.86.49): 56 data bytes
64 bytes from 217.160.86.49: icmp_seq=0 ttl=53 time=300.086 ms
64 bytes from 217.160.86.49: icmp_seq=1 ttl=53 time=278.544 ms
64 bytes from 217.160.86.49: icmp_seq=2 ttl=53 time=281.629 ms
64 bytes from 217.160.86.49: icmp_seq=3 ttl=53 time=285.517 ms
64 bytes from 217.160.86.49: icmp_seq=4 ttl=53 time=331.620 ms
64 bytes from 217.160.86.49: icmp_seq=5 ttl=53 time=277.634 ms
^C
--- ionos.de ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 277.634/292.505/331.620/19.020 ms


TIME Fibre
CODE
ping ionos.de
PING ionos.de (217.160.86.49): 56 data bytes
64 bytes from 217.160.86.49: icmp_seq=0 ttl=58 time=445.806 ms
64 bytes from 217.160.86.49: icmp_seq=1 ttl=58 time=459.067 ms
Request timeout for icmp_seq 2
64 bytes from 217.160.86.49: icmp_seq=3 ttl=58 time=491.900 ms
64 bytes from 217.160.86.49: icmp_seq=4 ttl=58 time=409.083 ms
Request timeout for icmp_seq 5
^C
--- ionos.de ping statistics ---
7 packets transmitted, 4 packets received, 42.9% packet loss
round-trip min/avg/max/stddev = 409.083/451.464/491.900/29.669 ms


Feel free to try and share your results.

This post has been edited by blacktubi: May 9 2024, 12:28 AM
blacktubi
post May 9 2024, 12:37 AM

-
Group Icon
Elite
8,409 posts

Joined: Jul 2008

QUOTE(zerorating @ May 8 2024, 08:18 PM)
and some people complaining high response time to twitter.
so much for so called superior routing.
https://forum.lowyat.net/topic/5456242

but question is which submarine cable pecah until NTT become badly impacted?
my office vpn also NTT send to japan gateway dunno for what reason? NTT gateway in cyberjaya jahanam meh?
CODE
Tracing the route to 104.244.42.129

1  ae-2.r22.kslrml02.my.bb.gin.ntt.net (129.250.3.224) 2 msec  *  2 msec
2   *  *
   ae-5.r27.tkokhk01.hk.bb.gin.ntt.net (129.250.2.195) [MPLS: Label 215797 Exp 0] 40 msec
3   *  *
   ae-13.r33.tokyjp05.jp.bb.gin.ntt.net (129.250.2.243) 72 msec
4   *
   ae-5.a01.tokyjp10.jp.bb.gin.ntt.net (129.250.6.35) 75 msec  83 msec
5  ae-1.a03.osakjp02.jp.bb.gin.ntt.net (129.250.4.219) 360 msec  350 msec
   ce-1-0-3.a01.tokyjp10.jp.ce.gin.ntt.net (120.88.53.154) 72 msec
6  ae-0.x-corp.osakjp02.jp.bb.gin.ntt.net (61.200.82.46) 340 msec  373 msec
   twitter.com (104.244.42.129) 72 msec

*
Comparison of Unifi and TIME to twitter.com. It's kinda obvious which one got superior peering and routing.


Unifi
CODE
2. 175.145.124.126               0.0%    38    7.7   8.5   6.7  18.5   2.2
3. 10.55.74.65                   0.0%    38  176.0 176.2 173.7 180.5   1.1
4. 10.55.68.57                   0.0%    38  199.0 198.5 196.8 201.7   1.0
5. 10.55.100.236                 0.0%    38   18.6  18.9  16.9  31.4   2.9
6. 10.55.192.125                 0.0%    37  175.4 175.5 173.4 182.6   1.4
7. eqix1.cr1.sjc2.twttr.com      0.0%    37  176.9 177.0 174.5 209.2   5.7
8. (waiting for reply)
9. 104.244.42.65                 0.0%    37  191.7 191.9 191.0 195.4   0.8


TIME
CODE
2. 202.184.32.1                              0.0%    34   17.6  18.2  16.8  23.1   1.4
3. (waiting for reply)
4. 223.28.43.34                              0.0%    34   18.4  19.5  17.6  29.1   2.5
5. ae-8.r01.kslrml02.my.bb.gin.ntt.net       0.0%    34   19.3  20.6  16.6  28.0   2.3
6. ae-2.r22.kslrml02.my.bb.gin.ntt.net      51.5%    33   20.4  20.7  18.6  29.8   2.7
7. ae-5.r27.tkokhk01.hk.bb.gin.ntt.net      39.4%    33   51.0  52.9  50.5  57.7   2.3
8. ae-4.r26.osakjp02.jp.bb.gin.ntt.net      59.4%    33   94.5  94.0  92.0  98.7   2.1
9. ae-0.r27.osakjp02.jp.bb.gin.ntt.net      42.4%    33   91.7  95.2  90.7 118.1   6.5
10. ae-1.a03.osakjp02.jp.bb.gin.ntt.net       0.0%    33   98.4  95.8  90.9 115.3   5.3
11. ae-0.x-corp.osakjp02.jp.bb.gin.ntt.net   15.2%    33  402.8 394.5 339.8 408.3  13.3
12. 104.244.42.193                            6.1%    33  402.6 395.8 339.5 404.9  15.1

blacktubi
post May 9 2024, 01:07 AM

-
Group Icon
Elite
8,409 posts

Joined: Jul 2008

QUOTE(zerorating @ May 9 2024, 12:55 AM)
looks like ntt issue to me, hop 5 is fine, hop 6 is packet loss galore.
*
NTT is always congested, last reported in Jan and never got fixed

https://forum.lowyat.net/index.php?showtopi...ost&p=109048968
https://forum.lowyat.net/index.php?showtopi...ost&p=109071408

 

Change to:
| Lo-Fi Version
0.0138sec    0.34    6 queries    GZIP Disabled
Time is now: 7th December 2025 - 07:29 AM