testtest

Server Maintenance

Annihilator

SAINT
Founding Member
I thought you said it was the Mayans πŸ‘ΉπŸ€”
1585703841057.jpeg
 

Annihilator

SAINT
Founding Member
Thanks for looking into this Louis. It's still up and running so that's a plus. Not much can be done (at least under the current circumstance), if the traffic has increased so significantly.
BET7 is so smart...I hope when I grow up I’ll be just like him........πŸ˜‚πŸ˜‚πŸ˜‚πŸ˜‚

Just messin with ya BET7....

Your my idol......😜😜😜😜
 

OkiePewPew

Moderator
Staff member
I've been talking with the hosting company and they have confirmed that there is slowness on the network but it is due to the amount of traffic on the internet in general. They are seeing this with all different servers in their data center. Here is a portion of their statement:

"As more people throughout the country and world are transitioning to a work from home or stay at home model, additional traffic and stress are placed upon the infrastructure that makes up the internet due to business and personal use. Depending on the location of the user and service, this additional traffic can result in connection latency resulting in slow or laggy response times."

I know there has been a fair bit of concern over the last few weeks in the IT world in general about all this stress on the internet framework, but I think we are getting to a point where it is actually causing issues.

Some of you mentioned that other sites are working fine, but it's all about the different routing that exists on the internet. Some websites go down certain "roads," if you will, and some go down others...and some "roads" some have more traffic than others, it's just sort of hit or miss and unfortunately our "road" for this server is being hit with a lot of traffic and congestion and it's not something that the hosting company can simply reroute. Hopefully it will improve but I am waiting to hear back more from them.
Thanks for sharing!
 

SMSgtRod

Professional
Founding Member
Louis, it sounds to me like you got a standard canned answer.

What is their problem anyways? Seems like everybody else has figured out
how to straighten out the internet road except them.

Of course there is a lot of traffic on the internet. If the abundance of traffic were
the problem then I'd see it on social media and Amazon along with Wally World
and YouTube to name a few. So would all the other TAL members.
Yet they zip right along and TAL struggles with difficult logins, pages that take
minutes to load and generally overall slugged down operation.

I'd say that the root cause is poor hosting. IMHO
My 2Β’
 

Louis G.

Administrator
Staff member
The hosting company says that they have moved traffic for some network routes to less busy routes and they believe the issue to be mostly resolved. Please let me know if you guys are still experiencing slowness. Thank you!

Louis
 

djthumper

Custom
Founding Member
I started to notice a bit of lag.

Once I get out of my corporate network I notice a significant drop in speed at GTT.net

6 2 ms 2 ms 2 ms iroutera.lvvwd.com [198.136.223.2]
7 2 ms 2 ms 2 ms g1-23.las-agg7s1-1.switchnap.com [66.209.71.21]
8 3 ms 3 ms 2 ms be731.las-n10s1-core1.switch.com [66.209.72.13]
9 6 ms 6 ms 6 ms be11011.las-brd8-1.switch.com [66.209.64.110]
10 8 ms 8 ms 8 ms h188.151.132.40.static.ip.windstream.net [40.132.151.188]
11 21 ms 9 ms 10 ms ae1.agr04.phnd01-az.us.windstream.net [169.130.169.32]
12 18 ms 18 ms 18 ms ae0-0.pe01.lsaj01-ca.us.windstream.net [169.130.114.158]
13 18 ms 18 ms 18 ms ae1-0.cr02.lsaj01-ca.us.windstream.net [169.130.164.168]
14 19 ms 19 ms 19 ms ae23.cr4-lax2.ip4.gtt.net [69.174.17.201]
15 29 ms 25 ms 25 ms ae19.cr0-sjc1.ip4.gtt.net [89.149.136.213]
16 25 ms 25 ms 25 ms xe-11-2-7.cr0-sjc1.ip4.gtt.net [98.124.184.158]
17 25 ms 25 ms 25 ms cloudproxy10155.sucuri.net [192.124.249.155]
 

Louis G.

Administrator
Staff member
I started to notice a bit of lag.

Once I get out of my corporate network I notice a significant drop in speed at GTT.net

6 2 ms 2 ms 2 ms iroutera.lvvwd.com [198.136.223.2]
7 2 ms 2 ms 2 ms g1-23.las-agg7s1-1.switchnap.com [66.209.71.21]
8 3 ms 3 ms 2 ms be731.las-n10s1-core1.switch.com [66.209.72.13]
9 6 ms 6 ms 6 ms be11011.las-brd8-1.switch.com [66.209.64.110]
10 8 ms 8 ms 8 ms h188.151.132.40.static.ip.windstream.net [40.132.151.188]
11 21 ms 9 ms 10 ms ae1.agr04.phnd01-az.us.windstream.net [169.130.169.32]
12 18 ms 18 ms 18 ms ae0-0.pe01.lsaj01-ca.us.windstream.net [169.130.114.158]
13 18 ms 18 ms 18 ms ae1-0.cr02.lsaj01-ca.us.windstream.net [169.130.164.168]
14 19 ms 19 ms 19 ms ae23.cr4-lax2.ip4.gtt.net [69.174.17.201]
15 29 ms 25 ms 25 ms ae19.cr0-sjc1.ip4.gtt.net [89.149.136.213]
16 25 ms 25 ms 25 ms xe-11-2-7.cr0-sjc1.ip4.gtt.net [98.124.184.158]
17 25 ms 25 ms 25 ms cloudproxy10155.sucuri.net [192.124.249.155]

Hmm, thanks for post the traceroute. Any better today?
 

