Re: AWS issues with 172.0.0.0/12

[Mehmet Akcin <mehmet () akcin net>]

Hey Andras

Here you go

Warning: www.reolink.com has multiple addresses; using 52.21.66.90
traceroute to www.reolink.com (52.21.66.90) , 5 relative hops max, 52 byte
packets
   1 192.168.7.1 (192.168.7.1) 4.200 ms 55.354 ms 56.375 ms
   2 192.168.1.254 (192.168.1.254) 5.175 ms 56.006 ms 57.214 ms
   3 75-55-252-1.lightspeed.irvnca.sbcglobal.net (75.55.252.1) 7.264 ms
380.989 ms 382.969 ms
   4  *
     71.147.164.53 (71.147.164.53) 5899.218 ms 5979.390 ms
   5 71.147.164.53 (71.147.164.53) 0.394 ms
     cr1.la2ca.ip.att.net (12.123.30.78) 40.402 ms 214.075 ms
   6 cr1.la2ca.ip.att.net (12.123.30.78) 0.452 ms
     12.122.2.166 (12.122.2.166) 39.478 ms 213.425 ms
   7 12.122.2.166 (12.122.2.166) 0.393 ms
     12.122.2.81 (12.122.2.81) 36.410 ms 210.089 ms
   8 12.122.2.81 (12.122.2.81) 0.508 ms
     12.123.18.209 (12.123.18.209) 35.774 ms 111.450 ms
   9 12.123.18.209 (12.123.18.209) 0.383 ms
     12.244.76.10 (12.244.76.10) 36.579 ms 136.809 ms
 10 12.244.76.10 (12.244.76.10) 0.454 ms * *
 11  * * *
 12  * * *
 13  *

On Mon, Sep 30, 2019 at 23:32 Andras Toth <diosbejgli () gmail com> wrote:

> Hi Mehmet,
>
> A traceroute would be particularly useful.
>
> Have you tried accessing http://ec2-reachability.amazonaws.com/ to verify
> if the green icons load? If not, any particular region that's broken? Could
> you collect a traceroute towards some of the working and non-working IPs
> listed there?
>
> Andras
>
> On 1 Oct 2019, at 16:29, Mehmet Akcin <mehmet () akcin net> wrote:
>
> 
>
> Hey there
>
> AT&T is using 172.0.0.0/12 block as public IP for customers in USA. AWS
> seems to be blocking this block, I can reach to many sites just fine but i
> can’t get to some sites hosted on AWS such as reolink.com
>
> If someone from AWS is reading the list, please fix this issue
>
> Mehmet
> --
> Mehmet
> +1-424-298-1903
>
> --
Mehmet
+1-424-298-1903