【求助】如果從 GiGa 改 HiNet , 部份 HiNet 線路會從新牽嗎 ?
目前使用 GiGa ADSL , 在連到某些地方, 經過 HiNet 線路, 發現有線路不穩的情況, 向 GiGa 反應, 答說會向 HiNet 反應; 向 HiNet 反應, 客服給了個 Email 讓我去反應, 寄去後石沉大海; 請使用 HiNet , SeedNet 朋友測試傳回結果給我, 數據都很正常
既然 GiGa 無力解決 (雖然錯不在 GiGa), 考慮換 ISP 到 SeedNet 或 HiNet , 但是換 ISP 後, 有問題的該段 HiNet 會換一條嗎 ? 有人知道嗎 ?
(如果不會, 變動就沒有意義了)
[CODE]
Pinging 168.95.1.1 with 32 bytes of data:
Request timed out.
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Reply from 168.95.1.1: bytes=32 time=54ms TTL=246
Reply from 168.95.1.1: bytes=32 time=50ms TTL=246
Reply from 168.95.1.1: bytes=32 time=55ms TTL=246
Reply from 168.95.1.1: bytes=32 time=52ms TTL=246
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Reply from 168.95.1.1: bytes=32 time=55ms TTL=246
Reply from 168.95.1.1: bytes=32 time=57ms TTL=246
Reply from 168.95.1.1: bytes=32 time=62ms TTL=246
Reply from 168.95.1.1: bytes=32 time=63ms TTL=246
Reply from 168.95.1.1: bytes=32 time=56ms TTL=246
Request timed out.
Reply from 168.95.1.1: bytes=32 time=56ms TTL=246
Request timed out.
Reply from 168.95.1.1: bytes=32 time=51ms TTL=246
Reply from 168.95.1.1: bytes=32 time=52ms TTL=246
Reply from 168.95.1.1: bytes=32 time=50ms TTL=246
Reply from 168.95.1.1: bytes=32 time=51ms TTL=246
Reply from 168.95.1.1: bytes=32 time=66ms TTL=246
Request timed out.
Request timed out.
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Request timed out.
Reply from 168.95.1.1: bytes=32 time=52ms TTL=246
Reply from 168.95.1.1: bytes=32 time=60ms TTL=246
Reply from 168.95.1.1: bytes=32 time=56ms TTL=246
Request timed out.
Reply from 168.95.1.1: bytes=32 time=54ms TTL=246
Request timed out.
Reply from 168.95.1.1: bytes=32 time=58ms TTL=246
Reply from 168.95.1.1: bytes=32 time=57ms TTL=246
Reply from 168.95.1.1: bytes=32 time=57ms TTL=246
Request timed out.
Reply from 168.95.1.1: bytes=32 time=64ms TTL=246
Reply from 168.95.1.1: bytes=32 time=56ms TTL=246
Reply from 168.95.1.1: bytes=32 time=54ms TTL=246
Reply from 168.95.1.1: bytes=32 time=51ms TTL=246
Reply from 168.95.1.1: bytes=32 time=48ms TTL=246
Reply from 168.95.1.1: bytes=32 time=55ms TTL=246
Reply from 168.95.1.1: bytes=32 time=49ms TTL=246
Reply from 168.95.1.1: bytes=32 time=50ms TTL=246
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Reply from 168.95.1.1: bytes=32 time=57ms TTL=246
Reply from 168.95.1.1: bytes=32 time=50ms TTL=246
Reply from 168.95.1.1: bytes=32 time=59ms TTL=246
Reply from 168.95.1.1: bytes=32 time=58ms TTL=246
Request timed out.
Reply from 168.95.1.1: bytes=32 time=59ms TTL=246
Reply from 168.95.1.1: bytes=32 time=52ms TTL=246
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Reply from 168.95.1.1: bytes=32 time=53ms TTL=246
Reply from 168.95.1.1: bytes=32 time=61ms TTL=246
Reply from 168.95.1.1: bytes=32 time=61ms TTL=246
Reply from 168.95.1.1: bytes=32 time=57ms TTL=246
Reply from 168.95.1.1: bytes=32 time=56ms TTL=246
Reply from 168.95.1.1: bytes=32 time=63ms TTL=246
Reply from 168.95.1.1: bytes=32 time=69ms TTL=246
Ping statistics for 168.95.1.1:
Packets: Sent = 60, Received = 50, Lost = 10 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 69ms, Average = 55ms
Tracing route to dns.hinet.net [168.95.1.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 51 ms 47 ms 49 ms TPNOC1-ERX-D09-BRAS-1.AX.giga.net.tw [203.133.3.31]
3 49 ms 48 ms 46 ms TPNOC1-C65-G4-1-ERX01.IX.giga.net.tw [203.187.3.85]
4 50 ms 48 ms 51 ms TPNOC1-P76-TenG3-1-C65.IX.giga.net.tw [203.187.9.54]
5 50 ms 50 ms 47 ms TPNOC1-G35-TWIX-G0-2-G65.IX.giga.net.tw [203.204.205.62]
6 51 ms 51 ms 50 ms GIGA-TWIX-G35-G0-8-TPNOC1.IX.giga.net.tw [203.133.92.146]
7 54 ms 58 ms 53 ms 210.62.255.5
8 * 53 ms * tp-twix-r1.router.hinet.net [210.65.161.126]
9 53 ms 52 ms 50 ms tp-s2-c12r2.router.hinet.net [211.22.35.230]
10 55 ms 52 ms 54 ms tp-s2-c6r8.router.hinet.net [211.22.35.53]
11 53 ms 51 ms 53 ms dns.hinet.net [168.95.1.1]
Trace complete.
Tracing route to dns.hinet.net [168.95.1.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 49 ms 48 ms 47 ms TPNOC1-ERX-D09-BRAS-1.AX.giga.net.tw [203.133.3.31]
3 51 ms 52 ms 50 ms TPNOC1-C65-G4-1-ERX01.IX.giga.net.tw [203.187.3.85]
4 49 ms 46 ms 46 ms TPNOC1-P76-TenG3-1-C65.IX.giga.net.tw [203.187.9.54]
5 50 ms 47 ms 48 ms TPNOC1-G35-TWIX-G0-2-G65.IX.giga.net.tw [203.204.205.62]
6 52 ms 56 ms 51 ms GIGA-TWIX-G35-G0-8-TPNOC1.IX.giga.net.tw [203.133.92.146]
7 50 ms 56 ms 56 ms 210.62.255.5 (這已經是 HiNet 地盤了)
8 * * 52 ms tp-twix-r1.router.hinet.net [210.65.161.126]
9 * 51 ms 53 ms tp-s2-c12r2.router.hinet.net [211.22.35.230]
10 51 ms 52 ms 51 ms tp-s2-c6r8.router.hinet.net [211.22.35.53]
11 50 ms 54 ms * dns.hinet.net [168.95.1.1]
12 56 ms 52 ms 53 ms dns.hinet.net [168.95.1.1]
Trace complete.
Tracing route to dns.hinet.net [168.95.1.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 49 ms 48 ms 47 ms TPNOC1-ERX-D09-BRAS-1.AX.giga.net.tw [203.133.3.31]
3 60 ms 50 ms 50 ms TPNOC1-C65-G4-1-ERX01.IX.giga.net.tw [203.187.3.85]
4 49 ms 49 ms 50 ms TPNOC1-P76-TenG3-1-C65.IX.giga.net.tw [203.187.9.54]
5 51 ms 50 ms 46 ms TPNOC1-G35-TWIX-G0-2-G65.IX.giga.net.tw [203.204.205.62]
6 57 ms 58 ms 63 ms GIGA-TWIX-G35-G0-8-TPNOC1.IX.giga.net.tw [203.133.92.146]
7 54 ms 51 ms 52 ms 210.62.255.5
8 54 ms 49 ms * tp-twix-r1.router.hinet.net [210.65.161.126]
9 57 ms 52 ms 52 ms tp-s2-c12r2.router.hinet.net [211.22.35.230]
10 54 ms 51 ms 49 ms tp-s2-c6r8.router.hinet.net [211.22.35.53]
11 52 ms 54 ms * dns.hinet.net [168.95.1.1]
12 * * 53 ms dns.hinet.net [168.95.1.1]
Trace complete.
[/CODE]
