Search for content in message boards

Slow, So Slow, So VERY Slooow.......

Slow, So Slow, So VERY Slooow.......

Posted: 15 Oct 2011 4:31PM GMT
Classification: Query
Could we have an improvement on the speed of the web site please. It's been very slow for the past few days, 2 and a half minutes for a page to load isn't what we pay for!!

So, pretty please, can we have more speed?

Thank you

Re: Slow, So Slow, So VERY Slooow.......

Posted: 15 Oct 2011 5:45PM GMT
Classification: Query
I'm not experiencing site slowness at all.

You are probably aware that internet service providers can determine customers' speed, prioritizing service to some and downgrading service to others. Providers advertise speeds, but may not be providing what is advertised.

This could be what you are experiencing.

You can check your actual effective speed at this site:

http://www.speedtest.net/

Re: Slow, So Slow, So VERY Slooow.......

Posted: 16 Oct 2011 3:12PM GMT
Classification: Query
It ain't that...I checked that mine was OK as soon as I hit this problem, and my speed was as it should be.

There are a lot of people out there complaining about the sudden slow-down in Ancestry.

Re: Slow, So Slow, So VERY Slooow.......

Posted: 16 Oct 2011 4:17PM GMT
Classification: Query
Where are these other people complaining? It sure isn't here.

You might want to ask your ISP to diagnose the problem, because it is not resonating from Ancestry to all customers.

Re: Slow, So Slow, So VERY Slooow.......

Posted: 17 Oct 2011 2:33AM GMT
Classification: Query
The speed leaving your ISP/provider may be fast but there are a lot of hops along the way on the Internet between you and Ancestry's servers in Utah. The slow down could be occurring at any point along the route. Perhaps your ISP support could help you to do a trace route to see where there the delay is occurring? The site hasn't been slow for the rest of us--so there is some issue causing the slowdown between you and Ancestry. If the problem was with Ancestry we'd all notice it.

Joan

Re: Slow, So Slow, So VERY Slooow.......

Posted: 17 Oct 2011 9:55AM GMT
Classification: Query
...on other genealogy message boards. I came here to find out if Ancestry had any answers.

I'm having the same experience as others in that (a) it seemed to have started within the last few days (b) other websites are fine and (c) ISP speed tests don't show any problem - i.e. that individual's connections are running slow.

People are experiencing the problem with various browsers, various OS, so at the moment the only common factor seems to be atempting to view images in Ancestry.

I've got another browser window open at the moment trying to view a 1911 census summary book image and it has been stuck for at least 5 minutes now, although I earlier viewed a 1901 image with no problem.

Re: Slow, So Slow, So VERY Slooow.......

Posted: 17 Oct 2011 2:03PM GMT
Classification: Query
We have received several reports of random slowness on the site. We are investigating the root cause. As some of you have noted, it doesn't affect everyone all of the time - it is sporadic - which makes it more challenging to track down. However, we _are_ working on it. Hopefully, we will have this resolved soon.

Because this is appears to be sporadic, one potential temporary workaround is to simply refresh the browser. That _may_ direct the request to a network segment that is working correctly.

Regards,

Jim Mosher
Search Product Management

Re: Slow, So Slow, So VERY Slooow.......

Posted: 17 Oct 2011 8:59PM GMT
Classification: Query
Edited: 17 Oct 2011 9:04PM GMT
Pick the bones out of the below..................

17/10/2011
21:18

****Now running pathping to www.Ancestry.co.uk****


Tracing route to www.ancestry.com [66.43.22.49]

over a maximum of 30 hops:

0 MINE [0.0.0.0]

1 0.0.0.0

2 lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

3 10.72.4.49

4 10.72.9.223

5 xe-10-3-0.bragg002.loh.as13285.net [80.40.155.25]

6 xe-5-3-0.scr001.loh.as13285.net [80.40.155.64]

7 Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213]

8 xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]

9 xe-1-0-1.er2.iad10.us.above.net [64.125.26.242]

