384K 產品

可列印頁面

在單一頁面顯示本主題中的 40 個文章

2004-02-26, 03:25 PM
coolbrother

【新消息】光速通訊將自 93/3/1 推出 3M/384K 產品

剛剛得知的消息，光速通訊將自 93/3/1 推出 3M/384K 產品！
費用方面預計為每個月 1200 元，近日內各位應該就可以在電視上看到促銷廣告了。:)
2004-02-26, 06:52 PM
Make

3M/384 1200啊...和現在2M/384 700比起來...
對我來講可以說是完全不具吸引力阿...xd

我真有需要到3M的話...寧願簽兩條2M/384K的....
2004-02-26, 07:07 PM
coolbrother

[QUOTE][i]最初由 Make 發表[/i]
[B]3M/384 1200啊...和現在2M/384 700比起來...
對我來講可以說是完全不具吸引力阿...xd

我真有需要到3M的話...寧願簽兩條2M/384K的.... [/B][/QUOTE]
然後買一台頻寬合併器嗎？
這樣也不錯喔~~:D
2004-02-26, 08:11 PM
gto1127

的確是沒啥吸引力
尤其是用過它們之前CABLE的舊客戶
以之前那種品質+服務
賣1000我看還怕招不到客戶勒XD
要收1200先拿6M出來跟GIGA抗衡吧~
或許我還會考慮:P:P
2004-02-26, 08:57 PM
tzulinle

恩恩，如果是3M/512的話那可以考慮說。
2004-02-26, 09:19 PM
coolbrother

[QUOTE][i]最初由 tzulinle 發表[/i]
[B]恩恩，如果是3M/512的話那可以考慮說。 [/B][/QUOTE]
已經向公司反應中！
畢竟公司的假想敵是中華電信~~~;)
2004-02-26, 09:37 PM
kiner

[QUOTE][i]最初由 coolbrother 發表[/i]
[B]已經向公司反應中！
畢竟公司的假想敵是中華電信~~~;) [/B][/QUOTE]

雖然離峰時段速度不錯
但是尖峰時段的速度也是慢到翻掉
我要強調是"慢到翻掉"
除了看網頁(圖不多)和msn可以正常運作外
下載的速度11.4kb/s
這樣就算升到15m/2m也是沒什麼用呀..
(已經是2m/384的用戶)
2004-02-26, 09:41 PM
coolbrother

[QUOTE][i]最初由 kiner 發表[/i]
[B]
下載的速度11.4kb/s
這樣就算升到15m/2m也是沒什麼用呀..
(已經是2m/384的用戶) [/B][/QUOTE]
kiner兄是下載哪裡的東西只有 11.4kb/s 呢？
折算一下竟然只有 1.425KBytes/sec :confused:
如果可以的話，希望把該網址給小弟，小弟試試看~~:)
2004-02-26, 09:50 PM
kiner

[QUOTE][i]最初由 coolbrother 發表[/i]
[B]kiner兄是下載哪裡的東西只有 11.4kb/s 呢？
折算一下竟然只有 1.425KBytes/sec :confused:
如果可以的話，希望把該網址給小弟，小弟試試看~~:) [/B][/QUOTE]

我的kb/s 就是 kbytes/s 啦
但是還是很慢
參考網址:
[url]http://hk.geocities.com/ghhjhdw0jw/av0271048.jpg[/url]

參考速度:

Pinging 168.95.1.1 with 32 bytes of data:

Reply from 168.95.1.1: bytes=32 time=222ms TTL=244
Reply from 168.95.1.1: bytes=32 time=154ms TTL=244
Reply from 168.95.1.1: bytes=32 time=162ms TTL=244
Reply from 168.95.1.1: bytes=32 time=197ms TTL=244
Request timed out.
Reply from 168.95.1.1: bytes=32 time=105ms TTL=244
Reply from 168.95.1.1: bytes=32 time=125ms TTL=244
Reply from 168.95.1.1: bytes=32 time=96ms TTL=244
Reply from 168.95.1.1: bytes=32 time=115ms TTL=244
Reply from 168.95.1.1: bytes=32 time=61ms TTL=244
Reply from 168.95.1.1: bytes=32 time=233ms TTL=244
Request timed out.
Reply from 168.95.1.1: bytes=32 time=107ms TTL=244
Reply from 168.95.1.1: bytes=32 time=95ms TTL=244
Request timed out.
Reply from 168.95.1.1: bytes=32 time=300ms TTL=244
Reply from 168.95.1.1: bytes=32 time=160ms TTL=244
Request timed out.
Reply from 168.95.1.1: bytes=32 time=63ms TTL=244
Reply from 168.95.1.1: bytes=32 time=34ms TTL=244
Reply from 168.95.1.1: bytes=32 time=270ms TTL=244
Reply from 168.95.1.1: bytes=32 time=318ms TTL=244
Reply from 168.95.1.1: bytes=32 time=340ms TTL=244
Request timed out.
Request timed out.
Request timed out.
Reply from 168.95.1.1: bytes=32 time=63ms TTL=244
Reply from 168.95.1.1: bytes=32 time=162ms TTL=244
Reply from 168.95.1.1: bytes=32 time=115ms TTL=244
Reply from 168.95.1.1: bytes=32 time=66ms TTL=244
Reply from 168.95.1.1: bytes=32 time=117ms TTL=244
Request timed out.
Request timed out.
Reply from 168.95.1.1: bytes=32 time=352ms TTL=244
Reply from 168.95.1.1: bytes=32 time=369ms TTL=244
Reply from 168.95.1.1: bytes=32 time=690ms TTL=244
Reply from 168.95.1.1: bytes=32 time=264ms TTL=244
Reply from 168.95.1.1: bytes=32 time=394ms TTL=244
Reply from 168.95.1.1: bytes=32 time=381ms TTL=244
Reply from 168.95.1.1: bytes=32 time=745ms TTL=244
Reply from 168.95.1.1: bytes=32 time=1658ms TTL=244
Reply from 168.95.1.1: bytes=32 time=1883ms TTL=244
Reply from 168.95.1.1: bytes=32 time=1081ms TTL=244
Request timed out.
Reply from 168.95.1.1: bytes=32 time=299ms TTL=244
Reply from 168.95.1.1: bytes=32 time=379ms TTL=244
Request timed out.
Reply from 168.95.1.1: bytes=32 time=134ms TTL=244
Reply from 168.95.1.1: bytes=32 time=118ms TTL=244
Request timed out.

