Further to the video below, we have a high priority issue that needs to be resolved within app.islg. We have had multiple reports from users indicating that they were getting access to George Mason University account, which has an IP address range accessible between 10.0.0.1 and 10.255.255.254:

image.png 91.3 KB • Download

When examining the usage details for George Mason University, between 2:24am and 8:43am EST, there was a sudden spike in Auto-IP usage on the account all coming through the same IP address: 10.68.138.10

image.png 125 KB • Download

This appears to be all auto-IP usage across the all subscribers during that period. Meaning every user (across all accounts) accessing the system via Auto-IP was getting their usage registered as originating 10.68.138.10 even though that is not IP address where the user was located when they accessed the system.

I assume that this issue is related to the deployment to app.islg that was occurring around this time, and the issue appeared to be resolved by 8:43am EST, but I'm very concerned that this happened. 

Harsh , can you please investigate the issue as a high priority and report back what happened and confirm whether the issue is now resolved. Also, I'm very concerned that this happened at all, and we need to examine how we're making deployments to app.islg going forward.

In the interim, we have disabled access to the 10.0.0.1 - 10.255.255.254 range, but we want to ensure we restore access as soon as possible so that we're not restricting access to users from the George Mason University's account.

Problem with IP access in app-islg (28-Apr-21).mp4 6.41 MB • Download