Didn't find what you were looking for?
We have advanced search options to make it easier to locate posts, questions and answers on this community.
More information can be found at Advanced Search Options
If you are looking for something specific, please check if someone else has already asked or answered the same question.
High Latency Between Node & Another Provider's Backbone
Hello
I'm noticing a seriously high latency / ICMP response time between where I live now (non-Spectrum) and the newly installed service.
I just had service setup at our new home.
Several units of existing utility equipment were replaced on the poles between the node and my home, including a brand new line between the last pole and my garage. Signup to installation completion was extremely fast - very impressive. The line technician showed me the test result on-site, concluding there was ZERO PERCENT LOSS between my modem and the node.
So layer 1 / physical connection is confirmed solid.
The IP block I need to access with very low latency is owned by 123Net, in Southfield
BGP range = 216.234.96.0/19
Using any ping-able hostname / IP from this list
I can't share which hostname / IP exactly - but any ping started to an IP in that list from the URL above, provides the same results:
NEW SITE (Spectrum) ~70 ms response time
OLD SITE (Non-Spectrum) ~15 ms response time
I perform Remote Desktop work from home and latency / response time is extremely important to my application
Considering that the new site and old site are 5 miles away from each other albeit the service providers are different…
I am wondering if engineering can identify a potential routing / traffic management performance issue between my the node for my new site and the BGP range (216.234.96.0/19) for 123Net
Any help or feedback would be greatly appreciated!
Best Answer
-
Six days later….
Thanks engineering!
Love,
Mitch
0
Answers
-
Got 45-55ms pings from my router's network tools here in South Carolina. During traces, didn't see any notable queuing happening until I got into 123's edge network...particularly at 69.39.66.244.
Out of curiosity... have you noticed if any IPv6 resolution is in play? Every time I tested it in the past in my market, I found the odd service showing worse jitter with v6 and wound up turning it back off. Still running IPv4 since I haven't "needed" v6 yet.
0 -
@RAIST515O let me check some parameters and make sure. Got a temporary router setup at new site until I can bring my 2.5 gig router / firewall over from current site after the move.
0
