Why is DegreeForum so SLOW lately?

[ss20ts]

This website is crawwwwwwwwwling today. I have to keep refreshing the page because the page just doesn't load.

[rachel83az]

This website is crawwwwwwwwwling today. I have to keep refreshing the page because the page just doesn't load.

Same, now. It was better earlier, now it's really bad. It's fine from about 8am UTC until about 3 or 4pm UTC and then it gets awful. It may or may not be better before 8am, but that's about when I start checking DF.

[LevelUP]

Just now, I did another test, and it was slow compared to another forum MyBB.

Loading times exceeded 10 seconds for some, and one time got a "This site can’t be reached" error.

Compared to MyBB, which consistently loaded each forum in about 1/4 of a second.

Here's a video of my experience browsing DF and MyBB
https://streamable.com/x343eb

DF seems to run smoothly at night and early morning. Forums were loading like 1/2 second each at most.

[sgloer]

I think we might be good now! Site seems to be running fast for me after the latest tweaks. Let me know if you still experience any slowness!

[rachel83az]

It seems to be running okay right now. We'll see how it goes in the next 24-48 hours.

[davewill]

Yeah, it hasn't been this peppy in a long time.

Knock on wood!!!!

[bjcheung77]

Yes, feels much better today, started off the same but when noon or so came along, it seemed speedier...

[ashkir]

Thank you! loading better now!

[studyingfortests]

Server issues is one thing for the web host LiquidWeb, but it's more the ISP (Comcast) who the webhost uses may also have issues...

It is not a Comcast issue. Any competent webhost (and LiquidWeb is definitely competent) has at least 4 or 5 providers for transit. They have sophisticated border routers in the data center that are constantly checking the best routing to a given IP address, updated multiple times per minute.

If an issue arises with a given transit provider, the border router seamlessly routes around the problem.

Now... if, in your example, Comcast was having an issue, it would be tricky. Most hosts peer with Comcast simply because Comcast serves so much end user transit. But it would be unlikely the entire Comcast network were having issues, so in that case, the routing software would simply identify a Comcast node where they could enter and deliver the content, routing around wherever the Comcast issue is.

Additinoally, traceroute was making it to LiquidWeb with no problem, with no meaningful latency.  All the latency was coming from the last hop, inside LiquidWeb. Again, this makes it pretty much impossible for it to be a Comcast issue.

This is almost certainly an issue within LiquidWeb.  It's possible they're getting clobbered with DOS attacks, which is making it difficult for anybody in their data center to get transit through, or it could be a server or database server issue. In my experience, it is most commonly one of those things.

I will say that, for now, things seem to be working normally.

[bjcheung77]

Thanks, that's what I think as well, here's my post #31 if you missed it: https://www.degreeforum.net/mybb/Thread-...#pid399401

---

And even though it may not be Comcast that LiquidWeb is using for the internet service provider, Comcast/Xfinity is/was having issues over the last week... It's a double edged sword for LiquidWeb and whatever their ISP is, could most likely be the server or their connections they use... Link: https://downdetector.com/status/xfinity/