Depends on just who manages that hop though. If it is a problem occurring prior to Ormuco (even at the exchange point into Ormuco) than it could be a problem with the top tier ISP's like TATA, LEvel3, Cogent, TiNet/SPA, or Verizon Business (ALTER.NET). If so, then TWC is in part responsible for the issue, and there would in fact be something TWC can do about it--as they are the ones who set up the agreement to use that specific third party ISP for transit to Ormuco. If they can't get that third party to remedy it somehow, they can change you to use one of their other routing partners.
Put in the proper perspective, then yes... TWC may have some ownership in the problem.
There is a fairly simple test you can run yourself to try to demonstrate it, and in fact was how I convinced one on-site technician they needed to escalate the problem for me. Test different VPN endpoints. Many out there offer trial or permanent free use that can provide enough usage to run some short tests. Some cap so many hours a day/week, or so much data per month on a renewing basis (like tunnelbear has a free plan that gives 500MB/month, while ones like Cyberghost or HotspotShield limit you to a few hours a day and/or so many hours a week).
If you can get the game to run more stable with a VPN, then it is clearly an issue with the path you are getting assigned to get to Ormuco. That is something determined by the policies of your ISP and/or who you are using for transit to get across the internet to a remote network (in this case, Ormuco). Your ISP sets the parameters for who provides that transit as well as how you get to their exchange point--a VPN allows you to bypass or at least dramatically alter those decisions.
So if using a VPN fixes things then there is a problem with the route your ISP has assigned to you and they need to either arrange to fix that route or switch you to an alternate path to avoid the troubled segments. Either solution is within their power.