icago then Seattle.
Sent from my iPhone
On 1 May 2017, at 2:10 pm, Florin Andrei
wrote:
Phil,
The traceroute was done by a coworker in Quebec on April 26, from one
of our corporate offices. His IP address was probably 104.163.180.188
at the time. He was tracing one of our endpoints in AWS
:
Hey Florin,
Do you have a traceroute showing the issue? FYI, you can test against
any
of the IPs listed here under US-West-2, they all respond to ICMP
requests.
http://ec2-reachability.amazonaws.com/
-Phil
On Fri, Apr 28, 2017 at 1:33 PM, Florin Andrei
wrote:
On 2017-04-28 13:28, Niels
On 2017-04-28 13:28, Niels Bakker wrote:
* flo...@andrei.myip.org (Florin Andrei) [Fri 28 Apr 2017, 21:12 CEST]:
I've seen a few strange instances where IP addresses in the AWS
us-west-2 region (Oregon) are routed through Europe if you start the
traceroute from some providers in the nor
I've seen a few strange instances where IP addresses in the AWS
us-west-2 region (Oregon) are routed through Europe if you start the
traceroute from some providers in the northern East Coast (Quebec, New
York). Any idea what's going on? I assume it's temporary.
--
Flo
On 2015-09-18 14:57, andrew wrote:
L3 fiber cut .
Is this related to the wave of deliberate fiber cuts on the West Coast
this year?
--
Florin Andrei
http://florin.myip.org/
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 &quo
.|-- ??? 100.0 80.0 0.0 0.0 0.0
0.0
--
Florin Andrei
http://florin.myip.org/
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 A
8 matches
Mail list logo
