hey ben, thanks for the reply
unfortunately i didnt export my report. as of now the issue seems to have resolved itself, again.
i will run it again tomorrow evening if/when it occurs and export it. also, the issue persists when connected directly to the modem, i know thatll be the first suggestion when i post the report and the first hop is 192.x.x.x.
others in my residence will be active during this timeframe and killing the (spotty) wifi just to get the same results will cause unnecessary frustration.
currently occurring:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.67.128.1 - 21 | 87 | 69 | 5 | 12 | 36 | 7 |
| 100.127.4.162 - 21 | 87 | 69 | 6 | 13 | 37 | 7 |
| 100.120.102.28 - 22 | 84 | 66 | 6 | 16 | 74 | 25 |
| langbprj02-ae1.0.rd.la.cox.net - 23 | 83 | 64 | 13 | 23 | 65 | 13 |
| 74.125.51.174 - 26 | 79 | 59 | 13 | 19 | 55 | 14 |
| 108.170.238.54 - 24 | 80 | 61 | 14 | 21 | 57 | 31 |
| 74.125.251.39 - 26 | 79 | 59 | 13 | 22 | 56 | 15 |
| dns.google - 20 | 88 | 71 | 12 | 19 | 79 | 30 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