10 206.111.0.213.ptr.us.xo.net [206.111.0.213]

11 207.88.14.162.ptr.us.xo.net [207.88.14.162]

12 vb6.rar3.chicago-il.us.xo.net [207.88.12.33]

13 te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

14 ae0d0.mcr1.saltlake-ut.us.xo.net [216.156.0.2]

15 67.110.119.70.ptr.us.xo.net [67.110.119.70]

16 71.4.83.22.ptr.us.xo.net [71.4.83.22]

17 * * *

Computing statistics for 425 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 Mine [0.0.0.0]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1

0/ 100 = 0% |

2 28ms 0/ 100 = 0% 0/ 100 = 0% lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

0/ 100 = 0% |

3 --- 100/ 100 =100% 100/ 100 =100% 10.72.4.49

0/ 100 = 0% |

4 --- 100/ 100 =100% 100/ 100 =100% 10.72.9.223

0/ 100 = 0% |

5 25ms 0/ 100 = 0% 0/ 100 = 0% xe-10-3-0.bragg002.loh.as13285.net [80.40.155.25]

0/ 100 = 0% |

6 --- 100/ 100 =100% 100/ 100 =100% xe-5-3-0.scr001.loh.as13285.net [80.40.155.64]

0/ 100 = 0% |

7 23ms 1/ 100 = 1% 1/ 100 = 1% Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213]

0/ 100 = 0% |

8 123ms 0/ 100 = 0% 0/ 100 = 0% xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]

0/ 100 = 0% |

9 104ms 0/ 100 = 0% 0/ 100 = 0% xe-1-0-1.er2.iad10.us.above.net [64.125.26.242]

0/ 100 = 0% |

10 108ms 5/ 100 = 5% 5/ 100 = 5% 206.111.0.213.ptr.us.xo.net [206.111.0.213]

0/ 100 = 0% |

11 110ms 1/ 100 = 1% 1/ 100 = 1% 207.88.14.162.ptr.us.xo.net [207.88.14.162]

0/ 100 = 0% |

12 122ms 0/ 100 = 0% 0/ 100 = 0% vb6.rar3.chicago-il.us.xo.net [207.88.12.33]

2/ 100 = 2% |

13 151ms 2/ 100 = 2% 0/ 100 = 0% te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

98/ 100 = 98% |

14 --- 100/ 100 =100% 0/ 100 = 0% ae0d0.mcr1.saltlake-ut.us.xo.net [216.156.0.2]

0/ 100 = 0% |

15 --- 100/ 100 =100% 0/ 100 = 0% 67.110.119.70.ptr.us.xo.net [67.110.119.70]

0/ 100 = 0% |

16 --- 100/ 100 =100% 0/ 100 = 0% 71.4.83.22.ptr.us.xo.net [71.4.83.22]

0/ 100 = 0% |

17 --- 100/ 100 =100% 0/ 100 = 0% MINE [0.0.0.0]



Trace complete.


21:25



Pinging www.ancestry.com [66.43.22.49] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 66.43.22.49:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


21:25


Tracing route to Ancestry.co.uk [66.43.22.122]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 0.0.0.0

2 21 ms 21 ms 21 ms lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

3 20 ms 20 ms 20 ms 10.72.4.49

4 21 ms 21 ms 21 ms 10.72.9.223

5 27 ms 22 ms 21 ms xe-10-3-0.bragg001.loh.as13285.net [80.40.155.21]

6 23 ms 22 ms 23 ms xe-5-0-0.scr001.log.as13285.net [80.40.155.54]

7 25 ms 23 ms 23 ms xe-7-0-0.edge4.London2.Level3.net [212.187.192.109]

8 28 ms 22 ms 30 ms ae-32-52.ebr2.London2.Level3.net [4.68.117.62]

9 23 ms 23 ms 23 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189]

10 23 ms 23 ms 22 ms vlan101.ebr2.London1.Level3.net [4.69.143.86]

11 94 ms 93 ms 93 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

12 95 ms 94 ms 96 ms ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]

