ASC - slow?

[BioRage]

Right, so we can trash this thread once I get an answer;

Is it just me or has been ASC been slow af the past few days?

[p0nch3]

Okay so I wasn't the only one. I've gotten more "you need to wait 5 seconds before searching for new threads" than usual these past few days

[NAAZ]

I get the same. at random times a page would take maybe 10 seconds to load while normally it's instant

[Red Dot]

Ya'll got shitty ISPs!

Jokes aside all good in the hood here, just Tapatalk issues on Android.

EDIT: this post took fucking forever to upload lol! I spoke too soon!

[Datawraith]

Yup, same here on both mobile (not tapatalk) and PC

[lurkingknight]

yes, for more than a few weeks now at random times, page would take forever to respond/load.

[Drakker]

Its very intermittent... but if you're in a hurry, it's guaranteed to be slow.

[pestobanana]

Okay for the most part, once in a while it would die for a few seconds to a minute. Started a few weeks ago for me.

[RainyEyes]

There's probably a node somewhere out there in the US or downtown TO that's giving people trouble:

Tracing route to airsoftcanada.com [168.235.83.126]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 6 ms 199.47.125.1
3 7 ms 6 ms 6 ms 10.15.32.1
4 9 ms 7 ms 6 ms xe-5-2-1-80.cr0-tor1.ip4.gtt.net [77.67.71.105]
5 19 ms 19 ms 20 ms xe-3-0-0.cr8-nyc3.ip4.gtt.net [89.149.183.46]
6 * * * Request timed out.
7 * * * Request timed out.
8 22 ms 18 ms 20 ms 168.235.83.126

Trace complete.



I've been having this problem lately too with not just ASC but google as well. There's a rogers node somewhere that's being overloaded, but I don't know the proper channels nor the right people to contact to ameliorate the problem.

Tracing route to google.ca [172.217.2.131]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 6 ms 199.47.125.1
3 6 ms 6 ms 6 ms 10.15.32.1
4 7 ms 6 ms 6 ms google.ip4.torontointernetxchange.net [206.108.34.6]
5 39 ms 59 ms 6 ms 209.85.242.13
6 12 ms 6 ms 6 ms 209.85.250.7
7 6 ms 6 ms 6 ms yyz08s14-in-f3.1e100.net [172.217.2.131]

Trace complete.


It's 12:37 am right now so it's off peak and the problem's not present at the moment... but sometimes hops 5-6 have problems.

If anyone else is tech savvy and knows something else that might be happening... please let me know.

[devbro]

trace just shows the path, it does not explain the slow response from the server.

[RainyEyes]

Originally Posted by devbro

trace just shows the path, it does not explain the slow response from the server.

Not sure what you mean... if there are nodes that are overloaded/responding slowly it delays the response from the server.

This usually happens during peak hours when lots of people are "in the same area all watching netflix at the same time" according to a Rogers representative when once asked why they were getting 500 ping between the hours of 6pm to 10 pm.

The server seems to be responding fine but the path leading up to the server is jittery.

Correct me if I'm wrong, I didn't go to an IT school or anything.

[OPENchestWOUND]

having issues uploading jpgs, (JPEG - 91 KB, 600/337 pixels)?
might be related?

[Drakker]

Originally Posted by RainyEyes

Not sure what you mean... if there are nodes that are overloaded/responding slowly it delays the response from the server.

This usually happens during peak hours when lots of people are "in the same area all watching netflix at the same time" according to a Rogers representative when once asked why they were getting 500 ping between the hours of 6pm to 10 pm.

The server seems to be responding fine but the path leading up to the server is jittery.

Correct me if I'm wrong, I didn't go to an IT school or anything.

Its possible, but to prove it you'd have to log your traceroute for a while and correlate the results with actual slow downs from the site. Server problems are a lot more likely. The only thing we can time as users are searches, when doing a search the processing time is displayed in the upper right part of the search results box. That is probably a good indicator of problems, is that number goes up a lot and gets in the multi-seconds, then we know for sure that there's a problem with the server, if its always low, well, it tells us that the DB search part of the site is working well.

[BloodSport]

I've notified our IT master/site owner to look into it.
We changed server providers a few weeks ago so might be related.

[BloodSport]

I've notified our IT master/site owner to look into it.
We changed server providers a few weeks ago so might be related.