For the last few years, sonic has been peering directly with Google in Palo Alto. I know this because I have been accessing a server hosted in Google's cloud, from my home in San Francisco, and I have been periodically checking the path and performance.
In the last day or so, Sonic began routing that traffic over gtt.net rather than handing it directly to google. My latency has gotten much worse, which is how I detected the change.
Was this an intentional routing change? It doesn't seem to make sense from an economic standpoint (paying gtt for transit rather than peering directly with google).
Is this a temporary change? Will it return to "normal" soon? I chose Sonic because of the very low and consistent latency. I very much hope this was a temporary issue and that it will be resolved. When I called technical support I was told that the only way to find out was to post to this forum.
Regards,
Oscar
In the last day or so, Sonic began routing that traffic over gtt.net rather than handing it directly to google. My latency has gotten much worse, which is how I detected the change.
Was this an intentional routing change? It doesn't seem to make sense from an economic standpoint (paying gtt for transit rather than peering directly with google).
Is this a temporary change? Will it return to "normal" soon? I chose Sonic because of the very low and consistent latency. I very much hope this was a temporary issue and that it will be resolved. When I called technical support I was told that the only way to find out was to post to this forum.
Regards,
Oscar