Ping statistics for 168.95.1.1:
Packets: Sent = 50, Received = 38, Lost = 12 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 1883ms, Average = 327ms
2004-02-26, 09:55 PM
kiner

Pinging lsc.net.tw [203.79.224.59] with 32 bytes of data:

Reply from 203.79.224.59: bytes=32 time=816ms TTL=249
Reply from 203.79.224.59: bytes=32 time=1477ms TTL=249
Reply from 203.79.224.59: bytes=32 time=1506ms TTL=249
Reply from 203.79.224.59: bytes=32 time=1211ms TTL=249
Reply from 203.79.224.59: bytes=32 time=1013ms TTL=249
Reply from 203.79.224.59: bytes=32 time=944ms TTL=249
Reply from 203.79.224.59: bytes=32 time=652ms TTL=249
Reply from 203.79.224.59: bytes=32 time=425ms TTL=249
Reply from 203.79.224.59: bytes=32 time=407ms TTL=249
Reply from 203.79.224.59: bytes=32 time=260ms TTL=249
Reply from 203.79.224.59: bytes=32 time=183ms TTL=249
Reply from 203.79.224.59: bytes=32 time=202ms TTL=249
Reply from 203.79.224.59: bytes=32 time=188ms TTL=249
Reply from 203.79.224.59: bytes=32 time=275ms TTL=249
Reply from 203.79.224.59: bytes=32 time=288ms TTL=249
Reply from 203.79.224.59: bytes=32 time=356ms TTL=249
Reply from 203.79.224.59: bytes=32 time=661ms TTL=249
Reply from 203.79.224.59: bytes=32 time=192ms TTL=249
Reply from 203.79.224.59: bytes=32 time=163ms TTL=249
Reply from 203.79.224.59: bytes=32 time=236ms TTL=249
Reply from 203.79.224.59: bytes=32 time=534ms TTL=249
Reply from 203.79.224.59: bytes=32 time=344ms TTL=249
Reply from 203.79.224.59: bytes=32 time=401ms TTL=249
Reply from 203.79.224.59: bytes=32 time=165ms TTL=249
Reply from 203.79.224.59: bytes=32 time=164ms TTL=249
Reply from 203.79.224.59: bytes=32 time=257ms TTL=249
Reply from 203.79.224.59: bytes=32 time=461ms TTL=249
Reply from 203.79.224.59: bytes=32 time=582ms TTL=249
Reply from 203.79.224.59: bytes=32 time=615ms TTL=249
Reply from 203.79.224.59: bytes=32 time=420ms TTL=249
Reply from 203.79.224.59: bytes=32 time=305ms TTL=249
Reply from 203.79.224.59: bytes=32 time=546ms TTL=249
Reply from 203.79.224.59: bytes=32 time=1091ms TTL=249
Reply from 203.79.224.59: bytes=32 time=512ms TTL=249
Request timed out.
Reply from 203.79.224.59: bytes=32 time=146ms TTL=249
Reply from 203.79.224.59: bytes=32 time=192ms TTL=249
Reply from 203.79.224.59: bytes=32 time=563ms TTL=249
Reply from 203.79.224.59: bytes=32 time=145ms TTL=249
Reply from 203.79.224.59: bytes=32 time=154ms TTL=249
Reply from 203.79.224.59: bytes=32 time=108ms TTL=249
Reply from 203.79.224.59: bytes=32 time=217ms TTL=249
Reply from 203.79.224.59: bytes=32 time=244ms TTL=249
Reply from 203.79.224.59: bytes=32 time=113ms TTL=249
Reply from 203.79.224.59: bytes=32 time=262ms TTL=249
Reply from 203.79.224.59: bytes=32 time=126ms TTL=249
Reply from 203.79.224.59: bytes=32 time=343ms TTL=249
Reply from 203.79.224.59: bytes=32 time=92ms TTL=249
Reply from 203.79.224.59: bytes=32 time=98ms TTL=249
Reply from 203.79.224.59: bytes=32 time=108ms TTL=249

Ping statistics for 203.79.224.59:
Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 1506ms, Average = 423ms

在單一頁面顯示本主題中的 40 個文章