The Breast Enhancement Archive

Anyone else experiencing this?? I cleared out all temp files and cache and [b]still [/b][i][u][/u][/i]getting long load times.

But, it's STILL worth the wait for dem enormous big torps!!!

I never noticed that unless I am on my phone or my laptop is not getting a strong Wi-Fi connection.

AD

BosomBlaster, if you are in FL, like I think you are, then you should be getting a fairly quick response time.

(05-15-2013, 03:01 PM)JustSomeone Wrote: [ -> ]BosomBlaster, if you are in FL, like I think you are, then you should be getting a fairly quick response time.

I am in FL (how did you know that?) and yet the response times remain crazy slow...much worse than they used to be only a week or so ago.

Admin's have access to your IP Address...LOL!

(05-16-2013, 09:29 AM)bosomblaster Wrote: [ -> ]

(05-15-2013, 03:01 PM)JustSomeone Wrote: [ -> ]BosomBlaster, if you are in FL, like I think you are, then you should be getting a fairly quick response time.

I am in FL (how did you know that?) and yet the response times remain crazy slow...much worse than they used to be only a week or so ago.

Our servers get a 15.5MB throughput. I can only think that the problem might be on your end? Try your luck at www.speedtest.com
[hr]
I should also mention that there is less that 200 miles between my servers and your home... Yet a traceroute sends your 30+ hops/requests in this order:

1. Small Town, Florida (from your home, multiple points)
2. Atlanta, GA.
3. San Fransisco, CA
4. Tampa, Fl. (to my datacenter)

My point is that you visit this forum, the data packets are sent all over US, before they hit my servers. The trip for your data packets should be shorter. You may want to have a conversation with your ISP. Ask them why their routing is all wonky.

Here is the traceroute information for the geeks:

traceroute to 74.233.xxx.xxx (74.233.xxx.xxx), 30 hops max, 60 byte packets
1 173.65.39.1 3.271 ms 3.236 ms 3.188 ms
2 130.81.109.236 5.629 ms 5.628 ms 5.599 ms
3 130.81.28.212 10.577 ms 10.548 ms 10.519 ms
4 152.63.87.162 10.431 ms 10.426 ms 10.394 ms
5 204.255.168.18 10.378 ms 10.350 ms 20.191 ms
6 * * *
7 12.122.1.45 21.526 ms 21.834 ms 21.785 ms
8 12.122.141.238 21.730 ms 18.863 ms 18.821 ms
9 12.81.20.57 21.252 ms 21.274 ms 21.258 ms
10 12.81.20.61 18.663 ms 18.674 ms 18.635 ms
11 70.159.201.66 19.687 ms 19.871 ms 19.813 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

All well and good, but why would it be fine one day and the next day, all of a sudden, it's not??

Well, that would require me to hazard a guess on the infrastructure between my data center to your computer... Keep in my that I don't control that infrastructure. But perhaps a router went down, and had to reroute your packets.

How long has this been going on?

It's also dependent on a few variables.
Server demands, network demands, network downtimes in some aspects where things have to be re-routed

Volume and demand has a lot to do with any server lag.

You have a point, Bone. But this is a very simple setup, our set of servers. In BosomBlaster's case, it's the infrastructure in between.