I'm seeing 250 ms between California and Oregon. Not just AWS, but also between, say, Comcast and AWS. Latency from other locations, such as between N. Virginia and Oregon, is much lower, about 72 ms in my tests. Anyone else experiencing these issues along the west coast? -- Florin Andrei http://florin.myip.org/
Hmmm, I am seeing about 20ms from a VPS in Seattle, do you happen to have a trace of the path with this issue? /Charles On Fri, Sep 18, 2015 at 1:50 PM, Florin Andrei <florin@andrei.myip.org> wrote:
I'm seeing 250 ms between California and Oregon. Not just AWS, but also between, say, Comcast and AWS.
Latency from other locations, such as between N. Virginia and Oregon, is much lower, about 72 ms in my tests.
Anyone else experiencing these issues along the west coast?
-- Florin Andrei http://florin.myip.org/
On 2015-09-18 13:20, Charles van Niman wrote:
Hmmm, I am seeing about 20ms from a VPS in Seattle, do you happen to have a trace of the path with this issue?
From my laptop in San Jose to an ELB in AWS / Oregon: 1.|-- 192.168.1.1 0.0% 10 10.6 6.0 1.0 17.1 5.2 2.|-- 10.1.10.1 0.0% 10 3.5 12.7 2.0 60.8 18.2 3.|-- c-98-207-128-1.hsd1.ca.co 0.0% 10 27.5 19.8 6.0 29.1 7.3 4.|-- te-0-2-0-7-sur04.sanjose. 0.0% 10 11.6 14.5 10.2 28.4 5.7 5.|-- te-0-6-0-6-sur03.sanjose. 0.0% 10 9.9 17.2 9.9 38.2 8.7 6.|-- he-0-3-0-2-ar01.santaclar 0.0% 10 16.0 20.1 11.8 35.2 8.0 7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 8.|-- he-0-11-0-1-pe02.529bryan 0.0% 10 21.4 21.7 10.8 43.4 10.4 9.|-- gtt-cr01.losangeles.ca.ib 0.0% 10 10.8 18.5 10.8 40.4 8.8 10.|-- 205.251.229.32 0.0% 10 204.7 216.3 204.7 236.7 10.2 11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 14.|-- 27.0.0.255 0.0% 10 208.0 217.5 201.1 300.2 30.1 15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 16.|-- 205.251.225.215 0.0% 10 205.6 217.6 200.5 302.2 30.1 17.|-- 205.251.232.72 0.0% 9 208.6 219.5 203.2 259.8 20.1 18.|-- 205.251.232.201 0.0% 9 216.6 225.5 206.3 254.8 15.5 19.|-- 205.251.230.127 0.0% 8 201.0 212.5 201.0 225.1 7.3 20.|-- ??? 100.0 8 0.0 0.0 0.0 0.0 0.0 1.|-- 192.168.1.1 0.0% 10 8.8 14.2 0.9 66.2 19.2 2.|-- 10.1.10.1 0.0% 10 7.1 16.7 1.4 72.0 20.7 3.|-- 98.207.128.1 0.0% 10 13.6 19.6 13.6 30.4 5.4 4.|-- 162.151.30.29 0.0% 10 13.3 24.9 9.2 97.9 26.8 5.|-- 162.151.79.1 0.0% 10 56.5 27.4 11.9 56.5 13.6 6.|-- 68.87.192.173 0.0% 10 13.8 21.1 9.9 45.1 11.2 7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 8.|-- 68.86.86.146 0.0% 10 14.3 20.0 13.5 38.0 7.6 9.|-- 66.208.229.30 0.0% 10 15.9 19.4 10.1 40.5 9.2 10.|-- 205.251.229.32 10.0% 10 213.0 245.7 208.2 377.9 53.2 11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 14.|-- 27.0.0.255 0.0% 10 220.0 234.2 207.6 335.0 39.5 15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 16.|-- 205.251.225.215 0.0% 10 208.3 226.3 206.7 276.6 21.8 17.|-- 205.251.232.72 0.0% 9 210.6 216.2 204.1 237.7 12.5 18.|-- 205.251.232.201 0.0% 9 236.1 232.5 205.8 261.2 18.3 19.|-- 205.251.230.127 0.0% 8 206.1 233.2 206.1 287.3 24.8 20.|-- ??? 100.0 8 0.0 0.0 0.0 0.0 0.0 -- Florin Andrei http://florin.myip.org/
hi andrei On 09/18/15 at 11:50am, Florin Andrei wrote:
I'm seeing 250 ms between California and Oregon. Not just AWS, but also between, say, Comcast and AWS.
Latency from other locations, such as between N. Virginia and Oregon, is much lower, about 72 ms in my tests.
Anyone else experiencing these issues along the west coast?
amazon seems confused from Reno# traceroute 205.251.230.127 ------------------------------------- traceroute to 205.251.230.127 (205.251.230.127), 30 hops max, 60 byte packets 1 ... deleted ... 2 * * * 3 rno-core0-ge.greatbasin.net (207.228.35.136) 10.863 ms 12.237 ms 13.611 ms 4 67.138.231.149 (67.138.231.149) 14.963 ms 16.372 ms 17.719 ms 5 paix01-sfo4.amazon.com (198.32.176.36) 21.914 ms 23.259 ms 26.048 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * *
I've asked Runscope (a monitoring service we're using for a few things, with locations in AWS and Rackspace), and they've confirmed my findings - there's unusually high latency somewhere around the AWS facility in Oregon, started last night, but they say it's "getting better". -- Florin Andrei http://florin.myip.org/
I have a SmokePing machine sitting in AWS Oregon looking at a few of my sites. It shows a bunch of ugliness starting around midnight Central and smoothing out but still with higher latency continuing to some sites. The same site is showing ugliness in the last hour. -- Keith Stokes
On Sep 18, 2015, at 4:39 PM, Florin Andrei <florin@andrei.myip.org> wrote:
I've asked Runscope (a monitoring service we're using for a few things, with locations in AWS and Rackspace), and they've confirmed my findings - there's unusually high latency somewhere around the AWS facility in Oregon, started last night, but they say it's "getting better".
-- Florin Andrei http://florin.myip.org/
On Fri, 18 Sep 2015 11:50:23 -0700 Florin Andrei <florin@andrei.myip.org> wrote:
I'm seeing 250 ms between California and Oregon. Not just AWS, but also between, say, Comcast and AWS.
Latency from other locations, such as between N. Virginia and Oregon, is much lower, about 72 ms in my tests.
Anyone else experiencing these issues along the west coast?
Not sure if related to what you are seeing, but I do know there is a BPA fiber cut. It is apparently to do with some towers on an island in the Columbia river. I heard ETR was evening on Saturday. It sounded like a complicated repair. --TimH
participants (6)
-
alvin nanog -
Charles van Niman -
Florin Andrei -
Justin Parker -
Keith Stokes -
Tim Howe