Yeah definitely the AWS path- and getting anything from their NOC is near impossible.
There was/is (I’m struggling to find updates) a break between Egypt and ME. Looking at the latency here- it seems that AWS are using a L2 overlay here - that first hop out of S.A doesn’t tell us much about how they’re getting there.
Generally once a path is restored, AWS soaks it for a while before bringing it back up.Tracing route to ec2-157-175-31-202.me-south-1.compute.amazonaws.com [157.175.31.202]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ARCHER_D2 [192.168.1.2]
2 75 ms 3 ms 2 ms 160.119.237.161
3 2 ms <1 ms <1 ms core.as-01.db1.za.ws.net.za [160.119.233.225]
4 8 ms 8 ms 8 ms 160.119.232.122
5 8 ms 8 ms 9 ms 196-60-9-105.ixp.joburg [196.60.9.105]
6 11 ms 9 ms 9 ms 52.93.56.120
7 8 ms 9 ms 8 ms 52.93.56.135
8 * * * Request timed out.
9 242 ms 245 ms 232 ms 52.93.225.92
10 231 ms 231 ms 231 ms 52.93.225.105
11 232 ms 244 ms 244 ms 52.93.224.156
12 232 ms 232 ms 254 ms 52.93.224.151
13 232 ms 235 ms 232 ms 52.93.227.54
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 231 ms 231 ms 231 ms ec2-157-175-31-202.me-south-1.compute.amazonaws.com [157.175.31.202]
Trace complete.
I'm pretty sure it is the AWS, cause this is a middle eastern server which I know used to have a good ping of around 125ms, now sitting at 230+, if you need any more information I'm happy to provide.
Thank you
Will keep looking for updates on the break
