Any recent issues with J:COM?

My apartment building uses J:COM which I've been using for a couple years without issue. However after going on vacation for a week and coming back, I'm seeing the following problems:

• Can't use VPNs reliably (maybe one or two requests then I get ERR_TIMED_OUT in my browser).
• Can't use SVN. A company I work for unfortunately uses SVN, and as soon as I try to do a checkout/up or anything that would suddenly download a flood of data, SVN stops working entirely (with the error that the hostname cannot be resolved).
• Can't even do a Speedtest.net. Once the test starts, a socket error occurs.

Has anyone else seen this? I've already removed my router from the equation, swapped out the apartment's LAN switcher with a spare device I have, and tried multiple devices (two PCs, one phone) with similar results (although the phone seems to be able to use a VPN). I've also confirmed the upstreams are not the issue as I can do SVN checkouts (for example) on remote machines over SSH.

My only guess is that either J:COM has begun blocking these kinds of requests/protocols, or some wiring or other hardware has gone bad such that it specifically drops these types of requests (seems unlikely, but I don't know anything about network hardware).