Hello everyone!
Thank you again for the patience on this issue. We pushed out today what we believe is a viable work-around to this network connectivity issue. The work-around should fix the reliability issues that were causing connections to be reset.
The caveat to the work-around is that if your job enables IP ranges and pushes anything to a destination that is hosted by the content delivery network (CDN) Fastly, the outgoing job traffic will not be routed through one of the well-defined IP addresses listed above. Instead, the IP address will be one of the IPs that AWS uses in the us-east-1 or us-east-2 regions. This is a known issue between AWS and Fastly that CircleCI is working to resolve.
Please reply and let us know if this does not solve the connectivity issue for your team.