google and cloudflare dns kan ado.
TIME DNS Issue again?
TIME DNS Issue again?
|
|
May 8 2024, 08:09 PM
Return to original view | Post
#1
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
google and cloudflare dns kan ado.
|
|
|
|
|
|
May 8 2024, 08:18 PM
Return to original view | Post
#2
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
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 This post has been edited by zerorating: May 8 2024, 08:25 PM |
|
|
May 8 2024, 09:01 PM
Return to original view | Post
#3
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
QUOTE(blacktubi @ May 8 2024, 08:54 PM) Kabel besar is just a marketing gimmick 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? binggungTIME in 2024 is just not what it used to be Nowadays Maxis / Unifi is better than TIME at EU, China, JP routing maybe equinix themself buat tahik, no give priority to our network packets. same can be said for cogent sometime. This post has been edited by zerorating: May 8 2024, 09:08 PM |
|
|
May 8 2024, 09:09 PM
Return to original view | Post
#4
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
QUOTE(MamulaMoon @ May 8 2024, 09:05 PM) their kepala think TM service is bad, so alternative is better option.meanwhile myself, TM is very good because thats the only provider service us for quite some time. having low quality service is better than no service. |
|
|
May 8 2024, 09:22 PM
Return to original view | Post
#5
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
|
|
|
May 9 2024, 12:55 AM
Return to original view | Post
#6
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
QUOTE(blacktubi @ May 9 2024, 12:37 AM) Comparison of Unifi and TIME to twitter.com. It's kinda obvious which one got superior peering and routing. looks like ntt issue to me, hop 5 is fine, hop 6 is packet loss galore.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 |
|
|
May 9 2024, 01:15 AM
Return to original view | Post
#7
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
QUOTE(blacktubi @ May 9 2024, 01:07 AM) NTT is always congested, last reported in Jan and never got fixed depending at ntt alone is kinda dangerous, they are datacenter provider not a full fledge isp here. whats the point of globaltransit if time cant have their own gateway on the target country or direct route to the isp of the target countryhttps://forum.lowyat.net/index.php?showtopi...ost&p=109048968 https://forum.lowyat.net/index.php?showtopi...ost&p=109071408 This post has been edited by zerorating: May 9 2024, 01:26 AM |
|
|
May 9 2024, 10:46 AM
Return to original view | Post
#8
|
![]() ![]() ![]() ![]() ![]()
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis |
blacktubi
NTT arcnet route traffic to australia instead. x.com load just fine. i guess NTT aware on the high utilization and only help moving corporate user from the mess. CODE Tracing route to x.com [104.244.42.65] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 10.x.x.x 2 3 ms 2 ms 2 ms 10.x.x.x 3 2 ms 2 ms 2 ms 10.x.x.x 4 3 ms 3 ms 10 ms x.x.x.x 5 4 ms 3 ms 3 ms cbj-br1.arc.net.my [203.115.232.53] 6 4 ms 2 ms 4 ms 203.115.224.110 7 223 ms 210 ms 210 ms 116.51.36.11 8 130 ms 131 ms 129 ms 103.13.83.171 9 220 ms 220 ms 220 ms as13414.sydney.megaport.com [103.26.68.119] 10 232 ms 232 ms 231 ms 104.244.42.65 This post has been edited by zerorating: May 9 2024, 10:47 AM |
| Change to: | 0.0154sec
0.24
6 queries
GZIP Disabled
Time is now: 7th December 2025 - 05:01 AM |