Rf Online private server :
1. RF POA (Rfpoa.com)
2. RF-RELAX (Relax-RF.com)
RO Private Server
1. AERO (Aerogaming.com)
2. XileRO (Xilero.com)
segera menyusul :
Lineage2 Private Server : Kameo L2
begitu kata operator 147, yang mengakibatkan speedy sumatera untuk link ke international sering RTO…. ??
benar ngga’ sihhh ?
user spididudut, hm.. kalo nurut gwa yah.. kalo pelanggan speedy complain… ke mereka.. jawaban mereka hanya gini.. coba cek kembali lan bapak ato modem bapak.. mgkn di sana ada kendalanya… lalu kalo sekarang PING ke internasional nya aja sering RTO kalo wnet browsing its ok lah.. tp kalo wnet gamenet? langsung DC dr game…. dan tahu jawaban complain nya? mgkn computer bapak kena VIRUS… “Tanya” begitu kah layanan speedy sekarang? telkom mmg milik BUMN.. cuman pelanggan kan harus jg di layani dengan sebaiknya.. kalo begini jawaban complain nya ANAK KECIL PUN BISA
otong, nasib….kita ditakdirkan sebagai wni. nasib….. beginilah resiko menjadi warga negara indonesia. keringat dan darah kita dihisap habis-habisan. boro-boro ngasih kompensasi….mimpi kali !!!!!!
user speedy, Dalam perjanjian kontrak speedy antara telkom dan pelanggan ada yang disebut SLG. Service Level Guarantee (SLG) adalah kepastian layanan yang diberikan Telkom kepada Pelanggan, dan Kompensasi adalah kewajiban Telkom yang menjadi hak Pelanggan apabila SLG tidak terpenuhi. Telkom akan memberikan Kompensasi kepada Pelanggan sesuai dengan yang ditentukan dalam SLG, atas tidak berfungsinya Sambungan Telekomunikasi akibat kerusakan atau gangguan yang terjadi di jaringan telekomunikasi milik Telkom dengan syarat bahwa kerusakan atau gangguan tersebut tidak disebabkan oleh kesalahan Pelanggan. Gugat saja telkom dengan pasal itu… (Rame-rame yukkkk !!)
MPOES, Gak apa lah.. kita maafin aja ya.. Nanti klo kita gak bayar tagihan Speedy selama 6 bulan kan kita jadinya masih punya cadangan “Maaf”: “MAAF SAYA BELUM BISA MEMBAYAR TAGIHAN 6 BULAN INI, SEMUA ITU DILUAR KENDALI SAYA” Betul toh….
andi, telkom… yang kerja di situ orang2nya…. pada mau kaya semua…. semoga telkom pailit……… tidak bisa berjalan lagi….. semua sahamnya semoga di jula kepada pihak lain yang lebih bertanggung jawab….. perusahaan negara ya seperti inilah contoh semua…. kalau pelanggan yang salh aja tindakannya gila-gilaan, kalau operator yang salh cuma bisa minta maaf…. makan aja itu maaf buat bapak2….. semoga telkom pailit… korupsi habis uang telkom
sumber : komentar (detik.com)
Jakarta – PT Telkom akhirnya memutuskan untuk tidak memberikan kompensasi apapun bagi korban tumbangnya koneksi internasional Speedy yang terjadi beberapa waktu lalu. Sekali lagi, Telkom hanya minta maaf.
VP Public and Marketing Communication Telkom, Eddy Kurnia beralasan, kompensasi tersebut ditiadakan karena gangguan yang terjadi diluar kendali Telkom.
“Gangguan itu diluar kendali kami, karena ada pembangunan fly-over. Tetapi kita juga tidak bisa menyalahkan pihak yang melakukan pembangunan fly-over itu karena pembangunan itu pun sedang berjalan,” kilahnya kepada detikINET, Rabu (12/3/2008).
Dilanjutkan Eddy, kerusakan itu sendiri kini sudah kembali normal setelah mengalami perbaikan selama kurang lebih 20 jam.
“Namun atas kejadian tersebut, yang pertama kami ingin meminta maaf. Kejadian itu memang diluar kendali dan upaya kontingensi plan-nya juga sudah dilakukan semua,” imbuhnya.
Seperti diketahui, pada Jumat (29/2/2008) akses internet internasional milik Telkom di link Sumatera terputus. Akibatnya, pelanggan Speedy dan TelkomNet Instant harus gigit jari karena akses internet mereka terganggu.
Dampaknya, sebagian besar bisnis warnet di Indonesia yang menggantungkan nasib koneksinya melalui Telkom Speedy ikut menggelepar karena pelanggan mereka pada kabur tidak bisa surfing ke situs luar negeri.
( ash / dbu )
sudah mulai membaikkkah ?
pagi 13/03/2008 jam8:48 wib :
Reply from 216.109.112.135: bytes=32 time=336ms TTL=46
Reply from 216.109.112.135: bytes=32 time=332ms TTL=48
Reply from 216.109.112.135: bytes=32 time=342ms TTL=46
Reply from 216.109.112.135: bytes=32 time=359ms TTL=46
Reply from 216.109.112.135: bytes=32 time=356ms TTL=46
Reply from 216.109.112.135: bytes=32 time=322ms TTL=48
Reply from 216.109.112.135: bytes=32 time=351ms TTL=46
Reply from 216.109.112.135: bytes=32 time=347ms TTL=46
Reply from 216.109.112.135: bytes=32 time=345ms TTL=46
Reply from 216.109.112.135: bytes=32 time=320ms TTL=48
Reply from 216.109.112.135: bytes=32 time=335ms TTL=46
Reply from 216.109.112.135: bytes=32 time=332ms TTL=46
Reply from 216.109.112.135: bytes=32 time=361ms TTL=46
Reply from 216.109.112.135: bytes=32 time=348ms TTL=46
Reply from 216.109.112.135: bytes=32 time=321ms TTL=48
Reply from 216.109.112.135: bytes=32 time=336ms TTL=46
Reply from 216.109.112.135: bytes=32 time=351ms TTL=46
Reply from 216.109.112.135: bytes=32 time=336ms TTL=46
Reply from 216.109.112.135: bytes=32 time=338ms TTL=48
Reply from 216.109.112.135: bytes=32 time=362ms TTL=46
Reply from 216.109.112.135: bytes=32 time=330ms TTL=46
Reply from 216.109.112.135: bytes=32 time=343ms TTL=46
Reply from 216.109.112.135: bytes=32 time=327ms TTL=48
Reply from 216.109.112.135: bytes=32 time=350ms TTL=46
…. udah 3 jam menunggu belum ada rto….
ini berkat usaha nelpon 147 selama 1 week tanpa lelah…moga2 kedepannya tetap oke.
ping ke yahoo terputus2 kenapa tidak ada yang lapor ????!!!!
Reply from 216.109.112.135: bytes=32 time=330ms TTL=48
Reply from 216.109.112.135: bytes=32 time=315ms TTL=48
Reply from 216.109.112.135: bytes=32 time=357ms TTL=47
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.109.112.135: bytes=32 time=357ms TTL=38
Reply from 216.109.112.135: bytes=32 time=364ms TTL=38
Reply from 216.109.112.135: bytes=32 time=383ms TTL=37
Reply from 216.109.112.135: bytes=32 time=393ms TTL=35
Reply from 216.109.112.135: bytes=32 time=364ms TTL=38
Reply from 216.109.112.135: bytes=32 time=359ms TTL=35
Reply from 216.109.112.135: bytes=32 time=433ms TTL=36
Reply from 216.109.112.135: bytes=32 time=435ms TTL=37
Reply from 216.109.112.135: bytes=32 time=411ms TTL=38
…..warnet lain tidak ada yang lapor, warnet anda saja yang lapor ….? begitulah kata teknisi speedy….
….saya lah yang mewakili warnet lain…..!!!. saya sudah lapor ini sejak jumat lalu…
Selamat menikmati :
Date: 03/05 02:06:20 Name: (portscan) TCP Portsweep
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 202.149.64.182:n/a
References: none found
Date: 03/05 02:11:08 Name: (http_inspect) IIS UNICODE CODEPOINT ENCODING
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:36710 -> 202.190.75.8:80
References: none found
Date: 03/05 02:11:08 Name: (http_inspect) OVERSIZE REQUEST-URI DIRECTORY
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:36710 -> 202.190.75.8:80
References: none found
Date: 03/05 02:16:12 Name: MS-SQL Worm propagation attempt
Priority: 2 Type: Misc Attack
IP info: 220.191.239.178:61345 -> 125.162.xxx.xxx:1434
References: 1 2 3 4 5
Date: 03/05 02:16:12 Name: MS-SQL version overflow attempt
Priority: 3 Type: Misc activity
IP info: 220.191.239.178:61345 -> 125.162.xxx.xxx:1434
References: 1 2 3 4
Date: 03/05 02:46:04 Name: MS-SQL Worm propagation attempt
Priority: 2 Type: Misc Attack
IP info: 202.103.11.41:1267 -> 125.162.xxx.xxx:1434
References: 1 2 3 4 5
Date: 03/05 02:46:04 Name: MS-SQL version overflow attempt
Priority: 3 Type: Misc activity
IP info: 202.103.11.41:1267 -> 125.162.xxx.xxx:1434
References: 1 2 3 4
Date: 03/05 04:08:43 Name: MS-SQL Worm propagation attempt
Priority: 2 Type: Misc Attack
IP info: 202.103.180.105:1866 -> 125.162.xxx.xxx:1434
References: 1 2 3 4 5
Date: 03/05 04:08:43 Name: MS-SQL version overflow attempt
Priority: 3 Type: Misc activity
IP info: 202.103.180.105:1866 -> 125.162.xxx.xxx:1434
References: 1 2 3 4
Date: 03/05 07:52:38 Name: MS-SQL Worm propagation attempt
Priority: 2 Type: Misc Attack
IP info: 61.181.255.106:1317 -> 125.162.xxx.xxx:1434
References: 1 2 3 4 5
Date: 03/05 07:52:38 Name: MS-SQL version overflow attempt
Priority: 3 Type: Misc activity
IP info: 61.181.255.106:1317 -> 125.162.xxx.xxx:1434
References: 1 2 3 4
Date: 03/05 10:56:44 Name: MS-SQL Worm propagation attempt
Priority: 2 Type: Misc Attack
IP info: 220.191.233.133:41661 -> 125.162.xxx.xxx:1434
References: 1 2 3 4 5
Date: 03/05 10:56:44 Name: MS-SQL version overflow attempt
Priority: 3 Type: Misc activity
IP info: 220.191.233.133:41661 -> 125.162.xxx.xxx:1434
References: 1 2 3 4
Date: 03/05 11:17:25 Name: MS-SQL Worm propagation attempt
Priority: 2 Type: Misc Attack
IP info: 218.64.237.219:2785 -> 125.162.xxx.xxx:1434
References: 1 2 3 4 5
Date: 03/05 11:17:25 Name: MS-SQL version overflow attempt
Priority: 3 Type: Misc activity
IP info: 218.64.237.219:2785 -> 125.162.xxx.xxx:1434
References: 1 2 3 4
Date: 03/05 15:11:05 Name: (portscan) TCP Portsweep
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 61.247.12.18:n/a
References: none found
Date: 03/05 15:11:40 Name: (portscan) TCP Portscan
Priority: n/a Type: n/a
IP info: 202.6.231.130:n/a -> 125.162.xxx.xxx:n/a
References: none found
Date: 03/05 15:12:08 Name: (portscan) TCP Portsweep
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 192.168.100.254:n/a
References: none found
Date: 03/05 15:13:09 Name: (portscan) TCP Portsweep
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 192.168.100.254:n/a
References: none found
Date: 03/05 15:14:11 Name: (portscan) TCP Portsweep
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 192.168.100.254:n/a
References: none found
Date: 03/05 16:17:48 Name: (portscan) TCP Portsweep
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 203.142.83.195:n/a
References: none found
Date: 03/05 17:42:38 Name: (http_inspect) IIS UNICODE CODEPOINT ENCODING
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:39973 -> 202.190.75.8:80
References: none found
Date: 03/05 17:42:39 Name: (http_inspect) OVERSIZE REQUEST-URI DIRECTORY
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:39973 -> 202.190.75.8:80
References: none found
Date: 03/05 18:02:46 Name: (portscan) TCP Portsweep
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 75.125.122.98:n/a
References: none found
Date: 03/05 18:03:02 Name: (portscan) TCP Portscan
Priority: n/a Type: n/a
IP info: 125.162.xxx.xxx:n/a -> 75.125.122.98:n/a
References: none found
begitu banyaknya masalah… harus pilih2 firewall & modem yang cocok untuk speedy anda.
bagusnya kalo pagi… masih segar :
64 bytes from 202.134.0.155: icmp_seq=1172 ttl=58 time=90.7 ms
64 bytes from 202.134.0.155: icmp_seq=1173 ttl=58 time=83.9 ms
64 bytes from 202.134.0.155: icmp_seq=1174 ttl=58 time=69.6 ms
64 bytes from 202.134.0.155: icmp_seq=1175 ttl=58 time=72.8 ms
64 bytes from 202.134.0.155: icmp_seq=1176 ttl=58 time=72.9 ms
64 bytes from 202.134.0.155: icmp_seq=1177 ttl=58 time=68.4 ms
64 bytes from 202.134.0.155: icmp_seq=1178 ttl=58 time=70.5 ms
64 bytes from 202.134.0.155: icmp_seq=1179 ttl=58 time=71.7 ms
64 bytes from 202.134.0.155: icmp_seq=1180 ttl=58 time=72.7 ms
64 bytes from 202.134.0.155: icmp_seq=1181 ttl=58 time=87.7 ms
64 bytes from 202.134.0.155: icmp_seq=1182 ttl=58 time=71.9 ms
64 bytes from 202.134.0.155: icmp_seq=1183 ttl=58 time=75.9 ms
64 bytes from 202.134.0.155: icmp_seq=1184 ttl=58 time=71.9 ms
64 bytes from 202.134.0.155: icmp_seq=1185 ttl=58 time=71.9 ms
64 bytes from 202.134.0.155: icmp_seq=1186 ttl=58 time=73.4 ms
64 bytes from 202.134.0.155: icmp_seq=1187 ttl=58 time=73.6 ms
64 bytes from 202.134.0.155: icmp_seq=1188 ttl=58 time=68.9 ms
ping ke yahoo…. normal kah ? atau masih pagi…so..oke2 saja.
64 bytes from 216.109.112.135: icmp_seq=29 ttl=48 time=346 ms
64 bytes from 216.109.112.135: icmp_seq=30 ttl=49 time=324 ms
64 bytes from 216.109.112.135: icmp_seq=31 ttl=49 time=325 ms
64 bytes from 216.109.112.135: icmp_seq=32 ttl=48 time=360 ms
64 bytes from 216.109.112.135: icmp_seq=33 ttl=48 time=347 ms
64 bytes from 216.109.112.135: icmp_seq=34 ttl=48 time=334 ms
64 bytes from 216.109.112.135: icmp_seq=35 ttl=48 time=343 ms
64 bytes from 216.109.112.135: icmp_seq=36 ttl=48 time=361 ms
64 bytes from 216.109.112.135: icmp_seq=37 ttl=48 time=326 ms
64 bytes from 216.109.112.135: icmp_seq=38 ttl=49 time=325 ms
64 bytes from 216.109.112.135: icmp_seq=39 ttl=48 time=337 ms
64 bytes from 216.109.112.135: icmp_seq=40 ttl=48 time=351 ms
64 bytes from 216.109.112.135: icmp_seq=41 ttl=49 time=330 ms
64 bytes from 216.109.112.135: icmp_seq=42 ttl=48 time=349 ms
64 bytes from 216.109.112.135: icmp_seq=43 ttl=48 time=339 ms
64 bytes from 216.109.112.135: icmp_seq=44 ttl=48 time=358 ms
64 bytes from 216.109.112.135: icmp_seq=45 ttl=48 time=326 ms
64 bytes from 216.109.112.135: icmp_seq=46 ttl=48 time=350 ms
64 bytes from 216.109.112.135: icmp_seq=47 ttl=48 time=332 ms
64 bytes from 216.109.112.135: icmp_seq=48 ttl=49 time=355 ms
64 bytes from 216.109.112.135: icmp_seq=49 ttl=49 time=357 ms
64 bytes from 216.109.112.135: icmp_seq=50 ttl=48 time=359 ms
mudah2an kedepannya tetap sama..ini mungkin karena kegigihan saya lapor ke 147, den kepada Bpk.Joko. thx dech….
koneksi ke IIX udah mulai sembuh :
Reply from 202.134.0.155: bytes=32 time=66ms TTL=57
Reply from 202.134.0.155: bytes=32 time=77ms TTL=57
Reply from 202.134.0.155: bytes=32 time=63ms TTL=57
Reply from 202.134.0.155: bytes=32 time=66ms TTL=57
Reply from 202.134.0.155: bytes=32 time=67ms TTL=57
Reply from 202.134.0.155: bytes=32 time=63ms TTL=57
Reply from 202.134.0.155: bytes=32 time=64ms TTL=57
Reply from 202.134.0.155: bytes=32 time=66ms TTL=57
Reply from 202.134.0.155: bytes=32 time=70ms TTL=57
Reply from 202.134.0.155: bytes=32 time=62ms TTL=57
Reply from 202.134.0.155: bytes=32 time=75ms TTL=57
Reply from 202.134.0.155: bytes=32 time=71ms TTL=57
Reply from 202.134.0.155: bytes=32 time=67ms TTL=57
Reply from 202.134.0.155: bytes=32 time=67ms TTL=57
Reply from 202.134.0.155: bytes=32 time=83ms TTL=57
Reply from 202.134.0.155: bytes=32 time=83ms TTL=57
Reply from 202.134.0.155: bytes=32 time=65ms TTL=57
Reply from 202.134.0.155: bytes=32 time=66ms TTL=57
Reply from 202.134.0.155: bytes=32 time=62ms TTL=57
Reply from 202.134.0.155: bytes=32 time=67ms TTL=57
Reply from 202.134.0.155: bytes=32 time=63ms TTL=57
Reply from 202.134.0.155: bytes=32 time=88ms TTL=57
Reply from 202.134.0.155: bytes=32 time=96ms TTL=57
Reply from 202.134.0.155: bytes=32 time=67ms TTL=57
wuihhhhh , sedangkan koneksi ke International Mulai parah ……..biasanya 200-300an ms.. sekarang :
Reply from 66.94.234.13: bytes=32 time=705ms TTL=51
Reply from 66.94.234.13: bytes=32 time=719ms TTL=50
Reply from 66.94.234.13: bytes=32 time=698ms TTL=51
Reply from 66.94.234.13: bytes=32 time=702ms TTL=50
Reply from 66.94.234.13: bytes=32 time=746ms TTL=50
Reply from 66.94.234.13: bytes=32 time=744ms TTL=51
Reply from 66.94.234.13: bytes=32 time=741ms TTL=51
Reply from 66.94.234.13: bytes=32 time=771ms TTL=50
Reply from 66.94.234.13: bytes=32 time=798ms TTL=51
Reply from 66.94.234.13: bytes=32 time=774ms TTL=51
Reply from 66.94.234.13: bytes=32 time=762ms TTL=50
Reply from 66.94.234.13: bytes=32 time=724ms TTL=51
Reply from 66.94.234.13: bytes=32 time=721ms TTL=51
Reply from 66.94.234.13: bytes=32 time=738ms TTL=50
Reply from 66.94.234.13: bytes=32 time=688ms TTL=51
Reply from 66.94.234.13: bytes=32 time=719ms TTL=50
Reply from 66.94.234.13: bytes=32 time=703ms TTL=50
Reply from 66.94.234.13: bytes=32 time=681ms TTL=51
Reply from 66.94.234.13: bytes=32 time=665ms TTL=50
Reply from 66.94.234.13: bytes=32 time=669ms TTL=51
Reply from 66.94.234.13: bytes=32 time=689ms TTL=50
Reply from 66.94.234.13: bytes=32 time=638ms TTL=50
Reply from 66.94.234.13: bytes=32 time=665ms TTL=51
Reply from 66.94.234.13: bytes=32 time=664ms TTL=50
speedy lemot untuk koneksi international…. mudah2an ada perbaikan ke depannya…RF-Blitz susah maennya kalau ping nya segitu…..