Indihome PING Hancur

[faridm]

Memang aneh, tp nyata adanya.
Server lokal dg BW 1Gbps (shared).
Tp download pake Indihome lambat.
Sementara server SG, download dr sana malah jauh lebih cepat.

 

[faridm]

Untuk koneksi Indihome hampir hancur semua karena port telkom di IIX dan OpenIX sudah full

Kalau NCIX gmn?

 

[natanetwork]

Kalau NCIX gmn?

sudah full jg terkadang.. jadi bisa pakai peer telkom

hasilnya mayan oke sih :

 

[morpig]

kok yang bersahabat malah adeknya yg 23693 ya? port di iix 100g.. skrg ada di jktix pula

 

[dhyhost]

Kalau NCIX gmn?

sama full juga,
penyedia server disuruh join ke ncix, bayar mayan mahal, eh penuh juga.

 

[kutubuku]

Coba ditracert hasilnya gimana?

Biznet
ping 103.150.xxx.xxx

Pinging 103.150.xxx.xxx with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 103.150.xxx.xxx: bytes=32 time=157ms TTL=56
Reply from 103.150.xxx.xxx: bytes=32 time=149ms TTL=56

Ping statistics for 103.150.xxx.xxx:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 149ms, Maximum = 157ms, Average = 153ms

tracert 103.150..xxx.xxx

Tracing route to xxx.wjv-1.biznetg.io [103.150.xxx.xxx]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1560 ms 1624 ms 1763 ms 10.45.0.1
3 4 ms 3 ms 3 ms 125.160.0.29
4 14 ms 13 ms 13 ms 218.100.36.56
5 * * * Request timed out.
6 209 ms 211 ms 207 ms 218.100.36.118
7 170 ms 178 ms 186 ms ip-122-127-59-137.core.biznetg.io [137.59.127.122]
8 192 ms * * ip-162-127-59-137.core.biznetg.io [137.59.127.162]
9 * 197 ms 188 ms xxx.wjv-1.biznetg.io [103.150.xxx.xxx]

ConnectIndo
ping 103.77.xxx.xxx

Pinging 103.77.xxx.xxx with 32 bytes of data:
Reply from 103.77.xxx.xxx: bytes=32 time=188ms TTL=57
Reply from 103.77.xxx.xxx: bytes=32 time=201ms TTL=57
Reply from 103.77.xxx.xxx: bytes=32 time=168ms TTL=57
Reply from 103.77.xxx.xxx: bytes=32 time=204ms TTL=57

Ping statistics for 103.77.xxx.xxx:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 204ms, Average = 190ms

tracert 103.77.xxx.xxx

Tracing route to xxx.xxx.azcore.web.id [103.77.xxx.xxx]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1541 ms 1391 ms * 10.45.0.1
3 4 ms 5 ms 7 ms 125.160.0.29
4 14 ms 13 ms 18 ms 218.100.36.56
5 * * * Request timed out.
6 158 ms 173 ms * bsti.openixp.net [218.100.27.181]
7 * 237 ms 216 ms 70.236.65.in-addr.arpa [103.65.236.70]
8 170 ms 161 ms 145 ms xxx.xxx.azcore.web.id [103.77.xxx.xxx]

ping dan tracert dilakukan pada jam 9:36 malam (12/14/22)

saya coba ping dan tracert ke vps saya yg di SG
ping 103.166.xxx.xxx

Pinging 103.166.xxx.xxx with 32 bytes of data:
Reply from 103.166.xxx.xxx: bytes=32 time=28ms TTL=57
Reply from 103.166.xxx.xxx: bytes=32 time=27ms TTL=57
Reply from 103.166.xxx.xxx: bytes=32 time=34ms TTL=57
Reply from 103.166.xxx.xxx: bytes=32 time=28ms TTL=57

Ping statistics for 103.166.xxx.xxx:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 34ms, Average = 29ms
tracert 103.166.xxx.xxx

Tracing route to xxx.xxx.speedyvps.uk [103.166.xxx.xxx]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 * 1408 ms * 10.45.0.1
3 4 ms 4 ms 4 ms 125.160.0.29
4 * * * Request timed out.
5 * * 27 ms 109.190.240.180.in-addr.arpa [180.240.190.109]
6 28 ms 29 ms 29 ms 53.204.240.180.in-addr.arpa [180.240.204.53]
7 30 ms 30 ms 30 ms core.sg3.sg.hostuniversal.com.au [103.216.222.17]
8 28 ms 28 ms 27 ms core.rc.sg.hostuniversal.com.au [103.216.222.16]
9 28 ms 28 ms 28 ms xxx.xxx.speedyvps.uk [103.166.xxx.xxx]

 

[kutubuku]

untuk spesifikasi VPS yang di singapura dengan yang di indonesia apakah sama pak?

berbeda sih pak. apakah dari spek VPS juga berpengaruh besar pak ?

Biznet

• MS 4.2
• 4 GB RAM
• 2 vCPU
• 60 GB Disk
• Centos-7

ConnectIndo

40 GB SSD NVMe

3 GB DDR4

2 Cores >3.5 GHz

SG

2 Cores

4 GB DDR4

60 GB

 

[kutubuku]

kapasitas telkom lbh besar* di exchange SG drpd jkt. makanya kdg lebih bagus dari sisi latency sm bandwidth.

lucu ya, tapi ya ketawain aja

siap pak, terimakasih penjelasannya. sayang banget disini ISP yg masuk cuma punya indihome doank. pingin pindah ke yg lain tapi belum ada jaringannya.

 

[kutubuku]

musti ambil dr provider yg sudah peering sama telkom

nyarinya susah2 gampang ini pak. hehe.
ya saya kira ketika vps dengan server di indonesia, jika di ping dari semua ISP di Indonesia hasilnya akan bagus juga.
namun ternyata tidak untuk indihome ini. emang agak aneh ini ISP. ke lokal ping tinggi, ke SG ping malah imut dan stabil.

 

[meAtharva]

Full om, coba komplain ke Telkom/Indihome hehe.