Frontier Communications → Re: Frontier Florida

It's not "trouble" with microsoft.com, it's just that it has been disabled from responding to
ping/traceroute requests.

When I said "issues" I was referring to the higher than normal latency.Agreed, and "gradually" is definitely the correct word, as they are saying it will be a two year process to renumber the IP addresses.

That latency is a result of routing within msn.net, external to the frontier network. I saw the same type of thing when we were still on alter.net network. Your latency is about twice what I see, probably a result of msn.network's cross country from where you are. This is what I see:
1 1 ms 1 ms 1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 10 ms 8 ms 7 ms lo0-100.LSANCA-VFTTP-312.verizon-gni.net [71.106.57.1]
3 10 ms 11 ms 11 ms 172.102.106.244
4 12 ms 10 ms 14 ms ae8---0.scr02.lsan.ca.frontiernet.net [74.40.3.49]
5 9 ms 7 ms 8 ms ae1---0.cbr01.lsan.ca.frontiernet.net [74.40.3.214]
6 * * * Request timed out.
7 15 ms 10 ms 11 ms ae-1-60.edge6.LosAngeles1.Level3.net [4.69.144.14]
8 8 ms 8 ms 11 ms ae-1-60.edge6.LosAngeles1.Level3.net [4.69.144.14]
9 8 ms 9 ms 7 ms ae-26-26.car1.LosAngeles1.Level3.net [4.69.201.10]
10 8 ms 7 ms 7 ms MICROSOFT-C.car1.LosAngeles1.Level3.net [4.71.140.78]
11 42 ms 45 ms 44 ms be-71-0.ibr02.lax03.ntwk.msn.net [104.44.8.108]
12 46 ms 47 ms 43 ms be-3-0.ibr01.sn4.ntwk.msn.net [104.44.4.5]
13 43 ms 44 ms 40 ms ae66-0.sn2-96cb-1b.ntwk.msn.net [104.44.9.59]
14 * * * Request timed out.

I really like the latency within frontier.net and Level3.
etc.

Latency looks better now.

Tracing route to microsoft.com [23.96.52.53]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  192.168.110.1
  2     5 ms     4 ms     4 ms  lo0-100.tampfl-vfttp-316.verizon-gni.net [72.91.227.1]
  3     3 ms     7 ms     6 ms  172.99.45.84
  4    10 ms     9 ms    10 ms  ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
  5     8 ms     8 ms     9 ms  ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
  6     *       10 ms     9 ms  lag-101.ear3.miami2.level3.net [4.15.156.29]
  7     8 ms     9 ms     9 ms  ae-2-3613.edge1.miami2.level3.net [4.69.136.193]
  8     8 ms     9 ms     9 ms  microsoft-c.edge1.miami2.level3.net [4.59.80.22]
  9     8 ms     9 ms     9 ms  ae9-0.mia-96cbe-1b.ntwk.msn.net [104.44.225.167]
 10    35 ms    37 ms    39 ms  ae5-0.atb-96cbe-1c.ntwk.msn.net [104.44.224.230]
 11    36 ms    36 ms    39 ms  be-3-0.ibr01.bn1.ntwk.msn.net [104.44.4.49]
 12    40 ms    39 ms    39 ms  be-1-0.ibr02.bn1.ntwk.msn.net [104.44.4.63]
 13    38 ms    39 ms    38 ms  be-3-0.ibr02.was05.ntwk.msn.net [104.44.4.26]
 14    36 ms    37 ms    37 ms  ae73-0.bl4-96cbe-1b.ntwk.msn.net [104.44.9.31]
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
 

Agreed, as this was a big worry for me going in.

Odd. Mine is unchanged.

My trace to Microsoft resolves to this route.
C:\Users\>tracert www.microsoft.com

Tracing route to e10088.dspb.akamaiedge.net [23.14.184.154]
over a maximum of 30 hops:

1 21 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.TAMPFL-VFTTP-68.verizon-gni.net [96.243.212.1]
3 11 ms 12 ms 9 ms 172.99.42.204
4 15 ms 11 ms 14 ms ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
5 16 ms 14 ms 17 ms ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
6 * * * Request timed out.
7 18 ms 19 ms 18 ms NTT-level3-80G.Miami.Level3.net [4.68.127.54]
8 27 ms 26 ms 29 ms ae-4.r05.miamfl02.us.bb.gin.ntt.net [129.250.2.129]
9 18 ms 16 ms 14 ms ae-4.akamai.miamfl02.us.bb.gin.ntt.net [157.238.179.26]
10 19 ms 17 ms 16 ms a23-14-184-154.deploy.static.akamaitechnologies.com [23.14.184.154]

Trace complete.

I just noticed when I did the trace to microsoft.com the 2nd time it resolved to a different IP, that's probably the reason for the change. But anyway, so far so good. Hopefully it continues to stay this way and our only potential issues are billing ones.

www.microsoft.com = akamaiedge.net
microsoft.com = ntwk.msn.net

www uses different hosting

Probaly because microsoft.com resolves to 23.96.52.53, 104.43.195.251, 191.239.213.197, 23.100.122.175, and 104.40.211.35 -- various Asure nodes in Virginia, Chicago, Dublin Ireland, etc. so what you hit is what you get.

Yup, I just hadn't noticed that before so when I saw the fluctuations in latency I thought something was amiss.

That IP for which your first trace showed excessive latency is an Azure node in Amsterdam. So that latency isn't bad for that location.

Agreed. Again, I just didn't notice it was resolving to different IP's so when I saw such large latency fluctuations I thought there was an issue outside of Frontiers network. Which is why I started looking at the trace route more closely and saw it was resolving to a different IP than the previous trace.