Koneksi Internet Smartfren Lumpuh Total Sabtu Ini!

Beranda
Komunitas
Tech
Internet Service & Networking
Koneksi Internet Smartfren Lumpuh Total Sabtu Ini!

hendriwijaya48

23-03-2013 13:06

Koneksi Internet Smartfren Lumpuh Total Sabtu Ini!

Adakah yang mengalami hal yang sama seperti saya? Dari pukul 14.30 WIB situs luar negeri tidak bisa diakses. Hanya situs lokal saja saya yang bisa diakses. Thread ini aja baru saya buat sekarang karena kode Captcha tidak muncul pada saat Smartfren gangguan tadi. Facebook aja sekarang nunggu 5 menit baru bisa terbuka. Ping situs luar aja sekarang sering RTO emoticon-Mad (S)

Ane tinggal di Rawa Buaya, Cengkareng, Jakarta Barat.
BENAR-BENAR KESAL DENGAN PROVIDER SAMPAH INI! emoticon-Mad (S)

UPDATE!!!

Spoiler for Ping Google di Command Prompt:

(Diambil pada Minggu, 24 Maret 2013 pukul 12.15 WIB)

Spoiler for Statisik (Smartfren Connex AC682 UI):

Diambil pada Minggu, 24 Maret 2013 pukul 12.27 WIB)

Spoiler for Ping Google, Facebook, dan Kaskus di Command Prompt (13.56 WIB):

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\HENDRY>ping google.com -t & ping facebook.com -t & ping kaskus.co.id -t

Pinging google.com [74.125.236.136] with 32 bytes of data:
Reply from 74.125.236.136: bytes=32 time=155ms TTL=52
Reply from 74.125.236.136: bytes=32 time=163ms TTL=52
Reply from 74.125.236.136: bytes=32 time=160ms TTL=52
Reply from 74.125.236.136: bytes=32 time=149ms TTL=52
Request timed out.
Request timed out.
Reply from 74.125.236.136: bytes=32 time=602ms TTL=45
Reply from 74.125.236.136: bytes=32 time=553ms TTL=48
Reply from 74.125.236.136: bytes=32 time=554ms TTL=48
Reply from 74.125.236.136: bytes=32 time=551ms TTL=48
Reply from 74.125.236.136: bytes=32 time=556ms TTL=48
Reply from 74.125.236.136: bytes=32 time=554ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.236.136: bytes=32 time=183ms TTL=49
Reply from 74.125.236.136: bytes=32 time=146ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.236.136: bytes=32 time=156ms TTL=52
Reply from 74.125.236.136: bytes=32 time=157ms TTL=52
Request timed out.
Reply from 74.125.236.136: bytes=32 time=149ms TTL=52
Reply from 74.125.236.136: bytes=32 time=236ms TTL=52
Reply from 74.125.236.136: bytes=32 time=146ms TTL=52
Reply from 74.125.236.136: bytes=32 time=148ms TTL=52
Reply from 74.125.236.136: bytes=32 time=147ms TTL=52
Reply from 74.125.236.136: bytes=32 time=151ms TTL=52
Reply from 74.125.236.136: bytes=32 time=180ms TTL=52
Reply from 74.125.236.136: bytes=32 time=150ms TTL=52
Reply from 74.125.236.136: bytes=32 time=142ms TTL=52
Reply from 74.125.236.136: bytes=32 time=165ms TTL=52
Reply from 74.125.236.136: bytes=32 time=149ms TTL=52
Request timed out.
Reply from 74.125.236.136: bytes=32 time=168ms TTL=52
Reply from 74.125.236.136: bytes=32 time=165ms TTL=52
Reply from 74.125.236.136: bytes=32 time=162ms TTL=52

