Site really slow

[ozonetrooper]

Site has been really slow my way for the past week.

This is what I see on my side (not good) :

C:\Windows\System32>tracert 147.182.165.119

Tracing route to newdo.neverstill.com [147.182.165.119]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 15 ms 13 ms 10 ms 10.54.155.131
3 11 ms 13 ms 12 ms po-307-340-rur202.lamarque.tx.houston.comcast.net [96.216.183.205]
4 12 ms 13 ms 12 ms po-200-xar02.lamarque.tx.houston.comcast.net [96.217.21.241]
5 12 ms 15 ms 27 ms po-2-xar01.lamarque.tx.houston.comcast.net [68.85.246.21]
6 17 ms 16 ms 17 ms be-325-arsc1.bearcreek.tx.houston.comcast.net [96.217.21.141]
7 * * * Request timed out.
8 45 ms * * ae2.3610.edge5.Newark1.net.lumen.tech [4.69.209.74]
9 44 ms 70 ms 45 ms digital-oce.edge5.newark1.level3.net [4.28.0.46]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 46 ms 43 ms 44 ms newdo.neverstill.com [147.182.165.119]

 

[ozonetrooper]

It is so slow I will try again tomorrow, I have things that got to be done today ....

 

[Milo Willamson]

It is so slow I will try again tomorrow, I have things that got to be done today ....

Yes... We all have stuff that needs to do.. Sure.. We all have stuff..

 

[PitCarver]

 

[jhtalisman]

It seems like the hosting site switched the server to dial-up.

 

[Fox Mulder]

Yes reported it in the Chat with Staff thread a few days ago, they haven't fed the hamster yet.

 

[olbriar]

We all know a simple refresh would set things right. Rob should have a regular scheduled reset. He's a bit difficult to reach. I understand that his family might be expanding.

 

[Milo Willamson]

Just now it is massively fast for me.

 

[Fox Mulder]

It's fine if he has personal obligations occupying his attention, we all so at some point. But if it's enough to keep him from taking proper care of the site he should share or pass along that responsibility to someone who can handle it.

 

[ozonetrooper]

for those whom do not know what a tracert report tells this is the issue :

7 * * * Request timed out.
8 45 ms * * ae2.3610.edge5.Newark1.net.lumen.tech [4.69.209.74]
9 44 ms 70 ms 45 ms digital-oce.edge5.newark1.level3.net [4.28.0.46]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 46 ms 43 ms 44 ms newdo.neverstill.com [147.182.165.119]

digital-oce.edge5.newark1.level3.net is the last server to respond and it is very slow, the next 6 lines are time outs meaning the next server did not respond, for six requests. This makes for slow/no page loading issues. The host needs to fix this it is a routing issue with them.


digital-oce.edge5.newark1.level3.net identifies a network endpoint within the DigitalOcean and Level 3 networks in Newark, NJ, that is owned by Lumen Technologies.


Comcast uses Level 3 networks and they suck !

 

[ozonetrooper]

Really slow I will check in tomorrow.

 

[ozonetrooper]

Crippity Crap Batman, y'all are dead in the water !

Tracing route to newdo.neverstill.com [147.182.165.119]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 11 ms 12 ms 13 ms 10.54.155.131
3 15 ms 11 ms 13 ms po-307-340-rur202.lamarque.tx.houston.comcast.net [96.216.183.205]
4 22 ms 12 ms 13 ms po-200-xar02.lamarque.tx.houston.comcast.net [96.217.21.241]
5 10 ms 13 ms 12 ms po-2-xar01.lamarque.tx.houston.comcast.net [68.85.246.21]
6 16 ms 17 ms 14 ms be-325-arsc1.bearcreek.tx.houston.comcast.net [96.217.21.141]


7 * * * Request timed out.
8 54 ms 53 ms 46 ms ae2.3610.edge5.Newark1.net.lumen.tech [4.69.209.74]
9 44 ms 44 ms 44 ms digital-oce.edge5.newark1.level3.net [4.28.0.46]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 46 ms 47 ms 46 ms newdo.neverstill.com [147.182.165.119]

Trace complete.

 

[Fox Mulder]

It just keeps getting worse.

But somehow the spammers can still post.

 

[Steven58]

It's my fault. Early Bird is mad at me.

 

[olbriar]

It's my fault. Early Bird is mad at me.

You have opened my eyes to the true reason for the Early Bird name. 🤣

 

[ozonetrooper]

Wowza ! I could not even get the site to open yesterday and today is barely better.

last tracert reported 7 servers timing out with very long response times to the ones that did.

Only fix is to notify the hosting service it is not gonna heal itself !

 

[olbriar]

The Admin has reached out to Rob. We sit and wait....

 

[Fox Mulder]

It's only the forums, the (useless) main page comes right up.

 

[Steven58]

They are trying to shake the rest of us free to get rid of us!

 

[ozonetrooper]

It's only the forums, the (useless) main page comes right up.

It depends on at least two things, the route and the server. Some host use several servers to handle the traffic, lets call server A the main page and server B the forums.

Then server C for PM's, etc.

Now lets look at the routing. Main page comes up and then a choice is made to view and it is sent to the correct destination. When all is well this happens instantly in a seamless manner, when there are routing issues you get servers not responding and timing out and ... well you see what happens.

Just like your computer, the servers need updating and rebooting occasionally and then there are the outside influences, such as hand-offs, to subcontractors like Level 3, when the path with them is at issue only they can fix it, but must be made aware of the issue.

Usually a phone call is all it takes ...

FYI it is running much smoother this way this morning !

 

[ozonetrooper]

I just switched to att fiber two days ago and have not really had any connection issues, but it looks like I path issues too. I need to run them down and see if it is att servers or the hand off servers.

The last good connecton to this site is 38.32.170.89, aftet that they still have 8 servers lying down on the job :

Tracing route to newdo.neverstill.com [147.182.165.119]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.254]
2 1 ms <1 ms 1 ms 162-238-204-1.lightspeed.hstntx.sbcglobal.net [162.238.204.1]
3 3 ms 2 ms 2 ms 71.149.23.208
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 29 ms 11 ms 9 ms be2763.ccr31.dfw01.atlas.cogentco.com [154.54.28.73]
10 17 ms 17 ms 17 ms port-channel8121.ccr91.jan02.atlas.cogentco.com [154.54.40.250]
11 23 ms 23 ms 23 ms be3009.ccr41.atl01.atlas.cogentco.com [154.54.29.133]
12 24 ms 24 ms 23 ms be4189.rcr51.b006503-1.atl01.atlas.cogentco.com [154.54.30.242]


13 24 ms 24 ms 23 ms 38.32.170.89


14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 40 ms 40 ms 40 ms newdo.neverstill.com [147.182.165.119]

Trace complete.


Looks like the last responding server is in Atlanta :

 

[ozonetrooper]

strange issue related to AT&T and Cogent routing.

https://www.reddit.com/r/networking/comments/1guoxux/strange_speed_bump_between_att_and_cogent/

(for reference)

figures, next stop open the router and see what is going on, I got stuff to do this morning, I will follow up on this.