Slow Connections

[quilix]

Hi,

My site is very slow. I wait for a whole minute befour the home page has opened. The site of Jaguarpc.com is slow too. This is since the last few days. Why? Is it because of the IP change? And when is it fast again?

[jason]

I haven't noticed any major slowdowns lately, so I don't think the problem is on JPC's end. It is probably an issue with your ISP or some point between your ISP and JPC. Try running a traceroute. There is liekly a program on your computer called either traceroute or tracert on your computer. At a command prompt, type either

tracert yoursite.com (if you are using Windows)

or

traceroute yoursite.com (if you are using Unix or Mac OS X)

and you will be able to see all of the hops that your data takes to reach JPC as well as where the slowdowns are occuring.

Good luck.

--Jason

[Vin DSL]

Originally posted by quilix
Hi,

My site is very slow. I wait for a whole minute befour the home page has opened. The site of Jaguarpc.com is slow too. This is since the last few days. Why? Is it because of the IP change? And when is it fast again?

Assuming you're talking about the site linked to your 'WWW' button, it pops right up for me - dittos for Jaguarpc.com. I have a feeling the problem is on YOUR end...

[klisis]

My site is slow as well, including this forum.
Here is my traceroute.

3 130.152.180.21 2.701 ms isi-1-lngw2-atm.ln.net [AS226] Los Nettos origin AS
4 198.172.117.161 8.811 ms ge-9-3.a01.lsanca02.us.ra.verio.net [AS2914] Verio
5 129.250.29.136 9.901 ms xe-1-0-0-4.r21.lsanca01.us.bb.verio.net [AS2914] Verio
6 129.250.9.34 9.472 ms p16-0.level3.lsanca01.us.bb.verio.net [AS2914] Verio
7 209.247.10.193 9.382 ms so-4-0-0.bbr1.LosAngeles1.level3.net [AS3356] Level 3 Communications North America
8 209.247.11.166 42.986 ms so-0-1-0.mp2.Houston1.Level3.net [AS3356] Level 3 Communications North America
9 209.247.11.190 39.753 ms gige9-1.hsipaccess1.Houston1.Level3.net [AS3356] Level 3 Communications North America
10 209.247.121.218 40.094 ms unknown.Level3.net (Fake rDNS) [AS3356] Level 3 Communications North America
11 66.7.143.182 40.284 ms o0-2jp2.hou002bd02.yipes.com [AS6517] Yipes Communications Inc.
12 66.7.143.158 40.841 ms o0-2bd2.hou003bd02.yipes.com [AS6517] Yipes Communications Inc.
13 66.7.143.54 44.088 ms o5-3bd2.hou005ap01.yipes.com [AS6517] Yipes Communications Inc.
14 66.54.158.66 123.923 ms DNS error [AS6517] Yipes Communications Inc.
15 66.227.56.15 43.562 ms DNS error [AS6517] Yipes Communications Inc.

The only issue I can see is on the second from bottom, 123.923 ms at Yipes inc.

[Stargazer]

Yipes seems to be where it breaks down for me too.

[dkadave]

Same here. Yipes end bad.

But now, it's fine! YAY

[quilix]

I have problems with Yipes too.
A few minutes ago I waited exactly 47 sec. befoure the site loaded.

[klisis]

I am still having the issue. Oh it's not me, it's the Yipes.
Maybe, it's time to take this a bit more seriously.

[JPC-Greg]

can I have a few other sample traces from anyone being affected by this . Thanks

[JPC-Greg]

thread moved to support

[JPC-Greg]

The ip table on the device (2nd to last found in your hops) was full. This caused that device to use more of its cpu The icmp traffic has been temp filtered out which will render pings and traces unusable, however the network itself should now be back to normal. As soon as we determine the cause of the ip table filling we will be able to correct this and restore icmp traffic capability.

[quilix]

Nope, I still have the problem. Somethimes it's fast, but most of the time I'm waiting at least 30 secs befoure the site loads. A few times the site never opened.

I did a traceroute:

[quilix]

Even with the picture above (trace.jpg) it is very slow. It's linked to my site. I waited a minute on the .jpg to load befoure I posted this message.

[salewit]

Excrutiatingly slow here too for the past 2-3 days. I thought it was on my end, but its clearly not. My tracert:

1 14 ms 27 ms 14 ms adsl-66-127-79-254.dsl.sntc01.pacbell.net [66.127.79.254]

2 14 ms 14 ms 27 ms dist1-vlan60.sntc01.pbi.net [63.203.51.65]

3 14 ms 14 ms 14 ms bb1-g1-0.sntc01.pbi.net [63.203.35.17]

4 14 ms 27 ms 14 ms bb2-p14-0.sntc01.pbi.net [64.161.1.30]

5 14 ms 28 ms 13 ms 64.161.1.46

6 27 ms 14 ms 14 ms 151.164.248.26

7 68 ms 69 ms 69 ms sntcca1wcx1-pos5-0.wcg.net [64.200.240.129]

8 82 ms 69 ms 96 ms anhmca1wcx3-pos4-0-oc48.wcg.net [64.200.240.1]

9 69 ms 68 ms 69 ms anhmca1wcx2-oc48.wcg.net [64.200.143.77]

10 69 ms 69 ms 68 ms dllstx1wcx3-oc48.wcg.net [64.200.240.5]

11 68 ms 69 ms 68 ms dllstx1wcx2-pos9-0.wcg.net [64.200.110.129]

12 68 ms 69 ms 69 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]

13 68 ms 83 ms 68 ms hstntx1wce2-yipes-gige.wcg.net [65.77.93.90]

14 69 ms 68 ms 69 ms 66.7.143.133

15 68 ms 69 ms 68 ms o0-1bd2.hou003bd01.yipes.com [66.7.180.158]

16 68 ms 69 ms 69 ms o5-3bd1.hou005ap01.yipes.com [66.7.143.50]

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.



Trace complete.

[JPC-Greg]

As mentioned above, your pings and traces will not work. We have filtered all icmp traffic for the time being. Its a no brainer, slower network or allow traces . When we are all in the clear with this issue we will allow icmp again.