R3 @ jitter

[Reykc9510]

So this is whats going on, I have switched internet providers 3 times in 2 weeks. I had metro net fiber 1 gig up an down for 2 years. Recently my ping went from 21 42 an jitter went from 0.4 0.6ish to 8 to 12 ms of jitter. 

I switched to wire 3 fiber 2gig up n down everything worked great had 9 ping an jitter was 0.4 0.6ish then all the sudden around 730 1030 at night it was horrible.  Then it got bad randomly.  I went back to metro net. They completely re wired the wire an modem worked great then boom 3 days later went to poopy again. After 3 hrs with customer service this evening they said everything on their end is working, can it be my router? I said good question.  Let me reach out an see. R3 everything is hardwired.  I have the beta version of the software there newest one. I have done a hard reset numerous times. Have all cat 6 ethernet cables.  Have CC dailed in. I'm stuck because I do not know how to rectify the problem. How can I tell if its the router? I had a tech here this afternoon showed him the stats on buffer bloat an had to explain an educate about jitter. Any ideas ln how an what i can do to fix this?

[DARKNESS]

@Reykc9510

You're creating a new topic for the same issue, but I want to highlight that using Waveform as your jitter test is not a reliable measurement tool. It doesn’t provide details about server locations, so you might end up testing a server far away—potentially 1,000 miles—which could distort the jitter results. The most accurate approach is to use PingPlotter. When testing, share a screenshot of your graph while your network is idle, ensuring there’s no activity for at least 5 minutes. Enable maximum latency on PingPlotter to get a clear view of your network performance. To create a shareable link, click "File," then "Create Share Page," and follow the steps. Use google.com as the test target for better accuracy. Remember, not all technicians are highly experienced—many rely solely on the tools provided by their company and may overlook complex issues. Often, effective troubleshooting falls on you unless the problem is easily detectable.