Is Friendfinder.com down???
Can somebody tell me what is going on with friendfinder.com? For about a month now I have been unable to reach the site. I e-mailed the site and they seem to have no clue that the site might be having trouble.
Adultfriendfinder.com has been up but friendfinder.com continues to not be accessible.
I did some trace routes and here are a few of the results (looks like trouble???):
--------------------------------------------------------------------------------
To perform a traceroute from www.usc.edu,
enter the destination IP address or fully qualified hostname:
traceroute to friendfinder.com (209.185.12.47), 30 hops max, 40 byte packets
1 v253-gw.usc.edu (128.125.253.254) 1.131 ms 0.442 ms 0.281 ms
2 v251-gw-19.usc.edu (128.125.251.155) 0.541 ms 5.352 ms 0.44 ms
3 130.152.181.129 (130.152.181.129) 1.025 ms 0.356 ms 0.26 ms
4 ge-9-3.a01.lsanca02.us.ra.verio.net (198.172.117.161) 0.635 ms 0.566 ms 0.647 ms
5 xe-1-0-0-4.r21.lsanca01.us.bb.verio.net (129.250.29.136) 0.601 ms 0.609 ms 0.641 ms
6 p16-7-0-0.r00.lsanca01.us.bb.verio.net (129.250.2.11) 0.736 ms 1.281 ms 4.939 ms
7 bpr1-so-6-0-0.LosAngeles.savvis.net (208.173.57.21) 0.896 ms 7.568 ms 0.857 ms
8 dcr1-ae0.LosAngeles.savvis.net (208.172.44.5) 2.214 ms dcr2-ae0.LosAngeles.savvis.net (208.172.44.129) 2.053 ms dcr1-ae0.LosAngeles.savvis.net (208.172.44.5) 1.941 ms
9 dcr1-loopback.SanFranciscosfo.savvis.net (206.24.210.99) 13.288 ms 14.272 ms 13.234 ms
10 bhr1-pos-13-0.SantaClarasc5.savvis.net (208.172.147.110) 12.981 ms 12.832 ms 24.423 ms
11 csr3-ve242.SantaClarasc5.savvis.net (64.56.192.154) 14.513 ms 13.063 ms 12.914 ms
12 216.136.135.74 (216.136.135.74) 13.747 ms 13.415 ms *
13 216.136.135.74 (216.136.135.74) 14.53 ms * *
14 * * 216.136.135.74 (216.136.135.74) 13.999 ms
15 * * *
16 * 216.136.135.74 (216.136.135.74) 18.7 ms *
17 * * *
18 * * 216.136.135.74 (216.136.135.74) 14.076 ms
19 * 216.136.135.74 (216.136.135.74) 13.764 ms *
20 * 216.136.135.74 (216.136.135.74) 14.109 ms *
21 * * *
22 * * *
23 * 216.136.135.74 (216.136.135.74) 14.155 ms 28.097 ms
24 * * 216.136.135.74 (216.136.135.74) 13.608 ms
25 * 216.136.135.74 (216.136.135.74) 13.749 ms *
26 216.136.135.74 (216.136.135.74) 14.234 ms * *
27 216.136.135.74 (216.136.135.74) 13.795 ms * *
28 * * *
29 * * 216.136.135.74 (216.136.135.74) 13.822 ms
30 * * *
--------------------------------------------------------------------------------
Traceroute from www.slac.stanford.edu to 209.185.12.47 (friendfinder.com)
traceroute to e47.friendfinder.com (209.185.12.47): 3-30 hops, 38 byte packets
3 rtr-dmz1-ger.slac.stanford.edu (134.79.135.15) 0.464 ms (ttl=253)
4 192.68.191.146 (192.68.191.146) 0.520 ms (ttl=251!)
5 snv-pos-slac.es.net (134.55.209.1) 0.871 ms (ttl=250!)
6 paix-pa-snv.es.net (134.55.208.205) 1.18 ms (ttl=249!)
7 ces1-fastethernet6-2-0-412.PaloAltoPaix.savvis.net (206.24.240.201) 1.19 ms (ttl=248!)
8 dcr2-so-3-3-0.SanFranciscosfo.savvis.net (208.172.147.93) 2.02 ms (ttl=247!)
9 bhr1-pos-13-0.SantaClarasc4.savvis.net (208.172.147.106) 4.22 ms (ttl=247)
10 csr3-ve241.SantaClarasc5.savvis.net (64.56.192.138) 4.29 ms (ttl=54!)
11 *
12 *
13 *
14 *
15 *
16 216.136.135.74 (216.136.135.74) 5.41 ms (ttl=245!) !U
--------------------------------------------------------------------------------
tracing path from www.net.princeton.edu to 209.185.12.47 ...
traceroute to 209.185.12.47 (209.185.12.47), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.500 ms 0.306 ms 0.343 ms
2 vgate1 (128.112.12.22) 0.321 ms 0.294 ms 0.353 ms
3 209.92.72.201 (209.92.72.201) 11.998 ms 5.941 ms 4.253 ms
4 165.113.8.66 (165.113.8.66) 6.642 ms 5.512 ms 6.542 ms
5 4.78.164.9 (4.78.164.9) 5.243 ms 3.692 ms 4.274 ms
6 ge-6-0-0.mp2.Philadelphia1.Level3.net (64.159.0.153) 3.856 ms 3.771 ms 3.197 ms
7 so-7-2-0.bbr2.NewYork1.Level3.net (209.247.8.66) 6.473 ms ae-0-0.bbr1.NewYork1.Level3.net (64.159.1.41) 6.110 ms so-7-2-0.bbr2.NewYork1.Level3.net (209.247.8.66) 4.860 ms
8 ge-6-0-0-55.gar3.NewYork1.Level3.net (4.68.97.132) 6.469 ms ge-7-0-0-52.gar3.NewYork1.Level3.net (4.68.97.36) 5.871 ms ge-6-0-0-55.gar3.NewYork1.Level3.net (4.68.97.132) 5.424 ms
9 dcr6-so-6-1-0.NewYork.savvis.net (4.68.127.206) 5.291 ms 5.720 ms 5.768 ms
10 dcr1-loopback.SanFranciscosfo.savvis.net (206.24.210.99) 81.181 ms 80.114 ms 82.403 ms
11 bhr1-pos-13-0.SantaClarasc5.savvis.net (208.172.147.110) 82.131 ms 83.705 ms 81.982 ms
12 csr4-ve242.SantaClarasc5.savvis.net (64.56.192.155) 82.601 ms 81.651 ms 82.948 ms
13 216.136.148.142 (216.136.148.142) 94.969 ms !X 93.824 ms !X *Done.
What does this mean? What should I tell friendfinder.com? They asked me for "more information" on the issue. How could they not know about this sort of trouble?
Can somebody tell me what is going on with friendfinder.com? For about a month now I have been unable to reach the site. I e-mailed the site and they seem to have no clue that the site might be having trouble.
Adultfriendfinder.com has been up but friendfinder.com continues to not be accessible.
I did some trace routes and here are a few of the results (looks like trouble???):
--------------------------------------------------------------------------------
To perform a traceroute from www.usc.edu,
enter the destination IP address or fully qualified hostname:
traceroute to friendfinder.com (209.185.12.47), 30 hops max, 40 byte packets
1 v253-gw.usc.edu (128.125.253.254) 1.131 ms 0.442 ms 0.281 ms
2 v251-gw-19.usc.edu (128.125.251.155) 0.541 ms 5.352 ms 0.44 ms
3 130.152.181.129 (130.152.181.129) 1.025 ms 0.356 ms 0.26 ms
4 ge-9-3.a01.lsanca02.us.ra.verio.net (198.172.117.161) 0.635 ms 0.566 ms 0.647 ms
5 xe-1-0-0-4.r21.lsanca01.us.bb.verio.net (129.250.29.136) 0.601 ms 0.609 ms 0.641 ms
6 p16-7-0-0.r00.lsanca01.us.bb.verio.net (129.250.2.11) 0.736 ms 1.281 ms 4.939 ms
7 bpr1-so-6-0-0.LosAngeles.savvis.net (208.173.57.21) 0.896 ms 7.568 ms 0.857 ms
8 dcr1-ae0.LosAngeles.savvis.net (208.172.44.5) 2.214 ms dcr2-ae0.LosAngeles.savvis.net (208.172.44.129) 2.053 ms dcr1-ae0.LosAngeles.savvis.net (208.172.44.5) 1.941 ms
9 dcr1-loopback.SanFranciscosfo.savvis.net (206.24.210.99) 13.288 ms 14.272 ms 13.234 ms
10 bhr1-pos-13-0.SantaClarasc5.savvis.net (208.172.147.110) 12.981 ms 12.832 ms 24.423 ms
11 csr3-ve242.SantaClarasc5.savvis.net (64.56.192.154) 14.513 ms 13.063 ms 12.914 ms
12 216.136.135.74 (216.136.135.74) 13.747 ms 13.415 ms *
13 216.136.135.74 (216.136.135.74) 14.53 ms * *
14 * * 216.136.135.74 (216.136.135.74) 13.999 ms
15 * * *
16 * 216.136.135.74 (216.136.135.74) 18.7 ms *
17 * * *
18 * * 216.136.135.74 (216.136.135.74) 14.076 ms
19 * 216.136.135.74 (216.136.135.74) 13.764 ms *
20 * 216.136.135.74 (216.136.135.74) 14.109 ms *
21 * * *
22 * * *
23 * 216.136.135.74 (216.136.135.74) 14.155 ms 28.097 ms
24 * * 216.136.135.74 (216.136.135.74) 13.608 ms
25 * 216.136.135.74 (216.136.135.74) 13.749 ms *
26 216.136.135.74 (216.136.135.74) 14.234 ms * *
27 216.136.135.74 (216.136.135.74) 13.795 ms * *
28 * * *
29 * * 216.136.135.74 (216.136.135.74) 13.822 ms
30 * * *
--------------------------------------------------------------------------------
Traceroute from www.slac.stanford.edu to 209.185.12.47 (friendfinder.com)
traceroute to e47.friendfinder.com (209.185.12.47): 3-30 hops, 38 byte packets
3 rtr-dmz1-ger.slac.stanford.edu (134.79.135.15) 0.464 ms (ttl=253)
4 192.68.191.146 (192.68.191.146) 0.520 ms (ttl=251!)
5 snv-pos-slac.es.net (134.55.209.1) 0.871 ms (ttl=250!)
6 paix-pa-snv.es.net (134.55.208.205) 1.18 ms (ttl=249!)
7 ces1-fastethernet6-2-0-412.PaloAltoPaix.savvis.net (206.24.240.201) 1.19 ms (ttl=248!)
8 dcr2-so-3-3-0.SanFranciscosfo.savvis.net (208.172.147.93) 2.02 ms (ttl=247!)
9 bhr1-pos-13-0.SantaClarasc4.savvis.net (208.172.147.106) 4.22 ms (ttl=247)
10 csr3-ve241.SantaClarasc5.savvis.net (64.56.192.138) 4.29 ms (ttl=54!)
11 *
12 *
13 *
14 *
15 *
16 216.136.135.74 (216.136.135.74) 5.41 ms (ttl=245!) !U
--------------------------------------------------------------------------------
tracing path from www.net.princeton.edu to 209.185.12.47 ...
traceroute to 209.185.12.47 (209.185.12.47), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.500 ms 0.306 ms 0.343 ms
2 vgate1 (128.112.12.22) 0.321 ms 0.294 ms 0.353 ms
3 209.92.72.201 (209.92.72.201) 11.998 ms 5.941 ms 4.253 ms
4 165.113.8.66 (165.113.8.66) 6.642 ms 5.512 ms 6.542 ms
5 4.78.164.9 (4.78.164.9) 5.243 ms 3.692 ms 4.274 ms
6 ge-6-0-0.mp2.Philadelphia1.Level3.net (64.159.0.153) 3.856 ms 3.771 ms 3.197 ms
7 so-7-2-0.bbr2.NewYork1.Level3.net (209.247.8.66) 6.473 ms ae-0-0.bbr1.NewYork1.Level3.net (64.159.1.41) 6.110 ms so-7-2-0.bbr2.NewYork1.Level3.net (209.247.8.66) 4.860 ms
8 ge-6-0-0-55.gar3.NewYork1.Level3.net (4.68.97.132) 6.469 ms ge-7-0-0-52.gar3.NewYork1.Level3.net (4.68.97.36) 5.871 ms ge-6-0-0-55.gar3.NewYork1.Level3.net (4.68.97.132) 5.424 ms
9 dcr6-so-6-1-0.NewYork.savvis.net (4.68.127.206) 5.291 ms 5.720 ms 5.768 ms
10 dcr1-loopback.SanFranciscosfo.savvis.net (206.24.210.99) 81.181 ms 80.114 ms 82.403 ms
11 bhr1-pos-13-0.SantaClarasc5.savvis.net (208.172.147.110) 82.131 ms 83.705 ms 81.982 ms
12 csr4-ve242.SantaClarasc5.savvis.net (64.56.192.155) 82.601 ms 81.651 ms 82.948 ms
13 216.136.148.142 (216.136.148.142) 94.969 ms !X 93.824 ms !X *Done.
What does this mean? What should I tell friendfinder.com? They asked me for "more information" on the issue. How could they not know about this sort of trouble?



Comment