Latency Issues

[Susan]

Some of you may have noticed an intermittent slowness over the last 10 days; during monitoring today, the ISP found a 2% packet loss to the fiber box on the outside of my house. They will be repairing it tomorrow. It is their belief that should fix the problem. There will be some potential downtime as they do the work, but it hopefully shouldn't last too long.

Secondly I have asked that they consider bumping up the the speed for pre-existing customers whose base speed is below their current minimum tier. The Technician is going to make that request officially on Monday. I feel the odds are good they will do so which will bump the bandwidth by a good bit. While we are not anywhere near maxing out now this will allow large file requests to be delivered faster.

[Michelle_P]

Susan, you have my deep admiration as a retired computer geek.  Running a server for a site as busy as this out of your home may very well be tougher than going through transition.

Thank you so much for all you do.

Everybody:  Please click the "Make a Donation" button.  Come on!  She's worth it.

[Dena]

A sunday repair call, you must have some pull with the ISP. I had my home line bumped up in speed and the first guy totally bungled the job. In the process he not only sent my error rate sky high but he change my phone number. By the time the second guy made the repair, almost 2 weeks passed living with with a marginal internet and my original phone number forwarded to my cell phone.

[Susan]

Susan, you have my deep admiration as a retired computer geek.  Running a server for a site as busy as this out of your home may very well be tougher than going through transition.

Thank you so much for all you do.

Everybody:  Please click the "Make a Donation" button.  Come on!  She's worth it.

24x7 access is worth its weight in gold. The last place I had the server it was $350 per hour 2 hour minimum to get access to the server after hours, on holidays, or weekends. We couldn't afford that happening once with the finances as tight as we run them.

As for the sunday service call that's why we pay the extra cost for enterprise level internet service.

Sent from my KFSAWI using Tapatalk

[Susan]

ISP is here expect some downtime shortly.

[sarah1972]

Thanks for all your hard work and creativity to keep the site running and the cost low. Hope the ISP can fix the latency issue...

[Susan]

The repair to the fiber optic interface didn't fix the problem I have requested they replace the hardware on the outside of the house, this will be done either tonight or tomorrow. Again there will be some down time when this is done. I will try keep you all up to date.

I am also looking at replacing all networking cables with new ones to ensure it's not a cabling problem, but can't do it till tomorrow.

[Susan]

They are here downtime incoming!

[Susan]

Replacing the hardware on the outside of the house didn't help, I am going to try replacing my network cables but i doubt that will help but will eliminate inside wiring.

[sarah1972]

Do you need another monitoring point? I can run some ping tests if it would be of any help (but it seems you have all this covered)

[Susan]

CDE's here for the third time in 3 days... Don't expect downtime today, but you never know...

BTW forgot to update new cables, another hub didn't resolve the problem.

[Susan]

 It took a few days but they finally fixed the issue I was having. Took 45 emails and 3 service calls. Oh and 56$ in new cables (Wasn't even the problem but was eliminating that as a possibility)...

On a plus note our ping time to the net has been reduced by about 6x.

[Dena]

My ping time of the site has remained pretty consistent at about 84 ms however I am taking the long way around.
Traceroute has started...

traceroute to susans.org (104.36.203.218), 64 hops max, 72 byte packets
1  192.168.0.1 (192.168.0.1)  0.789 ms  0.476 ms  0.332 ms
2  phnx-dsl-gw68.phnx.qwest.net (67.40.227.68)  21.710 ms  18.781 ms  18.766 ms
3  phnx-agw1.inet.qwest.net (75.160.238.25)  18.515 ms  24.053 ms  18.894 ms
4  los-brdr-01.inet.qwest.net (67.14.102.110)  28.807 ms  28.616 ms  28.721 ms
5  63.146.26.146 (63.146.26.146)  28.804 ms  30.261 ms  29.039 ms
6  if-ae-34-2.tcore2.dt8-dallas.as6453.net (66.110.57.20)  78.669 ms  77.089 ms  81.024 ms
7  if-ae-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5)  75.658 ms  82.092 ms  75.767 ms
8  if-ae-27-2.tcore1.a56-atlanta.as6453.net (64.86.113.5)  75.255 ms  83.377 ms  75.464 ms
9  64.86.113.50 (64.86.113.50)  84.008 ms  83.560 ms  94.981 ms
10  208.88.168.93 (208.88.168.93)  84.851 ms  89.010 ms  83.971 ms
11  208.95.183.232 (208.95.183.232)  84.765 ms  90.878 ms  83.687 ms
12  ns1.clarksvillemediaservices.com (104.36.203.218)  83.981 ms  84.592 ms  84.360 ms

[Susan]

Ping to google during the problem 20ms, ping to google after the problem 3.97ms.