Having Site Speed Issues (FIXED)
Comcast IP's only change about once every 4 months, not every time I reeboot. Dial-up connections are given a different IP everytime they connect. Your IP has nothing to do with rebooting your computer unless your ISP changed their IP pool while you were on line.
Yes IP can be had for those in the know, but I am not going to give it to people that don't know how to get it.
Yes IP can be had for those in the know, but I am not going to give it to people that don't know how to get it.
Comcast IP's only change about once every 4 months, not every time I reeboot. Dial-up connections are given a different IP everytime they connect. Your IP has nothing to do with rebooting your computer unless your ISP changed their IP pool while you were on line.
Yes IP can be had for those in the know, but I am not going to give it to people that don't know how to get it.
Yes IP can be had for those in the know, but I am not going to give it to people that don't know how to get it.
Nate, slow from my end:
7:40 AM
Woodland HIlls, CA
71.140.254.21
Please leave this thread to report speed and connectivity issues. We only asked for some information, If you do not want to supply the information then don't.
At least report the first 2 sets of numbers so we can see who the ISP is and the area. How can we trouble shoot these issues without some basic info.
Doc, I'm in pain
Where
My body
Where on your body
Oh here and there
Just as the doctor can't localize the issue neither can we. Hence we all suffer.
At least report the first 2 sets of numbers so we can see who the ISP is and the area. How can we trouble shoot these issues without some basic info.
Doc, I'm in pain
Where
My body
Where on your body
Oh here and there
Just as the doctor can't localize the issue neither can we. Hence we all suffer.
Coordinator :: Eastern Iowa MINIs
iTrader: (1)
Joined: Aug 2007
Posts: 1,163
Likes: 1
From: Round Rock, TX
This morning 5:45 AM CST - 6:15 AM CST the site was not reachable from my home connection (MediaCOM) Database error
Even other sites that have active links to this site were reporting DB errors on there feeds.
But over all not terrible speed from work today
162.123.233.132
Even other sites that have active links to this site were reporting DB errors on there feeds.
But over all not terrible speed from work today
162.123.233.132
Your IP changes depending on the ISP
Obtaining your IP is no hard thing to do, everyone that connects to a forum such as this has their IP captured anyway. Lots of people have access to that data.
Posting an IP is not like posting a CC or SSN. Chances are the IP will change with the next reboot.
Obtaining your IP is no hard thing to do, everyone that connects to a forum such as this has their IP captured anyway. Lots of people have access to that data.
Posting an IP is not like posting a CC or SSN. Chances are the IP will change with the next reboot.
BTW mine is static at home as well. but i put that one through a proxy so you can't see it.
Site very slow last night 6pm on EST from Massachusettes
Site very slow today 6am till this post and probably beyond this post. Many times i get not responding messages on both Firefox and IE browsers on windows machines. Massachusettes
Very slow site speed here in downtown Hooterville last night & today at 1:21 Eastern time.
No clue what my IP address is. I'm LAME & clueless.
Maybe NAM's supercharger belt is slipping.
No clue what my IP address is. I'm LAME & clueless.
Maybe NAM's supercharger belt is slipping.
Coordinator :: Eastern Iowa MINIs
iTrader: (1)
Joined: Aug 2007
Posts: 1,163
Likes: 1
From: Round Rock, TX
Tracing route to www.northamericanmotoring.com [67.201.16.207]
over a maximum of 30 hops:
0 CRGCL5WD1.us.aegon.com [162.123.233.132]
1 162.123.233.3
2 162.123.21.4
3 162.123.1.225
4 162.123.98.15
5 12.20.92.253
6 12.125.120.25
7 gbr1.cgcil.ip.att.net [12.123.193.66]
8 cr1.cgcil.ip.att.net [12.122.11.33]
9 tbr1.cgcil.ip.att.net [12.122.17.154]
10 ggr2.cgcil.ip.att.net [12.123.6.29]
11 192.205.33.210
12 ae-31-55.ebr1.chicago1.level3.net [4.68.101.158]
13 ae-68.ebr3.chicago1.level3.net [4.69.134.58]
14 ae-3.ebr2.denver1.level3.net [4.69.132.61]
15 ae-1-100.ebr1.denver1.level3.net [4.69.132.37]
16 ae-3.ebr2.sanjose1.level3.net [4.69.132.57]
17 ae-72-72.csw2.sanjose1.level3.net [4.69.134.214]
18 ae-73-73.ebr3.sanjose1.level3.net [4.69.134.229]
19 ae-2.ebr3.losangeles1.level3.net [4.69.132.10]
20 ae-83-83.csw3.losangeles1.level3.net [4.69.137.42]
21 ae-3-89.edge3.losangeles1.level3.net [4.68.20.137]
22 xe2-0.cr01.lax01.mzima.net [4.71.136.2]
23 xe0-7.cr02.lax06.mzima.net [216.193.255.66]
24 67.201.16.207
25 67.201.16.207
Computing statistics for 625 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 CRGCL5WD1.us.aegon.com [162.123.233.132]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 162.123.233.3
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 162.123.21.4
0/ 100 = 0% |
3 1ms 0/ 100 = 0% 0/ 100 = 0% 162.123.1.225
0/ 100 = 0% |
4 1ms 0/ 100 = 0% 0/ 100 = 0% 162.123.98.15
0/ 100 = 0% |
5 2ms 0/ 100 = 0% 0/ 100 = 0% 12.20.92.253
0/ 100 = 0% |
6 28ms 0/ 100 = 0% 0/ 100 = 0% 12.125.120.25
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% gbr1.cgcil.ip.att.net [12.123.193.66]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.11.33]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% tbr1.cgcil.ip.att.net [12.122.17.154]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% ggr2.cgcil.ip.att.net [12.123.6.29]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 192.205.33.210
0/ 100 = 0% |
12 23ms 0/ 100 = 0% 0/ 100 = 0% ae-31-55.ebr1.chicago1.level3.net [4.68.101.158]
0/ 100 = 0% |
13 23ms 0/ 100 = 0% 0/ 100 = 0% ae-68.ebr3.chicago1.level3.net [4.69.134.58]
0/ 100 = 0% |
14 58ms 0/ 100 = 0% 0/ 100 = 0% ae-3.ebr2.denver1.level3.net [4.69.132.61]
0/ 100 = 0% |
15 55ms 0/ 100 = 0% 0/ 100 = 0% ae-1-100.ebr1.denver1.level3.net [4.69.132.37]
0/ 100 = 0% |
16 73ms 0/ 100 = 0% 0/ 100 = 0% ae-3.ebr2.sanjose1.level3.net [4.69.132.57]
0/ 100 = 0% |
17 74ms 0/ 100 = 0% 0/ 100 = 0% ae-72-72.csw2.sanjose1.level3.net [4.69.134.214]
0/ 100 = 0% |
18 75ms 0/ 100 = 0% 0/ 100 = 0% ae-73-73.ebr3.sanjose1.level3.net [4.69.134.229]
0/ 100 = 0% |
19 84ms 0/ 100 = 0% 0/ 100 = 0% ae-2.ebr3.losangeles1.level3.net [4.69.132.10]
0/ 100 = 0% |
20 83ms 0/ 100 = 0% 0/ 100 = 0% ae-83-83.csw3.losangeles1.level3.net [4.69.137.42]
0/ 100 = 0% |
21 86ms 0/ 100 = 0% 0/ 100 = 0% ae-3-89.edge3.losangeles1.level3.net [4.68.20.137]
0/ 100 = 0% |
22 82ms 0/ 100 = 0% 0/ 100 = 0% xe2-0.cr01.lax01.mzima.net [4.71.136.2]
0/ 100 = 0% |
23 84ms 0/ 100 = 0% 0/ 100 = 0% xe0-7.cr02.lax06.mzima.net [216.193.255.66]
9/ 100 = 9% |
24 82ms 28/ 100 = 28% 19/ 100 = 19% 67.201.16.207
0/ 100 = 0% |
25 82ms 9/ 100 = 9% 0/ 100 = 0% 67.201.16.207
Trace complete.
The 100% losses on hops 7, 8, 9, 10 and 11 are normal but hops 24 and 25 at 28% and 9% loss are I believe where the problem lays.
That is the IP of your server this is a server problem not a wan issue I believe
over a maximum of 30 hops:
0 CRGCL5WD1.us.aegon.com [162.123.233.132]
1 162.123.233.3
2 162.123.21.4
3 162.123.1.225
4 162.123.98.15
5 12.20.92.253
6 12.125.120.25
7 gbr1.cgcil.ip.att.net [12.123.193.66]
8 cr1.cgcil.ip.att.net [12.122.11.33]
9 tbr1.cgcil.ip.att.net [12.122.17.154]
10 ggr2.cgcil.ip.att.net [12.123.6.29]
11 192.205.33.210
12 ae-31-55.ebr1.chicago1.level3.net [4.68.101.158]
13 ae-68.ebr3.chicago1.level3.net [4.69.134.58]
14 ae-3.ebr2.denver1.level3.net [4.69.132.61]
15 ae-1-100.ebr1.denver1.level3.net [4.69.132.37]
16 ae-3.ebr2.sanjose1.level3.net [4.69.132.57]
17 ae-72-72.csw2.sanjose1.level3.net [4.69.134.214]
18 ae-73-73.ebr3.sanjose1.level3.net [4.69.134.229]
19 ae-2.ebr3.losangeles1.level3.net [4.69.132.10]
20 ae-83-83.csw3.losangeles1.level3.net [4.69.137.42]
21 ae-3-89.edge3.losangeles1.level3.net [4.68.20.137]
22 xe2-0.cr01.lax01.mzima.net [4.71.136.2]
23 xe0-7.cr02.lax06.mzima.net [216.193.255.66]
24 67.201.16.207
25 67.201.16.207
Computing statistics for 625 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 CRGCL5WD1.us.aegon.com [162.123.233.132]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 162.123.233.3
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 162.123.21.4
0/ 100 = 0% |
3 1ms 0/ 100 = 0% 0/ 100 = 0% 162.123.1.225
0/ 100 = 0% |
4 1ms 0/ 100 = 0% 0/ 100 = 0% 162.123.98.15
0/ 100 = 0% |
5 2ms 0/ 100 = 0% 0/ 100 = 0% 12.20.92.253
0/ 100 = 0% |
6 28ms 0/ 100 = 0% 0/ 100 = 0% 12.125.120.25
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% gbr1.cgcil.ip.att.net [12.123.193.66]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.11.33]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% tbr1.cgcil.ip.att.net [12.122.17.154]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% ggr2.cgcil.ip.att.net [12.123.6.29]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 192.205.33.210
0/ 100 = 0% |
12 23ms 0/ 100 = 0% 0/ 100 = 0% ae-31-55.ebr1.chicago1.level3.net [4.68.101.158]
0/ 100 = 0% |
13 23ms 0/ 100 = 0% 0/ 100 = 0% ae-68.ebr3.chicago1.level3.net [4.69.134.58]
0/ 100 = 0% |
14 58ms 0/ 100 = 0% 0/ 100 = 0% ae-3.ebr2.denver1.level3.net [4.69.132.61]
0/ 100 = 0% |
15 55ms 0/ 100 = 0% 0/ 100 = 0% ae-1-100.ebr1.denver1.level3.net [4.69.132.37]
0/ 100 = 0% |
16 73ms 0/ 100 = 0% 0/ 100 = 0% ae-3.ebr2.sanjose1.level3.net [4.69.132.57]
0/ 100 = 0% |
17 74ms 0/ 100 = 0% 0/ 100 = 0% ae-72-72.csw2.sanjose1.level3.net [4.69.134.214]
0/ 100 = 0% |
18 75ms 0/ 100 = 0% 0/ 100 = 0% ae-73-73.ebr3.sanjose1.level3.net [4.69.134.229]
0/ 100 = 0% |
19 84ms 0/ 100 = 0% 0/ 100 = 0% ae-2.ebr3.losangeles1.level3.net [4.69.132.10]
0/ 100 = 0% |
20 83ms 0/ 100 = 0% 0/ 100 = 0% ae-83-83.csw3.losangeles1.level3.net [4.69.137.42]
0/ 100 = 0% |
21 86ms 0/ 100 = 0% 0/ 100 = 0% ae-3-89.edge3.losangeles1.level3.net [4.68.20.137]
0/ 100 = 0% |
22 82ms 0/ 100 = 0% 0/ 100 = 0% xe2-0.cr01.lax01.mzima.net [4.71.136.2]
0/ 100 = 0% |
23 84ms 0/ 100 = 0% 0/ 100 = 0% xe0-7.cr02.lax06.mzima.net [216.193.255.66]
9/ 100 = 9% |
24 82ms 28/ 100 = 28% 19/ 100 = 19% 67.201.16.207
0/ 100 = 0% |
25 82ms 9/ 100 = 9% 0/ 100 = 0% 67.201.16.207
Trace complete.
The 100% losses on hops 7, 8, 9, 10 and 11 are normal but hops 24 and 25 at 28% and 9% loss are I believe where the problem lays.
That is the IP of your server this is a server problem not a wan issue I believe
Coordinator :: Eastern Iowa MINIs
iTrader: (1)
Joined: Aug 2007
Posts: 1,163
Likes: 1
From: Round Rock, TX
The more I think about this it could be
1. DDOS attack
2. Bad NIC on the server
3. Server with not nearly enough CPU cycles to perform the DB functions thrown at it (didnt the DB just change a lot)
If you need me to test anything further just let me know more than willing to assist where I can
1. DDOS attack
2. Bad NIC on the server
3. Server with not nearly enough CPU cycles to perform the DB functions thrown at it (didnt the DB just change a lot)
If you need me to test anything further just let me know more than willing to assist where I can
Your IP changes depending on the ISP
Obtaining your IP is no hard thing to do, everyone that connects to a forum such as this has their IP captured anyway. Lots of people have access to that data.
Posting an IP is not like posting a CC or SSN. Chances are the IP will change with the next reboot.
Obtaining your IP is no hard thing to do, everyone that connects to a forum such as this has their IP captured anyway. Lots of people have access to that data.
Posting an IP is not like posting a CC or SSN. Chances are the IP will change with the next reboot.
Tell me how I find out my IP and I'll report it.
Working much better now!!
Man we are spoiled. I remember back when
there was no internet, phones had cords, had to actually use a key to unlock doors,
I WAS the remote!!! Now I get all buched-up when my 'puter is slow!
there was no internet, phones had cords, had to actually use a key to unlock doors,
I WAS the remote!!! Now I get all buched-up when my 'puter is slow!
Or if you'd like something you can cut/paste into your post, go to www.whatismyip.com and it'll display your IP. The font will be huge when you paste it into your post, but when you hit "submit", it'll end up normal size.





