Seeing the exact same issue from Texas. It's definitely not my ISP, it's whatever ISP SE is using within their server datacenter. It's been happening since Sunday night and it's really killing the mood for trying to run anything during my evenings.

Tracert from my location to the SE datacenter here, as well as seen packet loss occurring when running a constant ping to that same location:

5 11 ms 14 ms 15 ms 32.130.16.9
6 12 ms 9 ms 9 ms gar25.dlstx.ip.att.net [12.122.85.233]
7 30 ms 9 ms 11 ms ae-5.a00.dllstx14.us.bb.gin.ntt.net [129.250.8.237]
8 9 ms 8 ms 9 ms ae-2.r21.dllstx14.us.bb.gin.ntt.net [129.250.4.19]
9 46 ms 45 ms 49 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
10 173 ms 152 ms 177 ms ae-5.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.146]
11 178 ms 168 ms 179 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
12 209 ms 171 ms 176 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
13 * 154 ms * 204.2.229.230
14 173 ms 154 ms 183 ms 204.2.229.10

Packet loss seen:
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=117ms TTL=48
Reply from 204.2.229.10: bytes=32 time=190ms TTL=48
Reply from 204.2.229.10: bytes=32 time=212ms TTL=48
Reply from 204.2.229.10: bytes=32 time=206ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=200ms TTL=48
Reply from 204.2.229.10: bytes=32 time=198ms TTL=48
Reply from 204.2.229.10: bytes=32 time=185ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=194ms TTL=48
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=208ms TTL=48
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=204ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=194ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Reply from 204.2.229.10: bytes=32 time=203ms TTL=48
Reply from 204.2.229.10: bytes=32 time=199ms TTL=48
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=197ms TTL=48
Reply from 204.2.229.10: bytes=32 time=188ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=202ms TTL=48
Reply from 204.2.229.10: bytes=32 time=183ms TTL=48
Reply from 204.2.229.10: bytes=32 time=210ms TTL=48
Reply from 204.2.229.10: bytes=32 time=205ms TTL=48
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48
Reply from 204.2.229.10: bytes=32 time=195ms TTL=48
Reply from 204.2.229.10: bytes=32 time=163ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=201ms TTL=48
Reply from 204.2.229.10: bytes=32 time=207ms TTL=48
Request timed out.
Reply from 204.2.229.10: bytes=32 time=188ms TTL=48
Reply from 204.2.229.10: bytes=32 time=209ms TTL=48

Ping statistics for 204.2.229.10:
Packets: Sent = 12503, Received = 12316, Lost = 187 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 219ms, Average = 118ms