Kapankah Koneksi Internet Smartfren Normal Kembali? | KASKUS

Thread

For You

Hot Threads

Komunitas

Semua Komunitas

Kategori

Story

News

Hobby

Games

Entertainment

Female

Tech

Automotive

Sports

Food & Travel

Pengaturan

Gambar

Lainnya

Tentang KASKUS

Pusat Bantuan

Hubungi Kami

KASKUS Plus

© 2024 KASKUS, PT Darta Media Indonesia. All rights reserved

Beranda

...

Internet Service & Networking
Kapankah Koneksi Internet Smartfren Normal Kembali?

TS

hendriwijaya48

24-03-2013 11:01

Kapankah Koneksi Internet Smartfren Normal Kembali?

Dari kemarin siang hingga sekarang Smartfren melakukan maintenance (gangguan). Situs luar negeri seperti Google, Facebook, dan Twitter tidak bisa dibuka dan RTO (Request Timed Out) di Command Prompt. Sedangkan situs lokal seperti Kaskus, Indowebster, FastNCheap, Kompas, dan Detik masih bisa dibuka meskipun agak lama. Bahkan kemarin saya tidak bisa melakukan post/reply thread di Kaskus karena terkendala kode Captcha. Sudah menggunakan cara seperti mengganti DNS dan proxy dan menggunakan VPN (Virtual Private Network) tidak membuahkan hasil. Boro-boro mau melakukan Speedtest dan Pingtest, situsnya sendiri tidak bisa dibuka. Akibat masalah ini, saya merugi karena tertinggal info artikel terbaru dari situs kesayangan saya yang hostingnya berada di luar negeri. Sekarangpun, situs luar negeri sudah lancar kembali meskipun beberapa situs masih belum bisa diakses dan RTO. Dan apalagi saya harus bersiap menghadapi "densus" 64 Kbps karena perkiraan saya dalam waktu 5 hari FUP 2 GB/bulan pada paket Neo Regular Rp 49.000 akan habis yang juga akan mungkin memerlukan kesabaran yang ekstra tinggi jika membuka situs luar negeri.

Berikut ini hasil ping di Command Prompt baik situs luar maupun dalam negeri:

Spoiler for Google:

Pinging google.com [74.125.236.8] with 32 bytes of data:
Reply from 74.125.236.8: bytes=32 time=141ms TTL=52
Reply from 74.125.236.8: bytes=32 time=139ms TTL=52
Reply from 74.125.236.8: bytes=32 time=165ms TTL=52
Reply from 74.125.236.8: bytes=32 time=160ms TTL=52
Reply from 74.125.236.8: bytes=32 time=166ms TTL=52
Request timed out.
Request timed out.
Reply from 74.125.236.8: bytes=32 time=167ms TTL=52
Reply from 74.125.236.8: bytes=32 time=168ms TTL=52
Reply from 74.125.236.8: bytes=32 time=166ms TTL=52
Reply from 74.125.236.8: bytes=32 time=164ms TTL=52
Reply from 74.125.236.8: bytes=32 time=170ms TTL=52
Request timed out.
Reply from 74.125.236.8: bytes=32 time=146ms TTL=52
Request timed out.
Reply from 74.125.236.8: bytes=32 time=220ms TTL=52
Reply from 74.125.236.8: bytes=32 time=162ms TTL=52
Reply from 74.125.236.8: bytes=32 time=163ms TTL=52
Reply from 74.125.236.8: bytes=32 time=149ms TTL=52
Reply from 74.125.236.8: bytes=32 time=167ms TTL=52
Request timed out.
Reply from 74.125.236.8: bytes=32 time=161ms TTL=52
Reply from 74.125.236.8: bytes=32 time=164ms TTL=52
Request timed out.
Request timed out.
Reply from 74.125.236.8: bytes=32 time=164ms TTL=52
Request timed out.
Reply from 74.125.236.8: bytes=32 time=160ms TTL=52
Request timed out.
Reply from 74.125.236.8: bytes=32 time=170ms TTL=52
Request timed out.
Reply from 74.125.236.8: bytes=32 time=167ms TTL=52
Reply from 74.125.236.8: bytes=32 time=320ms TTL=52
Reply from 74.125.236.8: bytes=32 time=169ms TTL=52
Request timed out.

