Guys,
These result happened to be yesterday's. Insanely hilarious.....
To the TM DNS:
===========
Ping statistics for 202.188.0.133:
Packets: Sent = 126, Received = 123, Lost = 3 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 832ms, Average = 572ms
Ping statistics for 202.188.0.133:
Packets: Sent = 872, Received = 850, Lost = 22 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 1436ms, Average = 483ms
Ping statistics for 202.188.0.133:
Packets: Sent = 951, Received = 926, Lost = 25 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 1436ms, Average = 496ms
Email to TM's AGMs
=============
Dear All,
Some recap for your kind review and advise. This is one of those repeating issues from Streamyx. The information below is abstracted from the TRACE ROUTE which TM claims to be potentially causing ICMP overhead and has been blocked for that reason and security measures.
Please refer to the result below, the response time increased sharply on hop #3 onward (219.93.218.177, 219.93.216.157, 58.27.104.206, 219.94.9.166). The funny thing is, the respond time beyond TM's infrastructure seems to be perform alot better.
I recalled as per our previous discussion, one of the IP's location still await TM's confirmation on why it has high jump on respond time (ms). Have you found it? What about the 90% commitment to the users?
Tracing route to HOST [IP] with TTL of 32:
1 1ms 0ms 0ms 10.0.1.1
2 1ms 1ms 1ms 192.168.1.1
3 343ms 524ms * 219.93.218.177
4 836ms 848ms 726ms 219.93.216.157
5 802ms 727ms 607ms 58.27.104.206
6 875ms 869ms 893ms 219.94.9.166
7 783ms 999ms * gi2-8.mpd01.sjc04.atlas.cogentco.com [154.54.12.65]
8 211ms 211ms 211ms te3-1.mpd01.sfo01.atlas.cogentco.com [154.54.28.81]
9 406ms 472ms 427ms te7-4.mpd01.mci01.atlas.cogentco.com [154.54.24.106]
10 485ms 268ms 267ms te7-2.mpd01.ord01.atlas.cogentco.com [154.54.7.137]
11 284ms 284ms 284ms te2-1.mpd01.bos01.atlas.cogentco.com [154.54.6.17]
12 295ms 291ms 300ms te8-3.mpd03.jfk02.atlas.cogentco.com [66.28.4.202]
13 293ms 294ms 293ms te4-1.ccr01.phl01.atlas.cogentco.com [154.54.2.109]
14 293ms 294ms 293ms te4-1.ccr01.phl03.atlas.cogentco.com [154.54.0.190]
15 278ms 278ms 278ms hostnoc.demarc.cogentco.com [38.112.240.34]
16 293ms 295ms 304ms ec1-00.gwy02.HOST.HOST [IP]
17 399ms 399ms 402ms ec1-20.agg04.HOST.HOST [IP]
18 398ms 387ms 389ms HOST [IP]
Traceroute complete.
Seems like TM's backyard is jammed.