At this point it's priced out unfortunately. About 10X the per Gbps price compared to the more mature routes. I head a rumour this week that Paratus is adding some new capacity on that corridor - which should help with pricing.
Howdy. Definitely looks like last mile.loss here- seemingly some sort of congestion if it's time based.. Please log so we can escalate to the FNO. Could be an oversubscribed PON port
Apologies for the late reply. Let me take a look here for you.
Update: Checked your line profile, all looks good on the Openserve side. I have performed a port re-create for you. If you're still seeing issues, please can you log a fault and we can get the team to escalate to Openserve.
VX is active ethernet and runs jumbo frame, so your L2TP session establishes at a full 1540 bytes (router supporting), delivering a full 1500 byte payload client side. No issues saturating the line at that speed and the overhead is contained by the larger packet.
PPPOE on a 1500 byte ethernet...
Howdy, will reach out. First things first, we still allocate public IPs (dynamic or static). There is no reason why you can't have a static IP via the L2TP, which has been tested extensively and runs at 1 Gbps+ without issue. VX has jumbo frame support, so overhead is not an issue. v6 is now...
In both these results, the deviation in latency (ping spikes) doesn't carry through to the last hop. This points to a router queuing and processing direct ICMP requests but not the rest of your traffic.
Similar to packet loss, you would see these same spikes through to subsequent hops and all...