Why is DegreeForum so SLOW lately?

[dfrecore]

I don't think it's just me, since it's happening on both my computer at home and at work, but the last week or two, it has been incredibly slow on this forum.  Lots of times, I can't get on at all.  Then, once I'm on, it may take a while to be able to open up a thread.  And finally, posting is awful.  I can get the circle of death going, where it just goes and goes and nothing happens for minutes...and I have to copy what I wrote on a clipboard and open it back up to try again.  

Usually if there's a problem, it's for a day or two, but this has been going on for a while now.

[ss20ts]

It's not just you. I gave up a few times this week trying to get on because the page just wouldn't load.

[rachel83az]

I thought it was just my VPN acting weird. It happens sometimes. Seems to have resolved itself now?

[bjcheung77]

Seems there's an issue with Comcast and LiquidWeb

Pinging degreeforum.net [67.225.168.56] with 32 bytes of data:
Reply from 67.225.168.56: bytes=32 time=80ms TTL=55
Reply from 67.225.168.56: bytes=32 time=81ms TTL=55
Reply from 67.225.168.56: bytes=32 time=80ms TTL=55
Reply from 67.225.168.56: bytes=32 time=80ms TTL=55

Ping statistics for 67.225.168.56:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 81ms, Average = 80ms

Tracing route to host3.degreeforum.net [67.225.168.56]
over a maximum of 30 hops:


4 6 ms 6 ms 6 ms be-205-pe12.seattle.wa.ibone.comcast.net [173.167.57.213]
5 6 ms 6 ms 7 ms be-2412-cs04.seattle.wa.ibone.comcast.net [96.110.34.141]
6 7 ms 7 ms 7 ms be-1411-cr11.seattle.wa.ibone.comcast.net [96.110.47.214]
7 32 ms 31 ms 31 ms be-301-cr11.champa.co.ibone.comcast.net [96.110.36.209]
8 32 ms 31 ms 32 ms be-1111-cs01.champa.co.ibone.comcast.net [96.110.37.193]
9 35 ms 32 ms 31 ms be-1114-cr14.champa.co.ibone.comcast.net [96.110.37.242]
10 32 ms 32 ms 32 ms be-304-cr14.1601milehigh.co.ibone.comcast.net [96.110.39.14]
11 32 ms 32 ms 32 ms be-1214-cs02.1601milehigh.co.ibone.comcast.net [96.110.39.117]
12 32 ms 31 ms 32 ms be-1211-cr11.1601milehigh.co.ibone.comcast.net [96.110.39.70]
13 * * 57 ms be-301-cr21.350ecermak.il.ibone.comcast.net [96.110.37.145]
14 55 ms 54 ms 56 ms be-1221-cs22.350ecermak.il.ibone.comcast.net [68.86.82.245]
15 55 ms 55 ms 54 ms be-2203-pe03.350ecermak.il.ibone.comcast.net [96.110.37.22]
16 83 ms 82 ms 82 ms as32244-pe03.350ecermak.il.ibone.comcast.net [50.242.150.130]
17 81 ms 81 ms 82 ms lw-dc2-core1-nexus-eth3-19.rtr.liquidweb.com [209.59.157.224]
18 80 ms 81 ms 81 ms lw-dc2-dist4.rtr.liquidweb.com [209.59.157.99]
19 81 ms 80 ms 80 ms host3.degreeforum.net [67.225.168.56]

Trace complete.

[jch]

Same here, also severely impacts the mobile app. Most of the time now the app will no longer refresh or takes an extremely long time to do so.
I don't think it's a Comcast issue, as the problem is happening regardless of which wired or wireless ISP I'm using.

[ss20ts]

I thought it was just my VPN acting weird. It happens sometimes. Seems to have resolved itself now?

It's still doing it today. It's not an internet service provider issue. It's definitely this website. I don't have Comcast. I have fiber from a local company.

[DolceDolce]

I thought it was just my VPN acting weird. It happens sometimes. Seems to have resolved itself now?

It's still doing it today. It's not an internet service provider issue. It's definitely this website. I don't have Comcast. I have fiber from a local company.

I've also experienced the slowness, and when sending a PM, had to remove an attachment to be able to send, before being timed out.  It has been slow trying to log on and connect as well.  Even sending this message, it timed out, but I had it copied with my mouse, just in case I needed to write the post response again.  lol

[allvia]

Still happening. I thought it was me, but as others pointed out this is the only site giving me grief over the last few days.

[ss20ts]

Funny how some of us thought it was us. I thought that too but then realized it's only this site so it must be something with the server this is hosted on.

[bjcheung77]

As I was saying, what I mentioned was that DegreeForum uses LiquidWeb for Hosting, LiquidWeb most likely uses ComCast for internet access. One or both of them are having issues, it's not your browser/computer, or your internet service provider either, but it still needs to connect to ComCast on the last few legs of the trip and end up with LiquidWeb to view the webpages/update changes to posts or threads, etc.

An example is, if you come across these type of issues with CloudFlare, you'll see 3 icons, a check beside you (your browser/internet), CloudFlare (the hosting firewall), and the final destination will show the X, meaning that site host/internet provider is having issues. I get CloudFlare issues often and it's not really their issue or my ISP or Laptop. It's the host/ISP for the website CloudFlare is redirecting you to...