13 94 ms 90 ms 92 ms ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]

14 116 ms 114 ms 114 ms ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]

15 114 ms 115 ms 114 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]

16 144 ms 143 ms 142 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]

17 144 ms 141 ms 142 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

18 171 ms 165 ms 167 ms ae-5-5.car2.SaltLakeCity1.Level3.net [4.69.133.125]

19 170 ms 167 ms 167 ms ae-11-11.car1.SaltLakeCity1.Level3.net [4.69.133.121]

20 169 ms * 171 ms AMERICAN-FI.car1.SaltLakeCity1.Level3.net [64.158.68.14]

21 170 ms 167 ms 168 ms unknown.Level3.net [64.158.69.14]

22 169 ms 168 ms 167 ms 71.4.83.18.ptr.us.xo.net [71.4.83.18]

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.


21:28

****Now running pathping to Aunty****


Tracing route to www.bbc.net.uk [212.58.246.91]

over a maximum of 30 hops:

0 MINE [0.0.0.0]

1 0.0.0.0.

2 lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

3 10.72.4.49

4 10.72.9.223

5 xe-8-3-0.bragg002.loh.as13285.net [80.40.155.19]

6 xe-7-3-0.scr001.loh.as13285.net [80.40.155.66]

7 host-78-144-0-121.as13285.net [78.144.0.121]

8 bbc-pp-sov.as13285.net [78.144.5.1]

9 212.58.238.149

10 te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]

11 212.58.255.12

12 bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]



Computing statistics for 300 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 MINE [0.0.0.0]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 0.0.0.0

0/ 100 = 0% |

2 24ms 0/ 100 = 0% 0/ 100 = 0% lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

0/ 100 = 0% |

3 --- 100/ 100 =100% 100/ 100 =100% 10.72.4.49

0/ 100 = 0% |

4 --- 100/ 100 =100% 100/ 100 =100% 10.72.9.223

0/ 100 = 0% |

5 23ms 0/ 100 = 0% 0/ 100 = 0% xe-8-3-0.bragg002.loh.as13285.net [80.40.155.19]

0/ 100 = 0% |

6 --- 100/ 100 =100% 100/ 100 =100% xe-7-3-0.scr001.loh.as13285.net [80.40.155.66]

0/ 100 = 0% |

7 25ms 2/ 100 = 2% 2/ 100 = 2% host-78-144-0-121.as13285.net [78.144.0.121]

0/ 100 = 0% |

8 --- 100/ 100 =100% 100/ 100 =100% bbc-pp-sov.as13285.net [78.144.5.1]

0/ 100 = 0% |

9 27ms 1/ 100 = 1% 1/ 100 = 1% 212.58.238.149

0/ 100 = 0% |

10 24ms 0/ 100 = 0% 0/ 100 = 0% te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]

0/ 100 = 0% |

11 27ms 1/ 100 = 1% 1/ 100 = 1% 212.58.255.12

0/ 100 = 0% |

12 23ms 0/ 100 = 0% 0/ 100 = 0% bbc-vip012.cwwtf.bbc.co.uk [212.58.246.91]



Trace complete.




Pinging www.bbc.net.uk [212.58.246.95] with 32 bytes of data:



Reply from 212.58.246.95: bytes=32 time=25ms TTL=53

Reply from 212.58.246.95: bytes=32 time=21ms TTL=53

Reply from 212.58.246.95: bytes=32 time=23ms TTL=53

Reply from 212.58.246.95: bytes=32 time=24ms TTL=53



Ping statistics for 212.58.246.95:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 21ms, Maximum = 25ms, Average = 23ms


21:33


Tracing route to www.bbc.net.uk [212.58.246.95]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 0.0.0.0

2 20 ms 21 ms 23 ms lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

3 22 ms 20 ms 19 ms 10.72.4.49

4 21 ms 21 ms 21 ms 10.72.9.223

5 22 ms 20 ms 21 ms xe-10-3-0.bragg002.loh.as13285.net [80.40.155.25]

