Re: AWS us-west-2 routed through Europe from NY?
That's embarrassing. Thanks for opening my eyes. Sorry for wasting everyone's time. On 2017-05-01 11:34, Nikolas Geyer wrote: It hasn't gone through Europe, it's just most of Telia's IP space will return a geolocation of Europe. The trace provided goes to New York, Chicago then Seattle. Sent from my iPhone On 1 May 2017, at 2:10 pm, Florin Andrei <flo...@andrei.myip.org> 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 us-west-2; I do not know which IPs our endpoint had at the time, but one of its current IPs is 52.89.73.31 This is the trace as he described it: Route - #1: 2.7 ms IP Address: 192.168.1.1 Hostname: local TTL: 64 - #2: 34.8 ms IP Address: 10.170.162.238 TTL: 50 - #3: 17.3 ms IP Address: 10.170.192.53 TTL: 250 - #4: 16.7 ms IP Address: 74.116.184.145 Hostname: 0.xe-11-1-0.er1.mtl7.ebox.ca TTL: 249 AS Number: AS1403 AS Name: EBOX Country Name: Canada Country Code: CA Time Zone: America/Toronto Region: Quebec City: Vieux-Saint-Laurent Latitude: 45.475 Longitude: -73.696 - #5: 15.6 ms IP Address: 213.248.76.201 Hostname: motl-b1-link.telia.net TTL: 248 AS Number: AS1299 AS Name: Telia Company AB Country Name: Europe Country Code: EU Time Zone: Europe/Vaduz - #6: 31.8 ms IP Address: 62.115.134.52 Hostname: nyk-bb4-link.telia.net TTL: 247 AS Number: AS1299 AS Name: Telia Company AB Country Name: Europe Country Code: EU Time Zone: Europe/Vaduz - #7: 47.7 ms IP Address: 213.155.136.19 Hostname: chi-b21-link.telia.net TTL: 246 AS Number: AS1299 AS Name: Telia Company AB Country Name: Europe Country Code: EU Time Zone: Europe/Vaduz - #8: 89.7 ms IP Address: 62.115.117.48 Hostname: sea-b1-link.telia.net TTL: 245 AS Number: AS1299 AS Name: Telia Company AB Country Name: Europe Country Code: EU Time Zone: Europe/Vaduz - #9: 90.7 ms IP Address: 62.115.34.102 Hostname: amazon-ic-302508-sea-b1.c.telia.net TTL: 244 AS Number: AS1299 AS Name: Telia Company AB Country Name: Europe Country Code: EU Time Zone: Europe/Vaduz - #10: 86.3 ms IP Address: 52.95.52.80 TTL: 239 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Washington City: Seattle Latitude: 47.634 Longitude: -122.342 - #11: 80.8 ms IP Address: 52.95.52.97 TTL: 241 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Washington City: Seattle Latitude: 47.634 Longitude: -122.342 - #12: 86.1 ms IP Address: 54.239.43.124 TTL: 240 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Washington City: Seattle Latitude: 47.610 Longitude: -122.334 - #13: 94.3 ms IP Address: 52.93.13.12 TTL: 235 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Oregon City: Boardman Latitude: 45.870 Longitude: -119.688 - #14: 86.5 ms IP Address: 52.93.12.249 TTL: 238 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Oregon City: Boardman Latitude: 45.870 Longitude: -119.688 - #15: 111.7 ms IP Address: 52.93.12.140 TTL: 234 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Oregon City: Boardman Latitude: 45.870 Longitude: -119.688 - #16: 92.6 ms IP Address: 52.93.12.173 TTL: 234 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Oregon City: Boardman Latitude: 45.870 Longitude: -119.688 - #17: 88.3 ms IP Address: 52.93.15.217 TTL: 236 Country Name: United States Country Code: US Time Zone: America/Los_Angeles Region: Oregon City: Boardman Latitude: 45.870 Longitude: -119.688 - #18: N/A TTL: 0 We expected that trace to go straight East Coast / West Coast, but instead it went through Europe. For comparison, this is a trace also by same coworker to api.postmates.com, which was correctly routed on the shortest geographical path (more or less): Route - #1: 3.0 ms IP Address: 192.168.1.1 Hostname: local TTL: 64 - #2: 29.0 ms IP Address: 10.170.162.238 TTL: 50 - #3: 17.9 ms IP Address: 10.170.192.53 TTL: 250 - #4: 19.7 ms IP Address: 74.116.184.145 Hostname: 0.xe-11-1-0.er1.mtl7.ebox.ca TTL: 249 AS Number: AS1403 AS Name: EBOX Country Name: Canada Country Code: CA Time Zone: America/Toronto Region: Quebec City: Vieux-Saint-Laurent Latitude: 45.475 Longitude: -73.696 - #5: 17.7 ms IP Address: 96.127.249.30 TTL: 248 AS Number: AS1403 AS Name: EBOX Country Name: Canada Country Code: CA Time Zone: America/Toronto Region: Quebec City: Longueuil Latitude: 45.518 Longitude: -73.502 - #6: 18.0 ms IP Address: 198.179.18.55 Hostname: cloudflare.peer.qix.ca TTL: 247 Country Name: Canada Country Code: CA Time Zone: America/Toronto Region: Quebec City: Montreal Latitude: 45.501 Longitude: -73.568 - #7: 17.6
Re: AWS us-west-2 routed through Europe from NY?
Francisco Latitude: 37.770 Longitude: -122.393 On 2017-04-28 17:05, Phillip McGuire wrote: 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 <flo...@andrei.myip.org> wrote: 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 northern East Coast (Quebec, New York). Any idea what's going on? I assume it's temporary. Can you be a little bit more vague in your problem description? While ommitting the source networks from where you tried, you still included the destination. The list expects better. Sorry. Here's one source: 104.163.180.188 -- Florin Andrei http://florin.myip.org/ -- Florin Andrei http://florin.myip.org/
Re: AWS us-west-2 routed through Europe from NY?
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 northern East Coast (Quebec, New York). Any idea what's going on? I assume it's temporary. Can you be a little bit more vague in your problem description? While ommitting the source networks from where you tried, you still included the destination. The list expects better. Sorry. Here's one source: 104.163.180.188 -- Florin Andrei http://florin.myip.org/
AWS us-west-2 routed through Europe from NY?
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. -- Florin Andrei http://florin.myip.org/
Re: high latency on West Coast?
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/
high latency on West Coast?
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/
Re: high latency on West Coast?
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.10.0%10 10.6 6.0 1.0 17.1 5.2 2.|-- 10.1.10.1 0.0%103.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%109.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.0100.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.0100.0 0.0 0.0 0.0 0.0 12.|-- ??? 100.0100.0 0.0 0.0 0.0 0.0 13.|-- ??? 100.0100.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.0100.0 0.0 0.0 0.0 0.0 16.|-- 205.251.225.2150.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.2010.0% 9 216.6 225.5 206.3 254.8 15.5 19.|-- 205.251.230.1270.0% 8 201.0 212.5 201.0 225.1 7.3 20.|-- ??? 100.0 80.0 0.0 0.0 0.0 0.0 1.|-- 192.168.1.10.0%108.8 14.2 0.9 66.2 19.2 2.|-- 10.1.10.1 0.0%107.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.0100.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.3210.0%10 213.0 245.7 208.2 377.9 53.2 11.|-- ??? 100.0100.0 0.0 0.0 0.0 0.0 12.|-- ??? 100.0100.0 0.0 0.0 0.0 0.0 13.|-- ??? 100.0100.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.0100.0 0.0 0.0 0.0 0.0 16.|-- 205.251.225.2150.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.2010.0% 9 236.1 232.5 205.8 261.2 18.3 19.|-- 205.251.230.1270.0% 8 206.1 233.2 206.1 287.3 24.8 20.|-- ??? 100.0 80.0 0.0 0.0 0.0 0.0 -- Florin Andrei http://florin.myip.org/
Re: high latency on West Coast?
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/