Ping statistics for 74.125.236.136:
Packets: Sent = 39, Received = 28, Lost = 11 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 142ms, Maximum = 602ms, Average = 246ms
Control-C
^C
Pinging facebook.com [173.252.110.27] with 32 bytes of data:
Reply from 173.252.110.27: bytes=32 time=702ms TTL=237
Reply from 173.252.110.27: bytes=32 time=726ms TTL=237
Reply from 173.252.110.27: bytes=32 time=722ms TTL=237
Reply from 173.252.110.27: bytes=32 time=718ms TTL=237
Reply from 173.252.110.27: bytes=32 time=816ms TTL=237
Reply from 173.252.110.27: bytes=32 time=720ms TTL=237
Reply from 173.252.110.27: bytes=32 time=716ms TTL=237
Reply from 173.252.110.27: bytes=32 time=742ms TTL=237
Reply from 173.252.110.27: bytes=32 time=406ms TTL=237
Reply from 173.252.110.27: bytes=32 time=450ms TTL=237
Reply from 173.252.110.27: bytes=32 time=530ms TTL=237
Reply from 173.252.110.27: bytes=32 time=600ms TTL=237
Reply from 173.252.110.27: bytes=32 time=670ms TTL=237
Reply from 173.252.110.27: bytes=32 time=715ms TTL=237
Reply from 173.252.110.27: bytes=32 time=713ms TTL=237
Reply from 173.252.110.27: bytes=32 time=710ms TTL=237
Reply from 173.252.110.27: bytes=32 time=718ms TTL=237
Reply from 173.252.110.27: bytes=32 time=736ms TTL=237
Reply from 173.252.110.27: bytes=32 time=326ms TTL=240
Reply from 173.252.110.27: bytes=32 time=330ms TTL=240
Reply from 173.252.110.27: bytes=32 time=425ms TTL=240
Reply from 173.252.110.27: bytes=32 time=334ms TTL=240
Reply from 173.252.110.27: bytes=32 time=325ms TTL=240
Reply from 173.252.110.27: bytes=32 time=328ms TTL=240
Reply from 173.252.110.27: bytes=32 time=324ms TTL=240
Reply from 173.252.110.27: bytes=32 time=336ms TTL=240
Request timed out.
Request timed out.
Reply from 173.252.110.27: bytes=32 time=329ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=328ms TTL=240
Reply from 173.252.110.27: bytes=32 time=331ms TTL=240
Request timed out.
Reply from 173.252.110.27: bytes=32 time=325ms TTL=240
Reply from 173.252.110.27: bytes=32 time=328ms TTL=240
Reply from 173.252.110.27: bytes=32 time=327ms TTL=240
Reply from 173.252.110.27: bytes=32 time=331ms TTL=240
Reply from 173.252.110.27: bytes=32 time=327ms TTL=240

Ping statistics for 173.252.110.27:
Packets: Sent = 38, Received = 34, Lost = 4 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 324ms, Maximum = 816ms, Average = 513ms
Control-C
^C
Pinging kaskus.co.id [202.158.17.149] with 32 bytes of data:
Reply from 202.158.17.149: bytes=32 time=50ms TTL=54
Reply from 202.158.17.149: bytes=32 time=67ms TTL=54
Reply from 202.158.17.149: bytes=32 time=56ms TTL=54
Reply from 202.158.17.149: bytes=32 time=70ms TTL=54
Reply from 202.158.17.149: bytes=32 time=61ms TTL=54
Reply from 202.158.17.149: bytes=32 time=138ms TTL=54
Reply from 202.158.17.149: bytes=32 time=61ms TTL=54
Reply from 202.158.17.149: bytes=32 time=64ms TTL=54
Reply from 202.158.17.149: bytes=32 time=57ms TTL=54
Reply from 202.158.17.149: bytes=32 time=61ms TTL=54
Reply from 202.158.17.149: bytes=32 time=201ms TTL=54
Reply from 202.158.17.149: bytes=32 time=63ms TTL=54
Reply from 202.158.17.149: bytes=32 time=59ms TTL=54
Reply from 202.158.17.149: bytes=32 time=65ms TTL=54
Reply from 202.158.17.149: bytes=32 time=62ms TTL=54
Reply from 202.158.17.149: bytes=32 time=65ms TTL=54
Reply from 202.158.17.149: bytes=32 time=58ms TTL=54
Reply from 202.158.17.149: bytes=32 time=63ms TTL=54
Reply from 202.158.17.149: bytes=32 time=59ms TTL=54
Reply from 202.158.17.149: bytes=32 time=61ms TTL=54
Reply from 202.158.17.149: bytes=32 time=67ms TTL=54
Reply from 202.158.17.149: bytes=32 time=56ms TTL=54
Reply from 202.158.17.149: bytes=32 time=60ms TTL=54
Reply from 202.158.17.149: bytes=32 time=65ms TTL=54
Reply from 202.158.17.149: bytes=32 time=61ms TTL=54

Ping statistics for 202.158.17.149:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 201ms, Average = 70ms
Control-C
^C
C:\Users\HENDRY>

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:04

3.6K

Kutip

Balasan

Guest

Tulis komentar menarik atau mention replykgpt untuk ngobrol seru

Urutan

Terbaru

Terlama

Guest

Tulis komentar menarik atau mention replykgpt untuk ngobrol seru

Komunitas Pilihan