6 22 ms 22 ms 23 ms xe-7-3-0.scr001.loh.as13285.net [80.40.155.66]

7 24 ms 22 ms 83 ms host-78-144-0-121.as13285.net [78.144.0.121]

8 24 ms 21 ms 23 ms bbc-pp-sov.as13285.net [78.144.5.1]

9 25 ms 23 ms 22 ms 212.58.238.149

10 24 ms 24 ms 23 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]

11 26 ms 23 ms 23 ms 212.58.255.12

12 24 ms 22 ms 23 ms bbc-vip016.cwwtf.bbc.co.uk [212.58.246.95]



Trace complete.


21:33
****Now running pathping to www.ancestry.com.au****


Tracing route to Ancestry.com.au [66.43.22.124]

over a maximum of 30 hops:

0 MINE [0.0.0.0]

1 0.0.0.0

2 lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

3 10.72.4.49

4 10.72.9.223

5 xe-8-3-0.bragg002.loh.as13285.net [80.40.155.19]

6 xe-7-3-0.scr001.loh.as13285.net [80.40.155.66]

7 Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213]

8 xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]

9 xe-1-0-1.er2.iad10.us.above.net [64.125.26.242]

10 206.111.0.217.ptr.us.xo.net [206.111.0.217]

11 207.88.14.162.ptr.us.xo.net [207.88.14.162]

12 vb6.rar3.chicago-il.us.xo.net [207.88.12.33]

13 te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

14 ae0d0.mcr1.saltlake-ut.us.xo.net [216.156.0.2]

15 67.110.119.70.ptr.us.xo.net [67.110.119.70]

16 71.4.83.22.ptr.us.xo.net [71.4.83.22]

17 * * *

Computing statistics for 425 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 MINE [0.0.0.0]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 0.0.0.0

0/ 100 = 0% |

2 25ms 0/ 100 = 0% 0/ 100 = 0% lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

0/ 100 = 0% |

3 --- 100/ 100 =100% 100/ 100 =100% 10.72.4.49

0/ 100 = 0% |

4 --- 100/ 100 =100% 100/ 100 =100% 10.72.9.223

0/ 100 = 0% |

5 25ms 0/ 100 = 0% 0/ 100 = 0% xe-8-3-0.bragg002.loh.as13285.net [80.40.155.19]

0/ 100 = 0% |

6 --- 100/ 100 =100% 100/ 100 =100% xe-7-3-0.scr001.loh.as13285.net [80.40.155.66]

0/ 100 = 0% |

7 24ms 0/ 100 = 0% 0/ 100 = 0% Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213]

0/ 100 = 0% |

8 121ms 0/ 100 = 0% 0/ 100 = 0% xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]

0/ 100 = 0% |

9 103ms 1/ 100 = 1% 1/ 100 = 1% xe-1-0-1.er2.iad10.us.above.net [64.125.26.242]

0/ 100 = 0% |

10 99ms 1/ 100 = 1% 1/ 100 = 1% 206.111.0.217.ptr.us.xo.net [206.111.0.217]

0/ 100 = 0% |

11 110ms 0/ 100 = 0% 0/ 100 = 0% 207.88.14.162.ptr.us.xo.net [207.88.14.162]

1/ 100 = 1% |

12 121ms 1/ 100 = 1% 0/ 100 = 0% vb6.rar3.chicago-il.us.xo.net [207.88.12.33]

0/ 100 = 0% |

13 151ms 1/ 100 = 1% 0/ 100 = 0% te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

99/ 100 = 99% |

14 --- 100/ 100 =100% 0/ 100 = 0% ae0d0.mcr1.saltlake-ut.us.xo.net [216.156.0.2]

0/ 100 = 0% |

15 --- 100/ 100 =100% 0/ 100 = 0% 67.110.119.70.ptr.us.xo.net [67.110.119.70]

0/ 100 = 0% |

16 --- 100/ 100 =100% 0/ 100 = 0% 71.4.83.22.ptr.us.xo.net [71.4.83.22]

