This is only to AWS services? It would be using our direct connect in Johannesburg, I'm going to filter it out for Cape Town customers today if all goes well, until we get a direct connect in Cape Town as well.
The two AWS instances are EC2 instances.
Here is a trace route to my London instance:
1 <1 ms <1 ms <1 ms 172.18.7.225
2 1 ms <1 ms <1 ms 155.93.248.1
3 1 ms <1 ms <1 ms 154.0.1.125
4 1 ms 1 ms 1 ms 154.0.1.13
5 21 ms 21 ms 21 ms 154.0.1.245
6 21 ms 20 ms 20 ms unq-cust.coolideas.co.za [154.0.3.86]
7 21 ms 21 ms 21 ms 154.0.3.26
8 21 ms 23 ms 21 ms 52.95.106.82
9 21 ms 21 ms 22 ms 52.93.56.74
10 21 ms 21 ms 21 ms 52.93.56.87
11 185 ms 185 ms 185 ms 54.239.46.78
12 185 ms 185 ms 185 ms 54.239.46.87
13 * * * Request timed out.
14 164 ms 164 ms 164 ms 52.94.35.43
15 184 ms 200 ms 201 ms 52.94.35.42
16 186 ms 186 ms 186 ms 52.94.33.141
17 185 ms 185 ms 185 ms 52.94.33.42
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 186 ms 185 ms 185 ms ec2-35-176-155-105.eu-west-2.compute.amazonaws.com [35.176.155.105]
Not too sure if there is anything i can do on my side to show you guys more?
P.S It was working just perfectly around 3 weeks ago, so not sure what changed or what the issue might be now