Troubleshooting Issues with Inconsistent Access Certain Websites

1. Establish Baseline

Collect this info when the network is healthy. It should be used as a control factor to compare with deviations of network performance and issues.

H:\>pathping google.com

Tracing route to google.com [172.217.5.110]
over a maximum of 30 hops:
0 Komputer [192.168.1.500]
1 192.168.12.1
2 192.168.255.1
3 47.180.200.1
4 172.102.104.220
5 ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
6 ae1---0.cbr01.lsan.ca.frontiernet.net [74.40.3.214]
7 74.40.26.254
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 0 Komputer [192.168.1.500]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.12.1
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.255.1
0/ 100 = 0% |
3 2ms 2/ 100 = 2% 2/ 100 = 2% 47.180.200.1
0/ 100 = 0% |
4 5ms 1/ 100 = 1% 1/ 100 = 1% 172.102.104.220
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
0/ 100 = 0% |
6 5ms 0/ 100 = 0% 0/ 100 = 0% ae1---0.cbr01.lsan.ca.frontiernet.net [74.40.3.214]
1/ 100 = 1% |
7 4ms 1/ 100 = 1% 0/ 100 = 0% 74.40.26.254

Trace complete.
2. Compare to a known problematic URL
H:\>pathping outlook.office.com

Tracing route to SJC-efz.ms-acdc.office.com [52.96.55.194]
over a maximum of 30 hops:
0 Komputer [192.168.1.500]
1 192.168.12.1
2 192.168.255.1
3 47.180.200.1
4 172.102.104.220
5 ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
6 ae1---0.cbr01.lsan.ca.frontiernet.net [74.40.3.214]
7 ae11-0.lax-96cbe-1a.ntwk.msn.net [207.46.36.168]
8 be-61-0.ibr01.lax03.ntwk.msn.net [104.44.8.104]
9 be-4-0.ibr01.by2.ntwk.msn.net [104.44.4.3]
10 be-5-0.ibr03.by21.ntwk.msn.net [104.44.18.104]
11 ae120-0.icr01.by21.ntwk.msn.net [104.44.22.166]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 KDoan-HPZ.corp.vectorusa.com [192.168.13.21]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.12.1
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.255.1
0/ 100 = 0% |
3 2ms 1/ 100 = 1% 1/ 100 = 1% 47.180.200.1
0/ 100 = 0% |
4 5ms 1/ 100 = 1% 1/ 100 = 1% 172.102.104.220
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
0/ 100 = 0% |
6 4ms 0/ 100 = 0% 0/ 100 = 0% ae1---0.cbr01.lsan.ca.frontiernet.net [74.40.3.214]
2/ 100 = 2% |
7 --- 100/ 100 =100% 98/ 100 = 98% ae11-0.lax-96cbe-1a.ntwk.msn.net [207.46.36.168]
0/ 100 = 0% |
8 --- 100/ 100 =100% 98/ 100 = 98% be-61-0.ibr01.lax03.ntwk.msn.net [104.44.8.104]
0/ 100 = 0% |
9 --- 100/ 100 =100% 98/ 100 = 98% be-4-0.ibr01.by2.ntwk.msn.net [104.44.4.3]
0/ 100 = 0% |
10 --- 100/ 100 =100% 98/ 100 = 98% be-5-0.ibr03.by21.ntwk.msn.net [104.44.18.104]
0/ 100 = 0% |
11 13ms 2/ 100 = 2% 0/ 100 = 0% ae120-0.icr01.by21.ntwk.msn.net [104.44.22.166]

Trace complete.

Interpretation:
– There appears is a connection problem between hop 4 (172.102.104.220)and 5 (ae8—0.scr02.lsan.ca.frontiernet.net [74.40.3.49]). However, that could be caused by ping blocking between this client and such node.
– The final hop #11 shows a 2% loss. That indicates reachability with some packet losses. This usually leads to inconsistent accessibility.

Without being able to pin-point a “root cause,” these would be the possibilities for consideration:

  1. External ISP routing issues
  2. Internal multi-paths routing issues

Leave a Reply

Your email address will not be published. Required fields are marked *