我叫阿卜杜拉,来自科威特。抱歉,我的问题并不难,因为我知道这在技术上并不难。
我的网络连接出现了一些问题。我公司的 DSL 连接速度为 2mb。我的主要问题是延迟,早上还好,但之后就变得非常糟糕。我的互联网提供商说没有问题,一切都运行正常。我试图向他们解释延迟问题,但他们说只要我的下载速度正常,我就无能为力。
我只想知道这是否属实,并且在我更换互联网提供商之前公司是否无能为力,因为我觉得联络中心的人可能会在没有寻求技术支持的情况下回复我。
下面是我做的两条痕迹,一条是在早上,另一条是在下午:
这是 17:00 左右拍摄的
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>ping google.com
Pinging google.com [66.102.9.104] with 32 bytes of data:
Reply from 66.102.9.104: bytes=32 time=387ms TTL=49
Reply from 66.102.9.104: bytes=32 time=388ms TTL=49
Reply from 66.102.9.104: bytes=32 time=375ms TTL=49
Reply from 66.102.9.104: bytes=32 time=375ms TTL=49
Ping statistics for 66.102.9.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 375ms, Maximum = 388ms, Average = 381ms
C:\Documents and Settings\Administrator>ping google.com /t
Pinging google.com [66.102.9.104] with 32 bytes of data:
Reply from 66.102.9.104: bytes=32 time=376ms TTL=49
Reply from 66.102.9.104: bytes=32 time=382ms TTL=49
Reply from 66.102.9.104: bytes=32 time=371ms TTL=49
Reply from 66.102.9.104: bytes=32 time=378ms TTL=49
Reply from 66.102.9.104: bytes=32 time=374ms TTL=49
Reply from 66.102.9.104: bytes=32 time=371ms TTL=49
Reply from 66.102.9.104: bytes=32 time=365ms TTL=49
Reply from 66.102.9.104: bytes=32 time=366ms TTL=49
Reply from 66.102.9.104: bytes=32 time=353ms TTL=49
Reply from 66.102.9.104: bytes=32 time=331ms TTL=49
Reply from 66.102.9.104: bytes=32 time=333ms TTL=49
Reply from 66.102.9.104: bytes=32 time=348ms TTL=49
Reply from 66.102.9.104: bytes=32 time=365ms TTL=49
Reply from 66.102.9.104: bytes=32 time=346ms TTL=49
Reply from 66.102.9.104: bytes=32 time=335ms TTL=49
Reply from 66.102.9.104: bytes=32 time=340ms TTL=49
Reply from 66.102.9.104: bytes=32 time=344ms TTL=49
Reply from 66.102.9.104: bytes=32 time=333ms TTL=49
Reply from 66.102.9.104: bytes=32 time=328ms TTL=49
Reply from 66.102.9.104: bytes=32 time=332ms TTL=49
Reply from 66.102.9.104: bytes=32 time=326ms TTL=49
Reply from 66.102.9.104: bytes=32 time=333ms TTL=49
Reply from 66.102.9.104: bytes=32 time=325ms TTL=49
Reply from 66.102.9.104: bytes=32 time=333ms TTL=49
Reply from 66.102.9.104: bytes=32 time=338ms TTL=49
Reply from 66.102.9.104: bytes=32 time=341ms TTL=49
Ping statistics for 66.102.9.104:
Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 325ms, Maximum = 382ms, Average = 348ms
Control-C
^C
C:\Documents and Settings\Administrator>travert google.com
'travert' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Administrator>tracert google.com
Tracing route to google.com [66.102.9.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 80-184-31-1.adsl.kems.net [80.184.31.1]
3 7 ms 7 ms 8 ms 168.187.0.226
4 7 ms 8 ms 9 ms 168.187.0.125
5 180 ms 187 ms 188 ms if-11-2.core1.RSD-Riyad.as6453.net [116.0.78.89]
6 209 ms 222 ms 204 ms 195.219.167.57
7 541 ms 536 ms 540 ms 195.219.167.42
8 553 ms 552 ms 538 ms Vlan1102.icore1.PVU-Paris.as6453.net [195.219.24
1.109]
9 547 ms 543 ms 542 ms xe-9-1-0.edge4.paris1.level3.net [4.68.110.213]
10 540 ms 523 ms 531 ms ae-33-51.ebr1.Paris1.Level3.net [4.69.139.193]
11 755 ms 761 ms 695 ms ae-45-45.ebr1.London1.Level3.net [4.69.143.101]
12 271 ms 263 ms 400 ms ae-11-51.car1.London1.Level3.net [4.69.139.66]
13 701 ms 730 ms 742 ms 195.50.118.210
14 659 ms 641 ms 660 ms 209.85.255.76
15 280 ms 283 ms 292 ms 209.85.251.190
16 308 ms 293 ms 296 ms 72.14.232.239
17 679 ms 700 ms 721 ms 64.233.174.18
18 268 ms 281 ms 269 ms lm-in-f104.1e100.net [66.102.9.104]
Trace complete.
C:\Documents and Settings\Administrator>
这是上午 10:00 拍摄的
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>ping google.com
Pinging google.com [66.102.9.106] with 32 bytes of data:
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=111ms TTL=49
Reply from 66.102.9.106: bytes=32 time=112ms TTL=49
Reply from 66.102.9.106: bytes=32 time=120ms TTL=49
Ping statistics for 66.102.9.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 120ms, Average = 113ms
C:\Documents and Settings\Administrator>ping google.com /t
Pinging google.com [66.102.9.106] with 32 bytes of data:
Reply from 66.102.9.106: bytes=32 time=109ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=111ms TTL=49
Reply from 66.102.9.106: bytes=32 time=111ms TTL=49
Reply from 66.102.9.106: bytes=32 time=112ms TTL=49
Reply from 66.102.9.106: bytes=32 time=112ms TTL=49
Reply from 66.102.9.106: bytes=32 time=116ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=109ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=109ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=112ms TTL=49
Reply from 66.102.9.106: bytes=32 time=109ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=115ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=109ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Reply from 66.102.9.106: bytes=32 time=113ms TTL=49
Reply from 66.102.9.106: bytes=32 time=115ms TTL=49
Reply from 66.102.9.106: bytes=32 time=109ms TTL=49
Reply from 66.102.9.106: bytes=32 time=110ms TTL=49
Ping statistics for 66.102.9.106:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 135ms, Average = 112ms
Control-C
^C
C:\Documents and Settings\Administrator>tracert google.com
Tracing route to google.com [66.102.9.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 80-184-31-1.adsl.kems.net [80.184.31.1]
3 8 ms 7 ms 6 ms 168.187.0.226
4 6 ms 7 ms 7 ms 168.187.0.125
5 20 ms 20 ms 18 ms if-11-2.core1.RSD-Riyad.as6453.net [116.0.78.89]
6 171 ms 205 ms 215 ms 195.219.167.57
7 191 ms 215 ms 226 ms 195.219.167.42
8 * 103 ms 94 ms Vlan1102.icore1.PVU-Paris.as6453.net [195.219.24
1.109]
9 94 ms 95 ms 97 ms xe-9-1-0.edge4.paris1.level3.net [4.68.110.213]
10 94 ms 94 ms 94 ms ae-33-51.ebr1.Paris1.Level3.net [4.69.139.193]
11 101 ms 101 ms 101 ms ae-48-48.ebr1.London1.Level3.net [4.69.143.113]
12 102 ms 102 ms 101 ms ae-11-51.car1.London1.Level3.net [4.69.139.66]
13 103 ms 102 ms 103 ms 195.50.118.210
14 137 ms 103 ms 100 ms 209.85.255.76
15 130 ms 124 ms 124 ms 209.85.251.190
16 114 ms 116 ms 116 ms 72.14.232.239
17 135 ms 113 ms 126 ms 64.233.174.18
18 126 ms 125 ms 127 ms lm-in-f104.1e100.net [66.102.9.104]
Trace complete.
C:\Documents and Settings\Administrator>
答案1
好的,在我看来,延迟是由 TATA 通信网络引起的。因此,您的提供商 KEMS Peers 仅与 TATA 通信有关。
如果另一家 ISP 与您所在地区(科威特?)的其他提供商建立对等连接,那么您可能会获得更好的性能。如果其他 ISP 仍与 TATA 建立对等连接,除非他们在 TATA 网络上具有更高的优先级,否则您与他们建立对等连接似乎不会有任何更好的效果。
你可以使用 whois 查看谁拥有哪个 IP 来找到答案:
$ whois 168.187.0.226
...
inetnum: 168.187.0.0 - 168.187.255.255
netname: KEMS-KW
org: ORG-GI9-RIPE
descr: Kuwait Electronic and Messaging Services Company
descr: PO Box No 31811111
descr: Safat, kw 13036
country: KW
...
然后,您可以针对该 AS 运行 BGP 对等查询:
whois -h v4-peer.whois.cymru.com 168.187.0.226
PEER_AS | IP | AS Name
6453 | 168.187.0.226 | GLOBEINTERNET TATA Communications
因此,如果我没有看错的话,从延迟来看,它最终位于 TATA 通信网络内。
作为免责声明,我从未为 ISP 工作过,因此曾经工作过的人的答案可能比我的更权威。
答案2
Kyle 基本上是对的。延迟问题似乎出在您的 ISP 上游,因此他们几乎无法直接解决此问题,因为问题不在他们的网络中。
17:00 时,您已:
5 180 ms 187 ms 188 ms if-11-2.core1.RSD-Riyad.as6453.net [116.0.78.89]
6 209 ms 222 ms 204 ms 195.219.167.57
7 541 ms 536 ms 540 ms 195.219.167.42
8 553 ms 552 ms 538 ms Vlan1102.icore1.PVU-Paris.as6453.net [195.219.241.109]
10:00 时,您有:
5 20 ms 20 ms 18 ms if-11-2.core1.RSD-Riyad.as6453.net [116.0.78.89]
6 171 ms 205 ms 215 ms 195.219.167.57
7 191 ms 215 ms 226 ms 195.219.167.42
8 * 103 ms 94 ms Vlan1102.icore1.PVU-Paris.as6453.net [195.219.241.109]
看到 195.219.167.57 和 195.219.167.42 之间的延迟变化了吗?上午,只有大约 10 毫秒,这很好。然而,下午,有 300 毫秒的差异。两者都是 TATA 骨干网络的一部分,您的跟踪(和一般评论)似乎表明 TATA 在下午经历了这两个 IP 之间的拥塞。简而言之,它们有太多流量通过带宽不足的链路。
Kyle 是对的。既然问题出在 TATA 的网络中,那么这就是他们的问题,需要解决。您的 ISP 似乎使用 TATA 作为上行链路。我认为您有三个选择:
- 向你的 ISP 施压,迫使他们向 TATA 施压以解决问题。不幸的是,这可能没有多大帮助,但如果有足够多的人抱怨这个问题,他们可能会采取一些措施。TATA 可能已经计划修复它,如果你的 ISP 不联系 TATA,你可能永远不会知道。
- 了解您的 ISP 是否有其他互联网上行链路。如果有,请了解他们是否有可能将您的流量从 TATA 的网络转移出去。
- 寻找另一个不使用 TATA 网络的 ISP,或者至少寻找一个使用 TATA 但不通过此拥塞点路由的 ISP。