Highlighted
Not applicable

Intermitency that not even the technician could fix. Pls help

Been having intermitecny issues everyday for 2 weeks, they sent out a technician who said he couldnt see a problem. Hopefully someone here can help. Will post tracertand winmtr below. Thanks!

 

Tracert***************************


Tracing route to 137.221.105.2 over a maximum of 30 hops

1 4 ms 3 ms 1 ms SAGEMCOM [192.168.1.1]
2 11 ms 14 ms 11 ms 142.254.183.117
3 41 ms 168 ms 13 ms agg63.vnnzca2402h.socal.rr.com [76.167.27.53]
4 16 ms 15 ms 15 ms 72.129.14.86
5 19 ms 14 ms 24 ms agg29.tustcaft01r.socal.rr.com [72.129.13.2]
6 187 ms 22 ms 23 ms bu-ether16.tustca4200w-bcr00.tbone.rr.com [66.109.6.64]
7 14 ms 14 ms 14 ms 0.ae2.pr1.lax10.tbone.rr.com [107.14.19.54]
8 13 ms 16 ms 15 ms 66.109.9.161
9 529 ms 20 ms 30 ms ae1-br01-eqla1.as57976.net [137.221.68.33]
10 154 ms 79 ms 71 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
11 47 ms 225 ms 19 ms et-0-0-31-pe02-swlv10.as57976.net [137.221.83.69]
12 18 ms 19 ms 19 ms las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
13 21 ms 23 ms 22 ms 137.221.105.2

Trace complete.

 

WinMTR****************************************

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| SAGEMCOM - 3 | 758 | 739 | 0 | 1 | 14 | 1 |
| 142.254.183.117 - 3 | 758 | 739 | 9 | 24 | 238 | 14 |
| agg63.vnnzca2402h.socal.rr.com - 3 | 762 | 744 | 11 | 27 | 245 | 22 |
| 72.129.14.86 - 3 | 758 | 739 | 11 | 29 | 253 | 16 |
| agg29.tustcaft01r.socal.rr.com - 3 | 758 | 739 | 14 | 31 | 256 | 16 |
|bu-ether16.tustca4200w-bcr00.tbone.rr.com - 3 | 762 | 744 | 13 | 31 | 253 | 24 |
| 0.ae2.pr1.lax10.tbone.rr.com - 3 | 762 | 744 | 13 | 29 | 253 | 16 |
| 66.109.9.161 - 3 | 758 | 739 | 12 | 29 | 250 | 13 |
| ae1-br01-eqla1.as57976.net - 3 | 758 | 739 | 17 | 35 | 251 | 23 |
| et-0-0-2-br01-swlv10.as57976.net - 3 | 758 | 739 | 18 | 36 | 268 | 18 |
| et-0-0-31-pe02-swlv10.as57976.net - 3 | 758 | 739 | 18 | 33 | 250 | 19 |
| las-swlv10-ia-bons-04.as57976.net - 3 | 762 | 744 | 18 | 33 | 255 | 19 |
| 137.221.105.2 - 3 | 762 | 744 | 18 | 33 | 256 | 19 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

3 REPLIES 3
Lead Moderator

Re: Intermitency that not even the technician could fix. Pls help

Good morning.

 

I am sorry the tech was not able to resolve the issue. Looking at the trace I do see some latency after it leaves our network.  I was able to find your account through your registration

here and I am seeing signal issues on all of your downstream channels. I am unsure 

why the technician did not see this unless it is an intermittent signal issue.

 

I would like to suggest you contact our Social Media Customer Care team 

to schedule a technician to come back out and further investigate this.

 

I will leave notes on the account with what I am seeing so that if this is an issue

that is not always present they will know. Thank you! 

 

Twitter: @Ask_Spectrum

or
Facebook: https://www.facebook.com/Spectrum


Regards,
Julia R.
Spectrum-Social Media Customer Care
Lead Moderator-Community Forums

Not applicable

Re: Intermitency that not even the technician could fix. Pls help

I shall, thank you!

Proven Sharer

Re: Intermitency that not even the technician could fix. Pls help

I would recommend that you change the DNS server IP addresses in your network setup to use the Spectrum DNS servers found at  209.18.47.61 and 62.  The IP 8.8.8.8 you currently have loaded is Google, which is located outside the Spectrum transport network. 

All registered DNS sites receive the same file updates twice a day, so there's no major benefit for you to use something located beyond Specrum's boundary.  That forces your computer to go out to the web each time before it can resolve any domain name, thus incurring additional latency at each IXP handoff point.  As an example, your 500+ ms delay on hop #9, with IP address 137.221.68.33 is Blizzard Entertainment of Irvine, CA.  With that much extra delay I don't know why you would want to route anything through them.