Ping statistics for 74.125.236.8:
Packets: Sent = 35, Received = 24, Lost = 11 (31% loss),
Approximate round trip times in milli-seconds:
Minimum = 139ms, Maximum = 320ms, Average = 170ms

Spoiler for Facebook:

Pinging facebook.com [173.252.110.27] with 32 bytes of data:
Reply from 173.252.110.27: bytes=32 time=304ms TTL=240
Reply from 173.252.110.27: bytes=32 time=319ms TTL=240
Reply from 173.252.110.27: bytes=32 time=323ms TTL=240
Reply from 173.252.110.27: bytes=32 time=321ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=384ms TTL=240
Reply from 173.252.110.27: bytes=32 time=322ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=316ms TTL=240
Reply from 173.252.110.27: bytes=32 time=354ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=320ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=320ms TTL=240
Reply from 173.252.110.27: bytes=32 time=320ms TTL=240
Reply from 173.252.110.27: bytes=32 time=323ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=320ms TTL=240
Request timed out.
Request timed out.
Reply from 173.252.110.27: bytes=32 time=324ms TTL=240
Reply from 173.252.110.27: bytes=32 time=321ms TTL=240
Request timed out.
Request timed out.
Reply from 173.252.110.27: bytes=32 time=322ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=321ms TTL=240
Reply from 173.252.110.27: bytes=32 time=318ms TTL=240
Reply from 173.252.110.27: bytes=32 time=317ms TTL=240
Reply from 173.252.110.27: bytes=32 time=323ms TTL=240
Reply from 173.252.110.27: bytes=32 time=312ms TTL=240
Request timed out.

Ping statistics for 173.252.110.27:
Packets: Sent = 32, Received = 21, Lost = 11 (34% loss),
Approximate round trip times in milli-seconds:
Minimum = 304ms, Maximum = 384ms, Average = 324ms

Spoiler for Twitter:

Pinging twitter.com [199.59.148.10] with 32 bytes of data:
Reply from 199.59.148.10: bytes=32 time=499ms TTL=49
Reply from 199.59.148.10: bytes=32 time=284ms TTL=49
Reply from 199.59.148.10: bytes=32 time=288ms TTL=49
Reply from 199.59.148.10: bytes=32 time=280ms TTL=49
Reply from 199.59.148.10: bytes=32 time=284ms TTL=49
Reply from 199.59.148.10: bytes=32 time=282ms TTL=49
Reply from 199.59.148.10: bytes=32 time=286ms TTL=49
Reply from 199.59.148.10: bytes=32 time=281ms TTL=49
Reply from 199.59.148.10: bytes=32 time=282ms TTL=49
Reply from 199.59.148.10: bytes=32 time=284ms TTL=49
Reply from 199.59.148.10: bytes=32 time=282ms TTL=49
Reply from 199.59.148.10: bytes=32 time=284ms TTL=49
Reply from 199.59.148.10: bytes=32 time=282ms TTL=49
Reply from 199.59.148.10: bytes=32 time=461ms TTL=49
Reply from 199.59.148.10: bytes=32 time=279ms TTL=49
Reply from 199.59.148.10: bytes=32 time=279ms TTL=49
Reply from 199.59.148.10: bytes=32 time=283ms TTL=49
Reply from 199.59.148.10: bytes=32 time=283ms TTL=49
Reply from 199.59.148.10: bytes=32 time=292ms TTL=49
Reply from 199.59.148.10: bytes=32 time=283ms TTL=49
Reply from 199.59.148.10: bytes=32 time=281ms TTL=49
Reply from 199.59.148.10: bytes=32 time=282ms TTL=49
Reply from 199.59.148.10: bytes=32 time=282ms TTL=49
Reply from 199.59.148.10: bytes=32 time=325ms TTL=49
Reply from 199.59.148.10: bytes=32 time=282ms TTL=49
Reply from 199.59.148.10: bytes=32 time=278ms TTL=49
Reply from 199.59.148.10: bytes=32 time=287ms TTL=49
Reply from 199.59.148.10: bytes=32 time=280ms TTL=49
Reply from 199.59.148.10: bytes=32 time=357ms TTL=49
Reply from 199.59.148.10: bytes=32 time=278ms TTL=49
Reply from 199.59.148.10: bytes=32 time=281ms TTL=49
Reply from 199.59.148.10: bytes=32 time=281ms TTL=49
Reply from 199.59.148.10: bytes=32 time=286ms TTL=49

