AlanOfTheBerg wrote:Here's my ping results to that server. Does yours resolve to the same IP?
....
C:\Users\bz>ping tiles4.waze.com
Pinging tiles4.waze.com [75.101.158.200] with 32 bytes of data:
Reply from 75.101.158.200: bytes=32 time=55ms TTL=54
Reply from 75.101.158.200: bytes=32 time=53ms TTL=54
Reply from 75.101.158.200: bytes=32 time=54ms TTL=54
Reply from 75.101.158.200: bytes=32 time=53ms TTL=54
Ping statistics for 75.101.158.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 55ms, Average = 53ms
C:\Users\bz>tracert tiles4.waze.com
Tracing route to tiles4.waze.com [75.101.158.200]
over a maximum of 30 hops:
1 9 ms 9 ms 11 ms 10.128.40.1
2 9 ms 9 ms 9 ms 70.169.88.78
3 9 ms 9 ms 8 ms 70.169.88.36
4 9 ms 9 ms 9 ms btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
5 52 ms 57 ms 52 ms 68.1.4.133
6 54 ms 54 ms 61 ms 205.251.245.7
7 53 ms 52 ms 53 ms 205.251.245.47
8 52 ms 54 ms 52 ms 216.182.224.203
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 54 ms 54 ms 53 ms ec2-75-101-160-97.compute-1.amazonaws.com [75.10
1.160.97]
13 55 ms 53 ms 54 ms ec2-75-101-158-200.compute-1.amazonaws.com [75.1
01.158.200]
Trace complete.
Looks like the path has some intermittent dropouts.

