Club 600

Vnsmkr

Well-Known Member
Perhaps if RIU could keep their fucking servers from crashing every few seconds I could look at ALL the pages. FUCKING POS.

Clear my cache every day but yet it still won't load without crashing. I'll be fucked if we pay for advertising somewhere that wont even fucking load @DonTesla
 

DST

Well-Known Member
Perhaps if RIU could keep their fucking servers from crashing every few seconds I could look at ALL the pages. FUCKING POS.

Clear my cache every day but yet it still won't load without crashing. I'll be fucked if we pay for advertising somewhere that wont even fucking load @DonTesla
Not had any problems myself lately. You sure it's not the network you are connected to?
As for paying for advertising, ours didn't work out very great to be honest, but you got to try I guess.
 

Bbcchance

Well-Known Member
Not had any problems myself lately. You sure it's not the network you are connected to?
As for paying for advertising, ours didn't work out very great to be honest, but you got to try I guess.
You guys on IG? There are 140 images under #breedersboutique mostly just pics from folks who've grown or purchased your gear, but the name doesn't seem taken or used
 

Vnsmkr

Well-Known Member
Not had any problems myself lately. You sure it's not the network you are connected to?
As for paying for advertising, ours didn't work out very great to be honest, but you got to try I guess.
Thats all I needed to here @DST , my mind was made up anyway.

And as far as the network goes, no its not the network here and if the guy who runs the advertising (me) cant even view pages, sort of defeats the purpose
 

DST

Well-Known Member
Thats all I needed to here @DST , my mind was made up anyway.

And as far as the network goes, no its not the network here and if the guy who runs the advertising (me) cant even view pages, sort of defeats the purpose
I don't think the amount of new registrations we got in the time of advertising anywhere near reflected what we paid. Which wasn't a massive amount to to be fair and our banner was always flashing up. People tend to listen to what folks say in threads. For advertising to.work you got to spend a LOT imo.
 

bassman999

Well-Known Member
Thats all I needed to here @DST , my mind was made up anyway.

And as far as the network goes, no its not the network here and if the guy who runs the advertising (me) cant even view pages, sort of defeats the purpose
Loading slow like dial-up off and on today for me.
I have a 100mb connection speed test just now wifi 44mb/s and Ethernet 76mb/s so I doubt its my end
 

Vnsmkr

Well-Known Member
Loading slow like dial-up off and on today for me.
I have a 100mb connection speed test just now wifi 44mb/s and Ethernet 76mb/s so I doubt its my end
Its like that everyday for the last 2-3 months for me. Used to be I could clear my cache and the pages would load, but now if they have pictures on the page odds are it crashes before loading. Every other page loads up fast as fuck, so it aint me
 

bassman999

Well-Known Member
Not sure if i did it right, but came back with this response

Looks like a web URL, I will try and extract the target.
Executing 'traceroute -m 30 -q 3 -f 3 104.20.60.184'
traceroute to 104.20.60.184 (104.20.60.184), 30 hops max, 40 byte packets
3 fwc01-its-r1.mgmt.usc.edu (192.168.150.22) 0.716 ms 0.542 ms 0.630 ms
4 rtr30-rtr33-fw26-fw27-gw-33.mgmt.usc.edu (10.1.133.1) 1.258 ms 1.190 ms 1.067 ms
5 v249-gw-6 (68.181.194.65) 307.551 ms 1.491 ms 1.064 ms
6 fw6-rtr6 (128.125.255.147) 1.483 ms 0.956 ms 22.455 ms
7 rtr-border-cal-fw6 (128.125.251.226) 1.483 ms 1.166 ms 1.285 ms
8 ln-usc1-pwaveusc2042.ln.net (130.152.182.81) 3.438 ms 1.606 ms 3.024 ms
9 v338.core1.lax2.he.net (216.218.223.25) 9.995 ms 11.046 ms 9.328 ms
10 100ge2-2.core1.lax1.he.net (72.52.92.121) 2.352 ms 11.771 ms 1.922 ms
11 xe-0-1-0.edge01.lax01.as13335.net (206.223.123.156) 58.906 ms 51.001 ms laiix.as13335.net (198.32.146.195) 3.152 ms
12 104.20.60.184 (104.20.60.184) 4.899 ms 2.129 ms 1.877 ms
 

Vnsmkr

Well-Known Member
Not sure if i did it right, but came back with this response

Looks like a web URL, I will try and extract the target.
Executing 'traceroute -m 30 -q 3 -f 3 104.20.60.184'
traceroute to 104.20.60.184 (104.20.60.184), 30 hops max, 40 byte packets
3 fwc01-its-r1.mgmt.usc.edu (192.168.150.22) 0.716 ms 0.542 ms 0.630 ms
4 rtr30-rtr33-fw26-fw27-gw-33.mgmt.usc.edu (10.1.133.1) 1.258 ms 1.190 ms 1.067 ms
5 v249-gw-6 (68.181.194.65) 307.551 ms 1.491 ms 1.064 ms
6 fw6-rtr6 (128.125.255.147) 1.483 ms 0.956 ms 22.455 ms
7 rtr-border-cal-fw6 (128.125.251.226) 1.483 ms 1.166 ms 1.285 ms
8 ln-usc1-pwaveusc2042.ln.net (130.152.182.81) 3.438 ms 1.606 ms 3.024 ms
9 v338.core1.lax2.he.net (216.218.223.25) 9.995 ms 11.046 ms 9.328 ms
10 100ge2-2.core1.lax1.he.net (72.52.92.121) 2.352 ms 11.771 ms 1.922 ms
11 xe-0-1-0.edge01.lax01.as13335.net (206.223.123.156) 58.906 ms 51.001 ms laiix.as13335.net (198.32.146.195) 3.152 ms
12 104.20.60.184 (104.20.60.184) 4.899 ms 2.129 ms 1.877 ms
How you do that? And when you do find out the speed thieves how do you knock them out? Or can you
 
Top