Ping statistics for 199.59.148.10:
Packets: Sent = 33, Received = 33, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 278ms, Maximum = 499ms, Average = 298ms

Spoiler for Kaskus:

Pinging kaskus.co.id [202.158.17.149] with 32 bytes of data:
Reply from 202.158.17.149: bytes=32 time=59ms TTL=54
Reply from 202.158.17.149: bytes=32 time=58ms TTL=54
Reply from 202.158.17.149: bytes=32 time=61ms TTL=54
Reply from 202.158.17.149: bytes=32 time=58ms TTL=54
Reply from 202.158.17.149: bytes=32 time=64ms TTL=54
Reply from 202.158.17.149: bytes=32 time=61ms TTL=54
Reply from 202.158.17.149: bytes=32 time=60ms TTL=54
Reply from 202.158.17.149: bytes=32 time=81ms TTL=54
Reply from 202.158.17.149: bytes=32 time=59ms TTL=54

Ping statistics for 202.158.17.149:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 81ms, Average = 62ms

Spoiler for Indowebster:

Pinging indowebster.com [175.103.59.110] with 32 bytes of data:
Reply from 175.103.59.110: bytes=32 time=43ms TTL=55
Reply from 175.103.59.110: bytes=32 time=64ms TTL=55
Reply from 175.103.59.110: bytes=32 time=63ms TTL=55
Reply from 175.103.59.110: bytes=32 time=60ms TTL=55
Reply from 175.103.59.110: bytes=32 time=56ms TTL=55
Reply from 175.103.59.110: bytes=32 time=64ms TTL=55
Reply from 175.103.59.110: bytes=32 time=65ms TTL=55

Ping statistics for 175.103.59.110:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 65ms, Average = 59ms

Dari banyak hasil ping di atas, hanya Twitter yang tidak ada RTO di situs luar negeri.

So, jika kamu sudah terlanjur menggunakan modem Smartfren. Jika modem tersebut unlock, silakan ganti kartu dengan Flexi atau provider CDMA lain untuk internet lebih cepat. Sedangkan jika kamu akan berniat akan membeli modem Smartfren, sebaiknya diurungkan saja niatnya agar tidak menyesal di kemudian hari.
Saya juga akan berencana menggunakan LAN (Local Area Connection) kabel TelkomSpeedy karena kondisi modem Smartfren AC682 saya unlock dan tidak memungkinkan untuk diganti dengan kartu CDMA yang lain.

UPDATE!!!
Dari Facebook smartfrendan Twitter @smartfrenworld:

"Bro n Sis, saat ini kami mengalami penurunan layanan data dikarenakan gangguan sistem. Saat ini kami sedang melakukan pemulihan layanan data secepatnya. Mimin mohon maaf atas ketidaknyamanannya. Terimakasih. "

Untuk sementara bisa menggunakan proxy 222.124.185.90 dan port 6666. punya ane udah lancar pake proxy ini.

Diubah oleh hendriwijaya48 25-03-2013 08:02

0

3.5K

Kutip

23

Balasan

Guest

Tulis komentar menarik atau mention replykgpt untuk ngobrol seru

Mari bergabung, dapatkan informasi dan teman baru!

Internet Service & Networking

21.3KThread•3.9KAnggota

Terlama

Guest

Tulis komentar menarik atau mention replykgpt untuk ngobrol seru