We experienced an issue where thousands of connections were being held open to Auth0. A sample connection appeared like this after running lsof:
TCP ip-172-30-2-68.eu-west-1.compute.internal:49970->ec2-52-28-229-49.eu-central-1.compute.amazonaws.com:https
This was preventing the application from making any other http requests and the result to users was that the user token could not be verified. If encountered in the future, it may be possible to kill off these TCP connections or simply restarting the server will work.
A potential fix might be to use the auth0 java library for getting the user profile in Auth0Connection.java, which may manage auth0 connections better.