djthumper

Custom
Founding Member
No, it appears to get bogged down at GTT.net up in San Jose. Looks like they are taking the long way through the western states. I would be interested to see others tracerts to see where others are getting bogged down at.

6 2 ms 2 ms 2 ms iroutera.lvvwd.com [198.136.223.2]
7 3 ms 3 ms 2 ms g1-23.las-agg7s1-1.switchnap.com [66.209.71.21]
8 2 ms 2 ms 3 ms be731.las-n10s1-core1.switch.com [66.209.72.13]
9 4 ms 2 ms 2 ms be11011.las-brd8-1.switch.com [66.209.64.110]
10 8 ms 8 ms 8 ms h188.151.132.40.static.ip.windstream.net [40.132.151.188]
11 8 ms 8 ms 14 ms ae1.agr04.phnd01-az.us.windstream.net [169.130.169.32]
12 18 ms 18 ms 18 ms ae0-0.pe01.lsaj01-ca.us.windstream.net [169.130.114.158]
13 18 ms 18 ms 18 ms ae1-0.cr02.lsaj01-ca.us.windstream.net [169.130.164.168]
14 18 ms 18 ms 18 ms ae23.cr4-lax2.ip4.gtt.net [69.174.17.201]
15 26 ms 26 ms 26 ms ae19.cr0-sjc1.ip4.gtt.net [89.149.136.213]
16 25 ms 25 ms 25 ms xe-11-2-7.cr0-sjc1.ip4.gtt.net [98.124.184.158]
17 25 ms 25 ms 25 ms cloudproxy10155.sucuri.net [192.124.249.155]
 

OkiePewPew

Moderator
Staff member
No, it appears to get bogged down at GTT.net up in San Jose. Looks like they are taking the long way through the western states. I would be interested to see others tracerts to see where others are getting bogged down at.

6 2 ms 2 ms 2 ms iroutera.lvvwd.com [198.136.223.2]
7 3 ms 3 ms 2 ms g1-23.las-agg7s1-1.switchnap.com [66.209.71.21]
8 2 ms 2 ms 3 ms be731.las-n10s1-core1.switch.com [66.209.72.13]
9 4 ms 2 ms 2 ms be11011.las-brd8-1.switch.com [66.209.64.110]
10 8 ms 8 ms 8 ms h188.151.132.40.static.ip.windstream.net [40.132.151.188]
11 8 ms 8 ms 14 ms ae1.agr04.phnd01-az.us.windstream.net [169.130.169.32]
12 18 ms 18 ms 18 ms ae0-0.pe01.lsaj01-ca.us.windstream.net [169.130.114.158]
13 18 ms 18 ms 18 ms ae1-0.cr02.lsaj01-ca.us.windstream.net [169.130.164.168]
14 18 ms 18 ms 18 ms ae23.cr4-lax2.ip4.gtt.net [69.174.17.201]
15 26 ms 26 ms 26 ms ae19.cr0-sjc1.ip4.gtt.net [89.149.136.213]
16 25 ms 25 ms 25 ms xe-11-2-7.cr0-sjc1.ip4.gtt.net [98.124.184.158]
17 25 ms 25 ms 25 ms cloudproxy10155.sucuri.net [192.124.249.155]
Mines still running good but just for kicks
β€”
--- Nice Trace to https://www.thearmorylife.com/ ---

1) dsldevice.attlocal.net (192.168.1.254) 13.063 ms, 10/10 ps, 0.0% loss
2) 99-95-52-1.lightspeed.dybhfl.sbcglobal.net (99.95.52.1) 29.635 ms, 10/10 ps, 0.0% loss [AS 7018] United States
3) 99.168.24.232 (99.168.24.232) 29.574 ms, 10/10 ps, 0.0% loss [AS 7018] United States
4) cr2.ormfl.ip.att.net (12.122.106.66) 35.183 ms, 10/10 ps, 0.0% loss [AS 7018] European Union
5) 12.122.28.125 (12.122.28.125) 35.678 ms, 10/10 ps, 0.0% loss [AS 7018] European Union
6) attga402igs.ip.att.net (12.122.117.121) 33.918 ms, 10/10 ps, 0.0% loss [AS 7018] European Union
7) 192.205.36.158 (192.205.36.158) 32.039 ms, 10/10 ps, 0.0% loss [AS 7018] United States
8) ae-16.r22.atlnga05.us.bb.gin.ntt.net (129.250.5.57) 33.773 ms, 10/10 ps, 0.0% loss [AS 2914] United States
9) ae-4.r25.dllstx09.us.bb.gin.ntt.net (129.250.4.116) 51.490 ms, 9/9 ps, 0.0% loss [AS 2914] United States
10) ae-8.r23.snjsca04.us.bb.gin.ntt.net (129.250.4.154) 88.397 ms, 9/9 ps, 0.0% loss [AS 2914] United States
11) ae-45.r01.snjsca04.us.bb.gin.ntt.net (129.250.3.175) 88.358 ms, 9/9 ps, 0.0% loss [AS 2914] United States
12) ae-0.a02.snjsca04.us.bb.gin.ntt.net (129.250.2.3) 90.654 ms, 9/9 ps, 0.0% loss [AS 2914] United States
13) ae-7.akamai.snjsca04.us.bb.gin.ntt.net (130.94.195.14) 277.069 ms, 9/9 ps, 0.0% loss [AS 2914] United States
14) a23-217-138-110.deploy.static.akamaitechnologies.com (23.217.138.110) 108.147 ms, 9/9 ps, 0.0% loss [AS 20940] United States
 
Top