My laptop is working fine to connect
but my phone and TV connected to WIFI without internet. Same situation as last time when they kena DNS down.
TIME DNS Issue again?
|
|
 May 8 2024, 08:05 PM, updated 2y ago
Show posts by this member only | IPv6 | Post
#1
|
 
Senior Member
923 posts Joined: Nov 2006 From: KL  
|
|
Quote|
|
|
|
|
May 8 2024, 08:05 PM
Show posts by this member only | IPv6 | Post
#2
|
Senior Member
1,130 posts Joined: Jun 2015
|
nop, works fine.
|
|
|
May 8 2024, 08:09 PM
Show posts by this member only | Post
#3
|
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis
|
google and cloudflare dns kan ado.
|
|
|
May 8 2024, 08:15 PM
Show posts by this member only | IPv6 | Post
#4
|
Senior Member
3,581 posts Joined: Oct 2007 From: everywhere in sabah
|
i feel like all ISP's DNS is tak boleh guna punya
|
|
|
May 8 2024, 08:18 PM
Show posts by this member only | IPv6 | Post
#5
|
Junior Member
473 posts Joined: Dec 2009 From: Timbuktoo
|
Cloudflare problem again?
|
|
|
May 8 2024, 08:18 PM
Show posts by this member only | Post
#6
|
|
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, 08:54 PM
Show posts by this member only | Post
#7
|
 
Elite
8,409 posts Joined: Jul 2008 
|
QUOTE(zerorating @ May 8 2024, 08:18 PM) and some people complaining high response time to twitter. Kabel besar is just a marketing gimmickso 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  TIME in 2024 is just not what it used to be Nowadays Maxis / Unifi is better than TIME at EU, China, JP routing |
|
|
May 8 2024, 08:59 PM
Show posts by this member only | IPv6 | Post
#8
|
Senior Member
3,968 posts Joined: Nov 2007
|
cloudflare or google dns dah cuba ke
|
|
|
May 8 2024, 08:59 PM
Show posts by this member only | IPv6 | Post
#9
|
|
Senior Member
3,581 posts Joined: Oct 2007 From: everywhere in sabah
|
QUOTE(blacktubi @ May 8 2024, 08:54 PM) Kabel besar is just a marketing gimmick not from what i experience these few weeksTIME in 2024 is just not what it used to be Nowadays Maxis / Unifi is better than TIME at EU, China, JP routing 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 |
|
|
May 8 2024, 09:00 PM
|
Junior Member
109 posts Joined: May 2013
|
QUOTE(blacktubi @ May 8 2024, 08:54 PM) Kabel besar is just a marketing gimmick 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 thoughTIME in 2024 is just not what it used to be Nowadays Maxis / Unifi is better than TIME at EU, China, JP routing This post has been edited by Quantum Geist: May 8 2024, 09:03 PM |
|
|
May 8 2024, 09:01 PM
|
|
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:05 PM
Show posts by this member only | IPv6 | Post
#12
|
Junior Member
137 posts Joined: Mar 2009
|
I don't understand
Why so many ppl like to use Time braodband nowadays? |
|
|
May 8 2024, 09:09 PM
|
|
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis
|
QUOTE(MamulaMoon @ May 8 2024, 09:05 PM) I don't understand their kepala think TM service is bad, so alternative is better option.Why so many ppl like to use Time braodband nowadays? 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:19 PM
|
Senior Member
2,058 posts Joined: Mar 2011 From: Today: 9:03 AM 
|
Just switch to your own DNS la. Why use default DNS?
 I set alternate/3rd party DNS on my router itself and I never had issues including the previous downtime. |
|
|
May 8 2024, 09:22 PM
|
|
Senior Member
975 posts Joined: Aug 2007 From: Lokap Polis
|
QUOTE(patienceGNR @ May 8 2024, 09:19 PM) Just switch to your own DNS la. Why use default DNS? probably its not dns issue, but people treat it as dns issue. I set alternate/3rd party DNS on my router itself and I never had issues including the previous downtime. |
|
|
May 9 2024, 12:26 AM
|
|
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 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.maybe equinix themself buat tahik, no give priority to our network packets. same can be said for cogent sometime. 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 |
|
|
May 9 2024, 12:34 AM
Show posts by this member only | IPv6 | Post
#17
|
All Stars
12,039 posts Joined: Oct 2017
|
QUOTE(blacktubi @ May 9 2024, 12:26 AM) 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. CODE Pinging ionos.de [217.160.86.51] with 32 bytes of data: Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=268ms TTL=53 Reply from 217.160.86.51: bytes=32 time=271ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=268ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Reply from 217.160.86.51: bytes=32 time=268ms TTL=53 Reply from 217.160.86.51: bytes=32 time=270ms TTL=53 Ping statistics for 217.160.86.51: Packets: Sent = 15, Received = 15, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 268ms, Maximum = 271ms, Average = 269ms dunno what that ping for what site, just test for fun on unifi |
|
|
May 9 2024, 12:37 AM
|
|
Elite
8,409 posts Joined: Jul 2008
|
QUOTE(zerorating @ May 8 2024, 08:18 PM) and some people complaining high response time to twitter. Comparison of Unifi and TIME to twitter.com. It's kinda obvious which one got superior peering and routing.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 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, 12:55 AM
|
|
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:03 AM
Show posts by this member only | IPv6 | Post
#20
|
Senior Member
823 posts Joined: Jun 2005 From: 0:0:0:0:0:0:7f00:1
|
can confirm. twitter barely load on my pc, but for some reason on phone it works perfectly fine. already tried both google dns and open dns, same shit. been almost a week now...?
|
|
|
May 9 2024, 01:07 AM
|
|
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 fixedhttps://forum.lowyat.net/index.php?showtopi...ost&p=109048968 https://forum.lowyat.net/index.php?showtopi...ost&p=109071408 |
|
|
May 9 2024, 01:15 AM
|
|
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, 08:43 AM
Show posts by this member only | IPv6 | Post
#23
|
|
Senior Member
3,581 posts Joined: Oct 2007 From: everywhere in sabah
|
QUOTE(blacktubi @ May 9 2024, 12:26 AM) 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. the problem on TIME maybe temporaryTM 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. but the unifi routing problem has been like that for years and never resolved i'm not sure they even plan to resolve it it has always been bad at night, just that it's especially bad these few weeks |
|
|
May 9 2024, 10:46 AM
|
|
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.0200sec
 0.46
 5 queries
 GZIP Disabled
Time is now: 8th December 2025 - 06:36 AM |
All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)
Powered by Invision Power Board © 2025 IPS, Inc.