I seriously doubt there's anything we can do about this. Without a traceroute we can't even do basic troubleshooting. Short of that you could try to ping bitbucket.org from the problematic network and also telnet to 'bitbucket.org 443'. In all likelihood your campus network admins are blocking us for some reason. We're certainly not blocking you coming from that IP range. It might be worth trying your operations over ssh -- perhaps port 22 isn't blocked.
I would recommend you contact the Northeastern IT department, or perhaps the department that runs the 129.10.*.* network. If you think there's anything we can do to help please let us know.