Have you tried tracking the latency below persistently to see what
happens when the next disconnect occurs? The latency below alone likely
wouldn't cause a disconnect, it might have some drastic spikes or packet
loss when the issues occur.
From AT&T in SATX
64 bytes from 8.8.8.8: icmp_seq=0 ttl=56 time=12.155 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=11.019 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=11.479 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=10.899 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=10.852 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=11.261 ms
64 bytes from (to Ashburn VA): icmp_seq=0 ttl=46 time=44.093 ms
64 bytes from (to Ashburn VA): icmp_seq=1 ttl=46 time=44.169 ms
64 bytes from (to Ashburn VA): icmp_seq=2 ttl=46 time=44.416 ms
64 bytes from (to Ashburn VA): icmp_seq=3 ttl=46 time=45.020 ms
64 bytes from (to Ashburn VA): icmp_seq=4 ttl=46 time=50.492 ms
64 bytes from (to Ashburn VA): icmp_seq=5 ttl=46 time=44.620 ms
Tom Sands
Principal Architect
Sr Director of Networking
Rackspace Technology
On 1/3/24 1:21 PM, Bruce Orcutt via Outages wrote:
CAUTION: This message originated externally, please use caution when
clicking on links or opening attachments!
SOrry, forgot to mention, Spectrum also.
Bruce Orcutt
UTSA Libraries: Systems
(210) 458 – 6192
------------------------------------------------------------------------
*From:* Outages <[email protected]> on behalf of William
Peebles via Outages <[email protected]>
*Sent:* Wednesday, January 3, 2024 1:02 PM
*To:* [email protected] <[email protected]>
*Subject:* [EXTERNAL] [outages] Spectrum latency in SATX area
* **EXTERNAL EMAIL***
This email originated outside of The University of Texas at San Antonio.
Please exercise caution when clicking on links or opening attachments.
We have a few remote employees with Spectrum in different locations in
the San Antonio area who have had a lot of VPN disconnects today due
to high latency between their machines and our firewall in Boston.
Spectrum customer service gave them the typical run-around speech
about how it's our problem and not theirs, but even Google and
Cloudflare are giving higher pings than usual
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=41ms TTL=57
Reply from 8.8.8.8: bytes=32 time=35ms TTL=57
Reply from 8.8.8.8: bytes=32 time=32ms TTL=57
Reply from 8.8.8.8: bytes=32 time=38ms TTL=57
---
Pinging (redacted) with 32 bytes of data:
Reply from (redacted): bytes=32 time=76ms TTL=239
Reply from (redacted): bytes=32 time=69ms TTL=239
Reply from (redacted): bytes=32 time=64ms TTL=239
Reply from (redacted): bytes=32 time=62ms TTL=239
Sent with Proton Mail
<https://proton.me/>
secure email.
_______________________________________________
Outages mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/outages
_______________________________________________
Outages mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/outages
