AWS Routing from EC2

Hi Guys

Just noticed that as of today, all of our EC2 instances are showing some very odd addresses when performing a trace-route to any of our data-center's servers.

traceroute to aphrodite.launtel.net.au (45.248.48.18), 30 hops max, 60 byte packets 1 ec2-54-252-0-50.ap-southeast-2.compute.amazonaws.com (54.252.0.50) 14.373 ms ec2-54-252-0-56.ap-southeast-2.compute.amazonaws.com (54.252.0.56) 13.936 ms ec2-54-252-0-54.ap-southeast-2.compute.amazonaws.com (54.252.0.54) 12.975 ms 2 100.66.8.4 (100.66.8.4) 14.674 ms 100.66.8.28 (100.66.8.28) 21.099 ms 100.66.8.60 (100.66.8.60) 12.615 ms 3 100.66.11.108 (100.66.11.108) 16.102 ms 100.66.10.200 (100.66.10.200) 12.966 ms 100.66.10.70 (100.66.10.70) 14.562 ms 4 100.66.7.229 (100.66.7.229) 18.039 ms 100.66.6.107 (100.66.6.107) 21.333 ms 100.66.6.35 (100.66.6.35) 13.753 ms 5 100.66.4.227 (100.66.4.227) 18.660 ms 100.66.4.187 (100.66.4.187) 12.907 ms 100.66.4.29 (100.66.4.29) 22.398 ms 6 100.65.11.161 (100.65.11.161) 0.861 ms 100.65.8.1 (100.65.8.1) 0.368 ms 100.65.9.33 (100.65.9.33) 1.241 ms 7 52.95.38.225 (52.95.38.225) 14.028 ms 52.95.38.213 (52.95.38.213) 1.549 ms 52.95.38.211 (52.95.38.211) 3.794 ms 8 52.95.36.56 (52.95.36.56) 2.683 ms 52.95.36.136 (52.95.36.136) 1.744 ms 52.95.36.40 (52.95.36.40) 1.640 ms 9 52.95.37.51 (52.95.37.51) 1.244 ms 52.95.36.99 (52.95.36.99) 1.318 ms 52.95.37.51 (52.95.37.51) 1.275 ms 10 as134697.sydney.megaport.com (103.26.69.27) 1.555 ms 134697.syd.equinix.com (45.127.173.35) 1.518 ms as134697.sydney.megaport.com (103.26.69.27) 1.686 ms 11 bacchus.launtel.net.au (45.248.51.207) 27.234 ms 27.162 ms 27.007 ms 12 45-248-48-18.dyn.launtel.net.au (45.248.48.18) 26.829 ms 26.981 ms 26.837 ms 

As you can see, the CGNAT addresses at the top (100.xx.x.x) are what I have observed as new.

Is this is something Amazon does now or is this a cause for a ticket? Routing through a bunch of CGNAT seems very odd.