0/ 100 = 0% |

17 --- 100/ 100 =100% 0/ 100 = 0% MINE [0.0.0.0]



Trace complete.




Pinging e5255.b.akamaiedge.net [2.16.165.73] with 32 bytes of data:



Reply from 2.16.165.73: bytes=32 time=34ms TTL=56

Reply from 2.16.165.73: bytes=32 time=23ms TTL=56

Request timed out.

Reply from 2.16.165.73: bytes=32 time=22ms TTL=56



Ping statistics for 2.16.165.73:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

Approximate round trip times in milli-seconds:

Minimum = 22ms, Maximum = 34ms, Average = 26ms


21:40


Tracing route to e5255.b.akamaiedge.net [2.16.165.73]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 0.0.0.0

2 22 ms 22 ms 21 ms lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

3 20 ms 21 ms 35 ms 10.72.4.49

4 31 ms 21 ms 21 ms 10.72.9.223

5 26 ms 21 ms 21 ms xe-10-3-0.bragg001.loh.as13285.net [80.40.155.21]

6 23 ms 21 ms 23 ms xe-7-0-0.scr001.log.as13285.net [80.40.155.56]

7 23 ms 22 ms 23 ms xe-9-3-1.lon10.ip4.tinet.net [77.67.64.5]

8 23 ms 23 ms 23 ms 2.16.165.73



Trace complete.


21:41


Tracing route to Ancestry.com.au [66.43.22.124]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 0.0.0.0

2 20 ms 20 ms 19 ms lo98.sc-acc-sip-2.as9105.net [212.74.102.15]

3 21 ms 21 ms 21 ms 10.72.4.49

4 20 ms 20 ms 21 ms 10.72.9.223

5 23 ms 21 ms 20 ms xe-8-3-0.bragg002.loh.as13285.net [80.40.155.19]

6 24 ms 22 ms 23 ms xe-7-3-0.scr001.loh.as13285.net [80.40.155.66]

7 27 ms 23 ms 22 ms Opal-ge-2.2.0.mpr1.lhr3.above.net [213.161.78.213]

8 102 ms 98 ms 99 ms xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]

9 118 ms 101 ms 100 ms xe-1-0-1.er2.iad10.us.above.net [64.125.26.242]

10 103 ms 102 ms 101 ms 206.111.0.217.ptr.us.xo.net [206.111.0.217]

11 107 ms 108 ms 106 ms 207.88.14.162.ptr.us.xo.net [207.88.14.162]

12 173 ms 171 ms 189 ms vb6.rar3.chicago-il.us.xo.net [207.88.12.33]

13 170 ms 177 ms 179 ms te-4-1-0.rar3.denver-co.us.xo.net [207.88.12.22]

14 169 ms 168 ms 167 ms ae0d0.mcr1.saltlake-ut.us.xo.net [216.156.0.2]

15 172 ms 165 ms 165 ms 67.110.119.70.ptr.us.xo.net [67.110.119.70]

16 167 ms 166 ms 167 ms 71.4.83.22.ptr.us.xo.net [71.4.83.22]

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.


21:44
Attachments:

Re: Slow, So Slow, So VERY Slooow.......

Posted: 18 Oct 2011 2:35AM GMT
Classification: Query
I had mentioned that it was slow a couple days ago. Shortly after I posted, it cleared up and has been fine since then. Appreciate the response.

Re: Slow, So Slow, So VERY Slooow.......

Posted: 18 Oct 2011 7:59PM GMT
Classification: Query
i wish I could report that the speed had improved - it would also have been helpful to receive a response to the email i sent. The last 5 nights have been truly frustrating / annoying.
Also has anyone else noticed that hints seem to have re-loaded all 1901 records? Even where I had already located the record and saved it to the individuals within the tree I am finding that the 1901 records are appearing as new hints:clearly because I am checking hints this is very time consuming and since in the majority of cases the 1901 census record has already been saved is wasting precious time.
one very frustrated customer
per page

Find a board about a specific topic