This issue appears to be related to scaled compute capacity not being added into the load balancer target group as expected. We have added this manually for now and we'll raise a ticket with AWS relating to the underlying issue. All service look normal at this stage
