Could you please trace one my IP 130.94.171.89.
I don't know why, but there is no access from some locations.
1 20 ms 20 ms 21 ms adsl-6xxxxx
2 20 ms 20 ms 20 ms dist3-vlan50.snfc21.pbi.net[206.171.134.132]
3 20 ms 30 ms 20 ms bb2-g8-0.snfc21.pbi.net [209.232.130.83]
4 20 ms 30 ms 20 ms bb1-p14-0.snfc21.pbi.net [64.161.124.53]
5 20 ms 30 ms 20 ms sl-gw11-sj-3-0.sprintlink.net[144.228.44.49]
6 20 ms 31 ms 20 ms sl-bb20-sj-8-1.sprintlink.net[144.232.3.137]
7 40 ms 40 ms 40 ms sl-bb20-tac-11-1.sprintlink.net[144.232.9.214]
8 70 ms 80 ms 70 ms sl-bb21-che-4-1.sprintlink.net[144.232.19.246]
9 70 ms 81 ms 80 ms sl-gw10-che-10-0.sprintlink.net[144.232.15.166]
10 80 ms 81 ms 80 ms sl-timewarner-2-0.sprintlink.net[144.223.40.170]
11 80 ms 80 ms 80 ms core-01-ge-1-1-.dnvr.twtelecom.net[168.215.54.193]
12 200 ms 811 ms 511 ms 66.162.99.250
13 70 ms 70 ms 60 ms 66.162.99.2
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 *
Customer reported that everyone on AOL cant get to the server.
Thank you
Interestingly, domainwhitepages.com shows no data against that IP, although I can go there myself ( error page )
This is a traceroute from Au just for info...
traceroute to 130.94.171.89 (130.94.171.89), 30 hops max, 40 byte packets
1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.468 ms 0.47 ms 0.439 ms
2 GigabitEthernet0-0-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.553 ms 0.547 ms 0.437 ms
3 GigabitEthernet4-0-0.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.75 ms 0.718 ms 0.764 ms
4 Pos4-1.ken-core4.Sydney.telstra.net (203.50.6.69) 4.684 ms 4.666 ms 4.706 ms
5 Pos2-0.pad-core4.Sydney.telstra.net (203.50.6.22) 4.833 ms 4.775 ms 4.877 ms
6 GigabitEthernet0-0.syd-core01.Sydney.net.reach.com (203.50.13.242) 4.845 ms 4.939 ms 4.732 ms
7 202.84.249.217 (202.84.249.217) 161.315 ms 161.072 ms 161.198 ms
8 202.84.249.177 (202.84.249.177) 161.615 ms 161.318 ms 161.629 ms
9 fast3-0-0-0.paix-igr01.twtelecom.net (198.32.176.111) 164.318 ms 161.644 ms 161.697 ms
10 core-01-t3-3-1-0.mdso.twtelecom.net (168.215.54.253) 165.089 ms 165.385 ms 166.249 ms
11 core-02-ge-3-3-0.mdso.twtelecom.net (168.215.55.106) 165.091 ms 165.504 ms 164.781 ms
12 core-01-so-0-0-0.lsag.twtelecom.net (168.215.53.29) 174.436 ms 176.76 ms 177.348 ms
13 core-02-ge-0-2-1.lsag.twtelecom.net (168.215.53.22) 173.949 ms 174.789 ms 176.083 ms
14 core-02-so-0-0-0.mkpl.twtelecom.net (168.215.53.74) 186.229 ms 181.918 ms 181.779 ms
15 core-01-ge-3-3-0.mkpl.twtelecom.net (168.215.55.121) 186.211 ms 182.226 ms 181.818 ms
16 core-01-so-0-0-0.slcy.twtelecom.net (168.215.55.109) 189.664 ms 189.613 ms 189.829 ms
17 core-01-ge-3-3-0.slcy.twtelecom.net (168.215.55.181) 190.15 ms 189.666 ms 190.392 ms
18 core-01-so-1-0-0.dnvr.twtelecom.net (168.215.55.213) 199.636 ms 201.127 ms 201.141 ms
19 66.162.99.250 (66.162.99.250) 200.637 ms 200.865 ms 200.719 ms
20 66.162.99.2 (66.162.99.2) 244.232 ms 244.215 ms 243.453 ms
21 130.94.171.89 (130.94.171.89) 434.246 ms 243.411 ms 243.581 ms
Lats...
David@Digisurge
02-26-2002, 10:57 PM
Tracert via the MSN Network. I am located in Northern Indiana.
Trace 130.94.171.89 ...
1 192.168.0.1 0ms 0ms 0ms TTL: 0 (XXXXXXXX ok)
2 67.217.128.54 134ms 109ms 114ms TTL: 0 (tnt2.XXXXXX.in.da.uu.net ok)
3 67.217.130.125 215ms 119ms 135ms TTL: 0 (No rDNS)
4 152.63.65.190 223ms 209ms 183ms TTL: 0 (155.at-3-1-0.HR4.CHI2.ALTER.NET ok)
5 152.63.68.50 197ms 199ms 184ms TTL: 0 (160.at-5-0-0.XR1.CHI2.ALTER.NET ok)
6 152.63.67.129 172ms 166ms 184ms TTL: 0 (0.so-2-1-0.XL1.CHI2.ALTER.NET ok)
7 152.63.68.1 130ms 142ms 154ms TTL: 0 (POS6-0.BR3.CHI2.ALTER.NET ok)
8 4.24.203.29 193ms 218ms 184ms TTL: 0 (a3-0-1.chcgil2-cr2.bbnplanet.net ok)
9 4.24.9.33 126ms 137ms 163ms TTL: 0 (so-2-3-0.chcgil2-br2.bbnplanet.net ok)
10 4.24.9.62 177ms 185ms 194ms TTL: 0 (so-1-0-0.dnvtco1-br2.bbnplanet.net ok)
11 4.24.11.42 159ms 188ms 233ms TTL: 0 (p1-0.dnvtco1-cr2.bbnplanet.net ok)
12 4.24.11.57 192ms 167ms 203ms TTL: 0 (p2-0.dnvtco1-cr1.bbnplanet.net ok)
13 4.25.24.62 185ms 237ms 231ms TTL: 0 (gigabitethernet0.yipes9.bbnplanet.net ok)
14 209.50.40.181 185ms 197ms 212ms TTL: 0 (No rDNS)
15 209.50.40.62 193ms 215ms 220ms TTL: 0 (No rDNS)
16 66.7.174.90 185ms 243ms 260ms TTL: 0 (No rDNS)
17 130.94.171.89 210ms 214ms 273ms TTL:237 (No rDNS)
Thank you.
Why I (and 90%) can access this IP and around 5-10% of visitors can't? What is wrong.
BTW, if user can't access to this IP, he can't access to ALL ips on the server.
:eek:
What is wrong?
Jay Suds
02-27-2002, 01:42 AM
I can trace in fine over Level3 / Genuity, but whenver I go over TimeWarner (which explains the AOL problems ... AOL = TimeWarner), I can't ping your IP / get a destination address unreachable on a traceroute.
Interestingly, I can access other IPs in that data center without any problems on both TimeWarner and Level3 / Genuity.
Have you tried contacting your host?
DigitalXWeb
02-27-2002, 02:02 AM
This is from Timewarner on the Eastcoast..
1 10 ms 10 ms 10 ms 10.142.64.1
2 * * * Request timed out.
3 * * * Request timed out.
4 <10 ms <10 ms <10 ms 68.82.0.50
5 20 ms 20 ms 20 ms sl-gw4-spr-6-1.sprintlink.net [160.81.249.73]
6 20 ms 20 ms 20 ms sl-bb11-spr-0-0.sprintlink.net [144.232.21.50]
7 30 ms 41 ms 30 ms sl-bb21-chi-6-2.sprintlink.net [144.232.19.205]
8 50 ms 50 ms 60 ms sl-bb21-che-5-1.sprintlink.net [144.232.18.5]
9 50 ms 50 ms 50 ms sl-gw10-che-10-0.sprintlink.net [144.232.15.166]
10 50 ms 61 ms 50 ms sl-timewarner-2-0.sprintlink.net [144.223.40.170
]
11 50 ms 60 ms 50 ms core-01-ge-1-1-0.dnvr.twtelecom.net [168.215.54.
193]
12 140 ms 80 ms 60 ms 66.162.99.250
13 60 ms 61 ms 60 ms 66.162.99.2
14 60 ms 60 ms 50 ms 130.94.171.89
Jay Suds
02-27-2002, 02:12 AM
So weird. Here's my trace from the East Coast (connecticut). I can't get to the IP:
Target Name: N/A
IP: 130.94.171.89
Date/Time: 2/27/2002 1:07:42 AM
1 0 ms 0 ms 0 ms [192.168.123.254]
2 20 ms 20 ms 20 ms 1.64.252.64.snet.net [64.252.64.1]
3 20 ms 20 ms 20 ms [204.60.203.129]
4 20 ms 20 ms 20 ms [204.60.219.33]
5 30 ms 40 ms 40 ms bb1-p5-1.hrndva.sbcglobal.net [151.164.89.41]
6 30 ms 40 ms 30 ms bb2-p14-0.hrndva.sbcglobal.net [151.164.243.22]
7 40 ms 40 ms 40 ms mae-east.twtelecom.com [198.32.187.48]
8 40 ms 40 ms 40 ms core-02-so-1-1-0.chrl.twtelecom.net [168.215.53.129]
9 51 ms 50 ms 50 ms core-02-so-2-2-0.atln.twtelecom.net [168.215.53.146]
10 50 ms 50 ms 50 ms core-01-ge-2-3-0.atln.twtelecom.net [168.215.55.229]
11 70 ms 70 ms 70 ms core-01-so-2-2-0.dlfw.twtelecom.net [168.215.53.65]
12 90 ms 90 ms 90 ms core-01-so-0-0-0.dnvr.twtelecom.net [168.215.53.70]
13 90 ms 90 ms 90 ms [66.162.99.250]
14 90 ms 91 ms * [66.162.99.2]
15 * * * [-]
Jay Suds
02-27-2002, 04:10 AM
Hi H2. The problem should be resolved. I talked with Paul from VO on ICQ and everything seems to be running fine now :)
yes. :D they fixed problem. Some how port sentry started blocking the whole 64.0.0.0 class A IP space..
venturesonline.com - the BEST!!!