That’s inside the container, so you could have a docker networking issue, or it could have been a temporary issue?