Does Square do anything when we submit packet loss and latency info?
It's an honest question.
I only ask because I went through my old logs folder and found traceroutes and pathpings showing the same issue locations and they were from Sept. 2022. And that was just when I tried to start keeping track of them.
In other words, I've been submitting this data for over 9 months and nothing has changed. It's still pretty much:
5. 16-21 16-21 16-21 Last Comcast/Xfinity IP
6. 35-45 35-45 35-45 chicago NTT
7 thru 12 (up to 16):
San Jose / Sacramento area hops where latencies are low 87, high around 104 and usually a bunch of no replies. Some may have one or two, but there's almost always one that is all no replies and sometimes doesn't even return it's IP address.
I've tried every legal fix/workaround I can find and nothing changes these. If it does manage to not come in through LA, SJ, or SCR, the latency added from going around somehow makes it just as bad or worse.
How many more months of reports do I have to submit, or does SE just blackhole them and pretend they're analyzing the data?
Edit:
Here are the three I've submitted today from different times of day (morning, afternoon, evening)
1 2 ms 2 ms 2 ms <removed>
2 11 ms 11 ms 11 ms <removed>
3 18 ms 13 ms 15 ms <removed>
4 16 ms 17 ms 14 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 15 ms 23 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 18 ms 16 ms 17 ms 75.149.231.250
7 42 ms 37 ms 37 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 82 ms * 87 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 85 ms 108 ms 85 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 90 ms 87 ms 97 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * 87 ms 204.2.29.241
12 85 ms 85 ms 85 ms 204.2.29.122
--- ---
1 1 ms 1 ms 1 ms <removed>
2 12 ms 11 ms 14 ms <removed>
3 12 ms 11 ms 12 ms <removed>
4 14 ms 15 ms 13 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 16 ms 17 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 18 ms 23 ms 14 ms 75.149.231.250
7 36 ms 43 ms 37 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 * 82 ms 79 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 84 ms 85 ms 86 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 83 ms 83 ms 84 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 * * * Request timed out.
12 83 ms 94 ms 85 ms 204.2.29.122
--- ---
1 2 ms 1 ms 2 ms <removed>
2 12 ms 12 ms 11 ms <removed>
3 12 ms 12 ms 9 ms <removed>
4 18 ms 17 ms 17 ms be-58-ar01.needham.ma.boston.comcast.net [96.108.47.109]
5 15 ms 19 ms 15 ms be-1005-pe11.onesummer.ma.ibone.comcast.net [68.86.90.66]
6 15 ms 13 ms 15 ms 75.149.231.250
7 39 ms 38 ms 38 ms ae-2.r23.chcgil09.us.bb.gin.ntt.net [129.250.4.102]
8 * 91 ms 79 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 84 ms * 87 ms ae-4.a00.scrmca03.us.bb.gin.ntt.net [129.250.7.57]
10 86 ms 83 ms 86 ms xe-0-0-5-0.a00.scrmca03.us.ce.gin.ntt.net [128.241.2.18]
11 86 ms * * 204.2.29.241
12 85 ms 83 ms 86 ms 204.2.29.122
Trace complete.