For those wondering how bad the issue is, check out this[1] screenshot of a diff between the TLS/non-TLS html from www.example.com.
Here's "corrupted" UTF-8 characters expressed as bits. In this example you can see clearly what's happening. The top byte is correct and the second one is corrupted.
01100111 # g
01101111 # o
01110000 # p
01111000 # x
01101100 # l
01100100 # d
01100101 # e
01101101 # m
I'm on Fiber from Sonic and last week I was experiencing issues with connections randomly being dropped and being extremely slow to load. Sonic tech came out and said that the uplink was good and that it might be a problem with my UniFi system, but I don't have any issues with my LAN services.
It's great that the community was able to diagnose this, but a shame that AT&T didn't pick it up first and isn't acknowledging an issue on their network.
6 comments
[ 2.9 ms ] story [ 41.9 ms ] threadHere's "corrupted" UTF-8 characters expressed as bits. In this example you can see clearly what's happening. The top byte is correct and the second one is corrupted.
1. https://i.imgur.com/qIMnTTe.pngIt's great that the community was able to diagnose this, but a shame that AT&T didn't pick it up first and isn't acknowledging an issue on their network.