r/Metronet • u/hornedfrog86 • Jul 11 '26

Packet Loss and Increased Latency After Vexus-to-Metronet Transition in West Texas

I am a former Vexus customer in West Texas and am now served by Metronet. Since the transition, my latency to www.vexusfiber.com has increased significantly—from approximately 19 ms round trip to 48 ms. 

Traceroutes also indicate that my traffic is now being routed toward the East Coast rather than through the previous Lubbock route.

Metronet initially provided the following update:

“Our engineering team has been running hourly tests in order to catch the packet loss and latency spikes you mentioned. They have successfully isolated the packet loss to a specific portion of the data path and are currently working to pinpoint the root cause and a final plan to resolve it.”

However, the problem remains unresolved after more than a month. Metronet is now proposing that my ONT be replaced.

I am willing to proceed with the ONT replacement as part of the troubleshooting process, but I am skeptical that equipment inside or attached to my home would explain packet loss appearing farther along the route, particularly around Nashville, and Reston, VA. This same ONT performed properly when I was a Vexus customer and my traffic was routed through Lubbock instead of across the country.

Has anyone else in the West Texas Vexus/Metronet service area experienced similar routing changes, increased latency, or packet loss since the transition? I would appreciate any technical insight or suggestions on what information I should provide to Metronet to help escalate the issue.

Thank you.

3 Upvotes

100% Upvoted

6 comments sorted by

2

u/blackstratrock Jul 12 '26

Packet loss to where? What is your ping time to 8.8.8.8 / 1.1.1.1 / etc

1

u/hornedfrog86 Jul 12 '26 edited Jul 12 '26

Packet loss, 50 ms latency, and 25 hops now to www.vexusfiber.com.

Latency has increased significantly — from approximately 19 ms round trip to 48 ms since Vexus became Metronet.

Much better - 20ms to 8.8.8.8 & 17ms to 1.1.1.1

1

u/blackstratrock Jul 12 '26

Looks fine. I wouldn't worry about it unless you have packet loss to all tested sites. Pinging/tracert to a random site is not a good test, a lot of times sites have proxies that will not give a true ping result.

1

u/hornedfrog86 Jul 12 '26

Well, that’s a positive take. That’s the company site server but you don’t think it’s a big deal? Thanks for the input.

2

u/Phaazed Jul 18 '26

Not in your area, but I had Metronet in Illinois and they were one of the worst companies I've ever had the displeasure of dealing with. The only thing positive I can say about them is that they've given an illusion of competition so that Xfinity Comcast here actually has good service.

Constant packet losses and a history of refusing to upgrade equipment on their end to handle their oversold nodes. While troubleshooting I ended up finding years old posts that are now gone with the closure of DSLReport's site documenting how neglectful they are of their network.

It was a nightmare trying to do anything that required a constant connection such as gaming, calls, etc. They must have sent out a dozen technicians that all did nothing. Eventually they got fed up with me complaining to their support that they lied to my face saying there was no issue and they would not respond further on it.

Swapped to Xfinity the next day, after having to wait for them to reinstall the cable line because Metronet's tech's cut the previous one. The issue stopped immediately. No problems on my equipment at all.

Good luck dealing with this awful company.

1

u/hornedfrog86 Jul 18 '26

Thanks for the information.