Bishop Hill Slow
Aug 6, 2014 Blogs Some people are experiencing positively glacial performance from the site. It's an issue with Squarespace, who are investigating.
Bishop Hill
Squarespace Help are asking for information from people suffering from slow performance. Here's the details. Answers in the comments [or by email] please:
I'll need to know your visitors IP address. To find it, visit this site:
http://www.whatismyip.com
I'll also need them to do a traceroute. If you're using a Mac, open Spotlight by pressing Command+Space and open the Terminal.
Then, type traceroute and a space followed by your domain name. Press Enter.
If you're on a PC, go to Start > All Programs > Accessories > Command Prompt.
Then, type tracert and a space followed by your domain name. Press Enter.
Once you've done that, you'll need to do two more traceroutes: one for CNAME and another for IP
Update the CNAME and IP for the customer's platform:
CNAME:
five.squarespace.com
IP
65.39.205.54
When all three traceroutes are done, copy everything in the Terminal or Command Prompt and paste it into your reply along with your IP address.
Thanks.
Reader Comments (66)
Things seem a bit snappier now!
From IP: 86.132.93.52
C:\>tracert www.bishop-hill.netTracing route to five.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BThomehub.home [192.168.1.1]
2 5 ms 5 ms 4 ms 217.32.142.109
3 5 ms 5 ms 6 ms 217.32.142.174
4 11 ms 11 ms 10 ms 212.140.206.18
5 11 ms 11 ms 11 ms 213.120.162.67
6 11 ms 11 ms 11 ms 31.55.165.107
7 11 ms 10 ms 41 ms 109.159.250.54
8 16 ms 18 ms 24 ms core2-te0-13-0-15.ilford.ukcore.bt.net [109.159.250.36]
9 17 ms 17 ms 18 ms peer1-xe1-1-0.telehouse.ukcore.bt.net [109.159.254.134]
10 20 ms 19 ms 20 ms blackhole.prolexic.com [195.66.224.31]
11 23 ms 22 ms 22 ms unknown.prolexic.com [72.52.60.35]
12 * * * Request timed out.
13 110 ms 110 ms 110 ms unknown.prolexic.com [209.200.168.148]
14 109 ms 109 ms 109 ms 198.185.159.136
Trace complete.
C:\>tracert five.squarespace.com
Tracing route to five.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BThomehub.home [192.168.1.1]
2 5 ms 4 ms 5 ms 217.32.142.109
3 5 ms 5 ms 5 ms 217.32.142.174
4 11 ms 11 ms 11 ms 212.140.206.18
5 11 ms 11 ms 11 ms 213.120.162.67
6 11 ms 11 ms 11 ms 31.55.165.107
7 17 ms 11 ms 11 ms acc1-10GigE-1-3-0.mr.21cn-ipp.bt.net [109.159.250.86]
8 25 ms 18 ms 20 ms core1-te0-5-0-1.ealing.ukcore.bt.net [109.159.250.20]
9 17 ms 17 ms 17 ms peer1-xe1-1-0.telehouse.ukcore.bt.net [109.159.254.134]
10 19 ms 19 ms 19 ms blackhole.prolexic.com [195.66.224.31]
11 23 ms 23 ms 23 ms unknown.prolexic.com [72.52.60.35]
12 * * * Request timed out.
13 110 ms 110 ms 110 ms unknown.prolexic.com [209.200.168.148]
14 * 110 ms 110 ms 198.185.159.136
Trace complete.
C:\>tracert 65.39.205.54
Tracing route to squarespace.com [65.39.205.54]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms BThomehub.home [192.168.1.1]
2 5 ms 4 ms 4 ms 217.32.142.109
3 5 ms 5 ms 5 ms 217.32.142.158
4 11 ms 11 ms 11 ms 212.140.206.10
5 11 ms 11 ms 11 ms 213.120.162.67
6 11 ms 12 ms 11 ms 31.55.165.107
7 11 ms 11 ms 48 ms 109.159.250.60
8 18 ms 18 ms 19 ms core1-te0-3-0-5.ealing.ukcore.bt.net [109.159.250.13]
9 39 ms 18 ms 17 ms peer1-xe0-0-0.telehouse.ukcore.bt.net [109.159.254.96]
10 18 ms 17 ms 17 ms 10ge.xe-0-0-0.linxb.ldn-teleh-dis-1.peer1.net [195.66.224.156]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 104 ms 105 ms 104 ms 69.90.122.29
15 90 ms 90 ms 91 ms squarespace.com [65.39.205.54]
Trace complete
Hi Bish
1. Your site is glacial.
2. Reluctant to paste IP address on an open forum
Those instructions don't seem to work, Your Grace. I can find my IP address okay but the Traceroute instructions just take me to Bing as a search result.
The site has been glacial for about a week. Maybe more.
Sorry, not prepared to post that info in a public forum.
I've got the data but like johanna I'm not keen on giving that information to the world in general. Nor, I respectfully submit, should it be necessary. If squarespace have a problem it should be identifiable and correctable without requiring innocent third parties to reveal their IP addresses.
You always have the option of telling Squarespace where to put their hosting. Wordpress do a pretty good job!
The site is working better at the moment. I thought I'd try the VPN and that seems to have made a difference. Can't see why that should be.
And, the site is still trying post my last comment 15 minutes later. "Transferring data from www.bishop-hill.net"
Other UK sites, and some in Canada, the US and New Zealand, are working fine.
I'm with johanna on that but I'll email the guy if it helps solve the problem because it's been painfull here at times, but variable.
This is what I'll let you have for now,
City:
Poitiers
State/Region:
Poitou-Charentes
Country Code:
FR
Postal Code:
86910
ISP:
Orange S.A.
Time Zone:
+02:00 UTC/GMT
Latitude:
46.5833
Longitude:
0.3333
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
ping www.bishop-hill.net
Pinging five.squarespace.com [198.185.159.136] with 32 bytes of data:
Reply from 198.185.159.136: bytes=32 time=169ms TTL=244
Reply from 198.185.159.136: bytes=32 time=152ms TTL=244
Reply from 198.185.159.136: bytes=32 time=154ms TTL=244
Reply from 198.185.159.136: bytes=32 time=170ms TTL=244
Ping statistics for 198.185.159.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 152ms, Maximum = 170ms, Average = 161ms
ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.244.66] with 32 bytes of data:
Reply from 212.58.244.66: bytes=32 time=40ms TTL=49
Reply from 212.58.244.66: bytes=32 time=42ms TTL=49
Reply from 212.58.244.66: bytes=32 time=38ms TTL=49
Reply from 212.58.244.66: bytes=32 time=40ms TTL=49
Ping statistics for 212.58.244.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 42ms, Average = 40ms
Here's a ping session, that's all you get in public...
PING 198.185.159.136 (198.185.159.136): 56 data bytes
64 bytes from 198.185.159.136: icmp_seq=0 ttl=240 time=159.458 ms
64 bytes from 198.185.159.136: icmp_seq=1 ttl=240 time=222.747 ms
64 bytes from 198.185.159.136: icmp_seq=2 ttl=240 time=119.738 ms
64 bytes from 198.185.159.136: icmp_seq=3 ttl=240 time=233.792 ms
64 bytes from 198.185.159.136: icmp_seq=4 ttl=240 time=219.147 ms
64 bytes from 198.185.159.136: icmp_seq=5 ttl=240 time=108.902 ms
64 bytes from 198.185.159.136: icmp_seq=6 ttl=239 time=141.115 ms
64 bytes from 198.185.159.136: icmp_seq=7 ttl=239 time=251.140 ms
64 bytes from 198.185.159.136: icmp_seq=8 ttl=240 time=121.764 ms
64 bytes from 198.185.159.136: icmp_seq=9 ttl=240 time=183.615 ms
64 bytes from 198.185.159.136: icmp_seq=10 ttl=240 time=692.187 ms
64 bytes from 198.185.159.136: icmp_seq=11 ttl=240 time=109.042 ms
64 bytes from 198.185.159.136: icmp_seq=12 ttl=240 time=127.189 ms
64 bytes from 198.185.159.136: icmp_seq=13 ttl=240 time=109.299 ms
64 bytes from 198.185.159.136: icmp_seq=14 ttl=240 time=115.159 ms
64 bytes from 198.185.159.136: icmp_seq=15 ttl=240 time=881.964 ms
64 bytes from 198.185.159.136: icmp_seq=16 ttl=240 time=172.121 ms
64 bytes from 198.185.159.136: icmp_seq=17 ttl=240 time=590.127 ms
64 bytes from 198.185.159.136: icmp_seq=18 ttl=240 time=650.998 ms
64 bytes from 198.185.159.136: icmp_seq=19 ttl=240 time=445.561 ms
64 bytes from 198.185.159.136: icmp_seq=20 ttl=240 time=417.810 ms
64 bytes from 198.185.159.136: icmp_seq=21 ttl=240 time=303.787 ms
64 bytes from 198.185.159.136: icmp_seq=22 ttl=240 time=112.762 ms
64 bytes from 198.185.159.136: icmp_seq=23 ttl=240 time=156.777 ms
Request timeout for icmp_seq 24
64 bytes from 198.185.159.136: icmp_seq=25 ttl=240 time=114.613 ms
Request timeout for icmp_seq 26
64 bytes from 198.185.159.136: icmp_seq=26 ttl=240 time=1006.675 ms
64 bytes from 198.185.159.136: icmp_seq=27 ttl=240 time=287.651 ms
64 bytes from 198.185.159.136: icmp_seq=28 ttl=240 time=668.735 ms
64 bytes from 198.185.159.136: icmp_seq=29 ttl=240 time=848.638 ms
64 bytes from 198.185.159.136: icmp_seq=30 ttl=240 time=212.037 ms
64 bytes from 198.185.159.136: icmp_seq=31 ttl=240 time=225.973 ms
--- 198.185.159.136 ping statistics ---
32 packets transmitted, 31 packets received, 3.1% packet loss
round-trip min/avg/max/stddev = 108.902/322.920/1006.675/259.661 ms
Being with BT, I just restart the HUB and my IP changes.
Working OK for me now.
Fine for me.
Tracing route to bishop-hill.net [65.39.205.54]
over a maximum of 30 hops:
1 3 ms 1 ms <1 ms homeportal [192.168.1.254]
2 4 ms 26 ms 24 ms host81-134-112-1.in-addr.btopenworld.com [81.134.112.1]
3 24 ms 21 ms 22 ms 213.120.182.141
4 26 ms 22 ms 26 ms 213.120.161.82
5 28 ms 23 ms 22 ms 31.55.164.49
6 31 ms 22 ms 24 ms 31.55.164.107
7 33 ms 31 ms 31 ms 109.159.248.77
8 35 ms 29 ms 30 ms core2-te0-15-0-17.ilford.ukcore.bt.net [109.159.248.42]
9 34 ms 31 ms 29 ms peer1-xe2-1-0.telehouse.ukcore.bt.net [109.159.254.136]
10 33 ms 36 ms 34 ms 10ge.xe-0-0-0.linxb.ldn-teleh-dis-1.peer1.net [195.66.224.156]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 104 ms 104 ms 102 ms 69.90.122.29
15 119 ms 117 ms 113 ms squarespace.com [65.39.205.54]
I do not like to post my IP address. I am not on a domain.
My ISP is: Koninklijke KPN N.V.
I apologize for the fact that columns in my post are not preserved on the website.
Response from Bishop Hill takes minutes. Login does not work at all. This is a stable situation.
Trace to 65.39.205.54
Hop Time Time Time Host IP
1 0.674 0.662 0.904 72.55.191.34 72.55.191.34
2 0.902 0.904 0.904 te8-2.cr3.mtl.iweb.com 67.205.127.94
3 0.887 0.884 0.879 po22.cr1.mtl.iweb.com 184.107.1.1
4 0.877 0.873 0.869 ae0.cr6.mtl.iweb.com 184.107.1.62
5 8.224 8.21 8.216 ae0.er1.tor.iweb.com 67.205.127.122
6 11.191 8.084 8.07 xe-3-0-0.torix.tor-151f-cor-1.peer1.net 206.108.34.159
7 22.04 22.037 22.032 10ge.xe-0-3-0.nyc-telx-dis-1.peer1.net 216.187.114.194
8 20.01 20.027 17.932 10ge.ten1-3.nyc-75bre-dis-2.peer1.net 216.187.115.166
Trace to five.squarespace.com
Hop Time Time Time Host IP
1 0.48 174.142.32.131 174.142.32.131
2 0.435 0.724 0.737 te8-3.cr3.mtl.iweb.com 1 84.107.1.33
3 0.719 0.72 0.718 ix-6-0.tcore1.W6C-Montreal.as6453.net 66.198.96.57
4 22.548 22.54 22.539 if-5-2.tcore1.MTT-Montreal.as6453.net 64.86.31.5
5 23.01 23.025 23.025 if-0-2.tcore2.MTT-Montreal.as6453.net 216.6.115.90
6 22.491 22.361 22.369 if-5-2.tcore2.NYY-New-York.as6453.net 216.6.99.29
7 22.554 27.846 27.857 if-4-4.tcore2.NJY-Newark.as6453.net 66.198.111.17
8 22.858 22.871 22.668 if-11-2.tcore2.AEQ-Ashburn.as6453.net 216.6.87.137
9 22.63 22.644 22.646 if-2-2.tcore1.AEQ-Ashburn.as6453.net 216.6.87.2
Everything's been fine today, until I opened this post. I've been to Climate Audit, Lucia's and I'm now at Judith's in the time it took to login.
Sorry. Not going to post personal information.
I could send a screenshot of my Powershell tracert outputs, byt I do not know how to do that on the website.
These outputs are more illuminating than the traceroutes I provided in my previous post. I used a web tool for this, but they do not show the same amount of hops I get from Windows Powershell tracert.
I notice the adverts come up instantly..!
I'm on Linux here Bish,
Hope this helps, my traceroute output followed by 5 pings.
Output from mtr, My traceroute [v0.83]
AXXX (0.0.0.0) Packets Pings
Host Loss% Sent Last Avg Best Wrst StDev
1. 173.23.227.1 0.0% 11 105.1 101.2 84.6 145.6 19.8
2. 173.30.146.163 0.0% 11 103.8 92.3 84.3 114.3 10.4
3. 193.71.255.38 0.0% 11 103.2 98.2 84.4 129.4 12.5
4. 188.31.255.89 0.0% 11 99.6 102.3 80.3 149.7 18.2
5. ae4.man11.ip4.gtt.net 0.0% 11 98.0 95.4 85.1 115.5 8.9
6. xe-8-2-1.nyc20.ip4.gtt.net 0.0% 11 174.7 163.9 148.7 178.7 11.1
7. peer1-gw.ip4.gtt.net 0.0% 10 163.8 160.9 152.2 172.5 6.3
8. ???
9. 69.90.122.29 0.0% 10 160.9 154.6 149.4 163.6 5.1
10. squarespace.com 0.0% 10 178.4 165.4 151.7 188.5 11.8
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Format is messed up but info is OK. I don't know what happen at 8, is that a firewall?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[tom@**:***:*** ~]$ ping 65.39.205.54
PING 65.39.205.54 (65.39.205.54) 56(84) bytes of data.
64 bytes from 65.39.205.54: icmp_req=1 ttl=243 time=1207 ms
64 bytes from 65.39.205.54: icmp_req=2 ttl=243 time=307 ms
64 bytes from 65.39.205.54: icmp_req=3 ttl=243 time=158 ms
64 bytes from 65.39.205.54: icmp_req=4 ttl=243 time=144 ms
64 bytes from 65.39.205.54: icmp_req=5 ttl=243 time=154 ms
--- 65.39.205.54 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 144.719/394.741/1207.986/411.055 ms, pipe 2
Tracert of www.bishop-hill.net
Tracert of bishophill.squarespace.com performs likewise.
Tracert of five.squarespace.com performs likewise.
Tracert of 65.39.205.54 shows now sign of prolexic.com but does take ages.
No hop to prolexic.com in the last tracert. Prolexic protect websites from distributed denial of service attacks. Might this be what is happening? Or something about many of our IP addresses makes it look like a DDoS attack to Prolexic?
I find it inconceivable that Squarespace would need this information from a client's visitors. I think you may have ended up getting the midnight cleaning staff when you contacted their help line. Their log files should tell them where their bottlenecks are. If they don't know how to read their own logs, they should stick to hosting Tupperware parties. It's time for a move. Consider Wordpress.
Since none of the IPs are mine, I have no problem:
Tracing route to bishophill.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms BTHUB4 [192.168.1.254]
2 10 ms 9 ms 9 ms 217.32.147.104
3 9 ms 9 ms 12 ms 217.32.147.158
4 14 ms 13 ms 13 ms 212.140.206.82
5 14 ms 14 ms 14 ms 213.120.180.175
6 14 ms 14 ms 14 ms 217.41.169.109
7 13 ms 13 ms 25 ms acc2-xe-2-1-3.sf.21cn-ipp.bt.net [109.159.255.22
7]
8 18 ms 22 ms 19 ms core1-te0-0-0-4.ealing.ukcore.bt.net [109.159.25
1.25]
9 19 ms 21 ms 20 ms peer1-xe3-2-0.telehouse.ukcore.bt.net [109.159.2
54.205]
10 21 ms 21 ms 24 ms blackhole.prolexic.com [195.66.224.31]
11 23 ms 24 ms 24 ms unknown.prolexic.com [72.52.60.35]
12 * * * Request timed out.
13 113 ms 114 ms 113 ms unknown.prolexic.com [209.200.169.222]
14 97 ms 100 ms 97 ms 198.185.159.136
Trace complete.
Tracing route to five.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms BTHUB4 [192.168.1.254]
2 9 ms 9 ms 9 ms 217.32.147.104
3 24 ms 9 ms 9 ms 217.32.147.158
4 14 ms 13 ms 13 ms 212.140.206.82
5 13 ms 13 ms 14 ms 213.120.180.175
6 14 ms 15 ms 14 ms 217.41.169.109
7 13 ms 13 ms 13 ms acc2-10gige-3-2-0.sf.21cn-ipp.bt.net [109.159.25
1.217]
8 24 ms 18 ms 26 ms core1-te0-4-0-2.ilford.ukcore.bt.net [109.159.25
1.129]
9 21 ms 23 ms 21 ms peer1-xe3-2-0.telehouse.ukcore.bt.net [109.159.2
54.205]
10 22 ms 21 ms 22 ms blackhole.prolexic.com [195.66.224.31]
11 24 ms 24 ms 24 ms unknown.prolexic.com [72.52.60.35]
12 * * * Request timed out.
13 * 116 ms 116 ms unknown.prolexic.com [209.200.169.222]
14 98 ms 98 ms 97 ms 198.185.159.136
Trace complete.
C:\Users\svs.RCL>tracert 65.39.205.54
Tracing route to squarespace.com [65.39.205.54]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms BTHUB4 [192.168.1.254]
2 9 ms 9 ms 9 ms 217.32.147.104
3 9 ms 9 ms 9 ms 217.32.147.158
4 13 ms 13 ms 13 ms 212.140.206.82
5 14 ms 13 ms 13 ms 213.120.180.175
6 13 ms 14 ms 13 ms 217.41.169.109
7 13 ms 13 ms 13 ms acc2-xe-5-1-2.sf.21cn-ipp.bt.net [109.159.251.24
3]
8 27 ms 26 ms 26 ms core1-te0-0-0-6.ilford.ukcore.bt.net [109.159.25
1.157]
9 20 ms 24 ms 21 ms peer1-xe0-1-0.telehouse.ukcore.bt.net [109.159.2
54.132]
10 21 ms 21 ms 22 ms 10ge.xe-0-0-0.linxb.ldn-teleh-dis-1.peer1.net [1
95.66.224.156]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 96 ms 96 ms 96 ms 69.90.122.29
15 92 ms 94 ms 94 ms squarespace.com [65.39.205.54]
Trace complete.
Pretty similar to the others.
Cheers -
Simon
They did ask for your IP as well which is what made me wary.
tracert www.bishop-hill.net
Tracing route to five.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 3 ms 1 ms 3 ms BTBusinessHub.home [EDIT]
2 138 ms 21 ms 24 ms 217.32.142.110
3 23 ms 22 ms 22 ms 217.32.142.158
4 27 ms 27 ms 28 ms 212.140.206.10
5 29 ms 27 ms 28 ms 31.55.165.93
6 29 ms 27 ms 28 ms 31.55.165.107
7 28 ms 27 ms 28 ms acc1-10GigE-1-3-0.mr.21cn-ipp.bt.net [109.159.250.86]
8 35 ms 34 ms 35 ms core1-te0-5-0-1.ealing.ukcore.bt.net [109.159.250.20]
9 35 ms 36 ms 35 ms peer1-xe3-1-1.telehouse.ukcore.bt.net [109.159.254.217]
10 40 ms 37 ms 38 ms blackhole.prolexic.com [195.66.224.31]
11 38 ms 37 ms 37 ms unknown.prolexic.com [72.52.60.35]
12 * * * Request timed out.
13 120 ms 119 ms 118 ms unknown.prolexic.com [209.200.169.222]
14 128 ms 130 ms 128 ms 198.185.159.136
Trace complete.
tracert five.squarespace.com
Tracing route to five.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms BTBusinessHub.home [EDIT]
2 27 ms 22 ms 22 ms 217.32.142.110
3 22 ms 22 ms 21 ms 217.32.142.158
4 31 ms 28 ms 28 ms 212.140.206.10
5 29 ms 27 ms 28 ms 31.55.165.93
6 30 ms 28 ms 28 ms 31.55.165.107
7 29 ms 27 ms 29 ms acc1-10GigE-1-2-0.mr.21cn-ipp.bt.net [109.159.250.70]
8 37 ms 36 ms 39 ms core2-te0-13-0-16.ilford.ukcore.bt.net [109.159.250.38]
9 35 ms 35 ms 35 ms peer1-xe3-1-1.telehouse.ukcore.bt.net [109.159.254.217]
10 37 ms 37 ms 37 ms blackhole.prolexic.com [195.66.224.31]
11 37 ms 36 ms 38 ms unknown.prolexic.com [72.52.60.35]
12 * * * Request timed out.
13 117 ms 120 ms 118 ms unknown.prolexic.com [209.200.169.222]
14 128 ms 128 ms 128 ms 198.185.159.136
Trace complete.
tracert 65.39.205.54
Tracing route to squarespace.com [65.39.205.54]
over a maximum of 30 hops:
1 4 ms 1 ms 1 ms BTBusinessHub.home [EDIT]
2 22 ms 21 ms 21 ms 217.32.142.110
3 89 ms 22 ms 22 ms 217.32.142.158
4 28 ms 28 ms 28 ms 212.140.206.2
5 28 ms 28 ms 28 ms 31.55.165.93
6 28 ms 28 ms 28 ms 31.55.165.107
7 29 ms 28 ms 28 ms acc1-10GigE-0-2-0.mr.21cn-ipp.bt.net [109.159.250.66]
8 41 ms 39 ms 38 ms 109.159.250.19
9 37 ms 34 ms 35 ms peer1-xe0-1-0.telehouse.ukcore.bt.net [109.159.254.132]
10 39 ms 38 ms 40 ms 10ge.xe-0-0-0.linxb.ldn-teleh-dis-1.peer1.net [195.66.224.156]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 143 ms 129 ms 124 ms 69.90.122.29
15 120 ms 118 ms 118 ms squarespace.com [65.39.205.54]
Trace complete.
Rob-26: No more to add - disgraceful!
Enjoyed the 'hosting Tupperware parties'!
Took me a number of minutes to get this far.
On a lighter note, and since this is about IT infrastructure it may even be on topic, Hack yourself. An IIRC conversation where an aggressive newbie is lured into attacking his own machine. 127.0.0.1 is known as the loopback address and always points to the local machine...
Identifying IP blanked for security.
traceroute to free.fr (212.27.48.10), 30 hops max, 38 byte packets
1 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 0 ms 0 ms 0 ms
2 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 30 ms 30 ms 20 ms
3 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 30 ms 30 ms 30 ms
4 perpignan-49m-1-v802.intf.routers.proxad.net (212.27.51.130) 30 ms 30 ms 30 ms
5 narbonne-49m-1-v900.intf.routers.proxad.net (212.27.59.65) 30 ms 30 ms 30 ms
6 poilhes-49m-1-v910.intf.routers.proxad.net (212.27.58.69) 30 ms 30 ms 30 ms
7 montpellier-crs8-2-be1000.intf.routers.proxad.net (78.254.249.33) 30 ms 30 ms 30 ms
8 p11-cr16-1-be1103.intf.routers.proxad.net (194.149.160.21) 40 ms 40 ms 50 ms
9 bzn-crs16-2-be2000.intf.routers.proxad.net (78.254.250.125) 40 ms 40 ms 50 ms
10 bzn-crs16-1-be1106.intf.routers.proxad.net (212.27.59.101) 40 ms 40 ms 40 ms
11 bzn-6k-sys-po20.intf.routers.proxad.net (212.27.51.70) 40 ms 40 ms 40 ms
12 www.free.fr (212.27.48.10) 40 ms 40 ms 40 ms
traceroute to five.squarespace.com (198.185.159.136), 30 hops max, 38 byte packets
1 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 0 ms 0 ms 0 ms
2 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 30 ms 30 ms 20 ms
3 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 30 ms 30 ms 30 ms
4 perpignan-49m-1-v802.intf.routers.proxad.net (212.27.51.130) 20 ms 30 ms 40 ms
5 narbonne-49m-1-v900.intf.routers.proxad.net (212.27.59.65) 30 ms 30 ms 30 ms
6 poilhes-49m-1-v910.intf.routers.proxad.net (212.27.58.69) 30 ms 30 ms 30 ms
7 montpellier-crs8-2-be1000.intf.routers.proxad.net (78.254.249.33) 30 ms 30 ms 30 ms
8 p11-cr16-1-be1103.intf.routers.proxad.net (194.149.160.21) 40 ms 40 ms 40 ms
9 th2-9k-1-be1001.intf.routers.proxad.net (78.254.249.6) 40 ms 40 ms 40 ms
10 ae56.edge4.Paris1.Level3.net (213.242.111.209) 40 ms 50 ms 40 ms
11 vlan90.csw4.Paris1.Level3.net (4.69.168.254) 50 ms 50 ms ae-60-60.csw1.Paris1.Level3.net (4.69.168.62) 50 ms
12 * * *
13 ae-47-47.ebr1.Frankfurt1.Level3.net (4.69.143.141) 50 ms ae-46-46.ebr1.Frankfurt1.Level3.net (4.69.143.137) 50 ms ae-48-48.ebr1.Frankfurt1.Level3.net (4.69.143.145) 70 ms
14 ae-81-81.csw3.Frankfurt1.Level3.net (4.69.140.10) 50 ms ae-71-71.csw2.Frankfurt1.Level3.net (4.69.140.6) 60 ms 60 ms
15 ae-3-80.ear1.Frankfurt1.Level3.net (4.69.154.148) 40 ms ae-4-90.ear1.Frankfurt1.Level3.net (4.69.154.212) 50 ms ae-3-80.ear1.Frankfurt1.Level3.net (4.69.154.148) 40 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
traceroute to 65.39.205.54 (65.39.205.54), 30 hops max, 38 byte packets
1 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 0 ms 0 ms 0 ms
2 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 30 ms 30 ms 20 ms
3 xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 30 ms 30 ms 30 ms
4 perpignan-49m-1-v802.intf.routers.proxad.net (212.27.51.130) 20 ms 30 ms 30 ms
5 narbonne-49m-1-v900.intf.routers.proxad.net (212.27.59.65) 30 ms 20 ms 30 ms
6 poilhes-49m-1-v910.intf.routers.proxad.net (212.27.58.69) 30 ms 30 ms 30 ms
7 montpellier-crs8-2-be1000.intf.routers.proxad.net (78.254.249.33) 30 ms 30 ms 30 ms
8 p11-cr16-1-be1103.intf.routers.proxad.net (194.149.160.21) 40 ms 50 ms 50 ms
9 bzn-9k-4-be1004.intf.routers.proxad.net (78.254.249.2) 40 ms 40 ms 50 ms
10 yankee-6k-1.po2.intf.routers.proxad.net (212.27.58.26) 120 ms 120 ms 130 ms
11 equinixexchange.peer1.net (206.126.236.30) 120 ms 120 ms 120 ms
12 10ge.xe-3-1-0.wdc-sp225-sbcor-2.peer1.net (216.187.115.234) 130 ms 120 ms 130 ms
13 10ge.xe-1-0-0.nyc-telx-dis-1.peer1.net (216.187.115.221) 130 ms 130 ms 130 ms
14 10ge.ten1-3.nyc-75bre-dis-2.peer1.net (216.187.115.166) 130 ms 130 ms 130 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
@Mike Jackson - you're right I didn't notice that (NEVER read the instructions carefully!). Looks like its not needed anyway: the problem appears to be a bit further upstream.
Cheers -
The generic www.squarespace.com site works OK (with all the template demos) and this is on a different IP to BH, leading me to think it is a server=specific problem
All this tracert stuff looks highly suspect to me
And I thought it was Virginmedia...here in W. Mids they have total disruptions per 2 to 3 days for 3 hrs (7am thru 11am), for last 6 weeks. Help from India....no chance!
Its out of VM and down a blackhole.prolexic.com
The weird thing is not everyone has a problem.
Trying again with tracert via Powershell
Tracing route to five.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms sitecomwlr5001.sitecomwlr5001 [192.168.0.1]
2 27 ms 99 ms 99 ms 192.168.1.254
3 16 ms 15 ms 16 ms 195.190.228.7
4 19 ms 19 ms 19 ms nl-asd-dc2-git-cr03.kpn.net [213.75.1.81]
5 26 ms 23 ms 23 ms nl-asd-dc2-ice-ir02.kpn.net [213.75.1.80]
6 21 ms 23 ms 23 ms nl-asd-dc2-ice-ir01.kpn.net [213.75.1.146]
7 18 ms 17 ms 17 ms asd2-rou-1022.NL.eurorings.net [134.222.93.138]
8 17 ms 18 ms 18 ms asd2-rou-1043.NL.eurorings.net [134.222.229.101]
9 18 ms 18 ms 18 ms ae9.edge3.Amsterdam1.level3.net [213.244.164.205]
10 25 ms 26 ms 25 ms vl-3511-ve-125.csw1.Amsterdam1.Level3.net [4.69.162.169]
11 25 ms 25 ms 25 ms ae-59-114.ebr1.Amsterdam1.Level3.net [4.69.153.197]
12 24 ms 24 ms 25 ms ae-45-45.ebr2.Dusseldorf1.Level3.net [4.69.143.198]
13 25 ms 25 ms 25 ms ae-21-21.ebr1.Dusseldorf1.Level3.net [4.69.143.181]
14 25 ms 25 ms 25 ms ae-46-46.ebr3.Frankfurt1.Level3.net [4.69.143.170]
15 25 ms 24 ms 24 ms ae-93-93.csw4.Frankfurt1.Level3.net [4.69.163.14]
16 * * 25 ms ae-4-90.ear1.Frankfurt1.Level3.net [4.69.154.212]
17 26 ms 25 ms 26 ms unknown.Level3.net [212.162.40.138]
18 26 ms 25 ms 25 ms unknown.prolexic.com [72.52.48.35]
19 * * * Request timed out.
20 111 ms 116 ms 111 ms unknown.prolexic.com [209.200.168.148]
21 111 ms 110 ms 111 ms 198.185.159.136
Trace complete.
Tracing route to squarespace.com [65.39.205.54]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms sitecomwlr5001.sitecomwlr5001 [192.168.0.1]
2 81 ms 99 ms 99 ms 192.168.1.254
3 16 ms 16 ms 16 ms 195.190.228.7
4 18 ms 19 ms 19 ms nl-asd-dc2-git-cr03.kpn.net [213.75.1.81]
5 18 ms 23 ms 23 ms nl-asd-dc2-ice-ir02.kpn.net [213.75.1.80]
6 27 ms 23 ms 23 ms nl-asd-dc2-ice-ir01.kpn.net [213.75.1.146]
7 18 ms 18 ms 18 ms asd2-rou-1022.NL.eurorings.net [134.222.93.138]
8 18 ms 18 ms 18 ms asd2-rou-1043.NL.eurorings.net [134.222.225.194]
9 18 ms 18 ms 18 ms ae9.edge3.Amsterdam1.level3.net [213.244.164.205]
10 99 ms 99 ms 99 ms vl-3611-ve-235.csw2.Amsterdam1.Level3.net [4.69.162.217]
11 99 ms 99 ms 96 ms ae-58-223.ebr2.Amsterdam1.Level3.net [4.69.153.209]
12 97 ms 97 ms 97 ms ae-48-48.ebr2.London1.Level3.net [4.69.143.82]
13 97 ms 97 ms 97 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]
14 98 ms 97 ms 98 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
15 97 ms 96 ms 97 ms ae-2-70.edge1.NewYork1.Level3.net [4.69.155.78]
16 * * * Request timed out.
17 104 ms 104 ms 104 ms 69.90.122.29
18 98 ms 97 ms 97 ms squarespace.com [65.39.205.54]
Trace complete.
Not prepared to post IP etc in public forum but for what it is worth my ISP is Telus in Calgary, Alberta, Canada and glacial is a good description
The problem seems to have gone away for the moment so I can't post anything useful.
Thanks @Simon Aug 6, 2014 at 1:59 PM, that story is awesome!
Very slow at the moment in Normandy
in five minutes all your hard drives is deleted
I have a BT 40Mb internet connection. Click on Met Office or Amazon and the page comes up instantly (less than one second). Bishophill home page takes 30 seconds to load. Clicking to see comments takes a further 34 seconds. I offer this non technical observation as a measure of "glacial"!
Interesting that while I've got this page up the little green wheel is still quietly going round apparently still loading data from twitter.
Everything else on the page finished loading about five minutes ago!
There's a message there somewhere — and not just in 140 characters!
Chris Long posted a nice tip - page 2 of the Discussion thread - on using FF 'developer tools'.
In my case it seems the images in the right panel are "corrupt or truncated"
http://i22.photobucket.com/albums/b331/kevster1346/bishop1_zpsf0e81f29.png
http://i22.photobucket.com/albums/b331/kevster1346/bishop2_zpsfd1b574c.jpg
Still slow at 15.30 hours mountain time. Given that you have visitors from around the world, all seemingly seeing the same very slow load, does not that suggest that the issue rests within the squarespace world itself and not the route taken to reach their servers?
Response of BH blog in my case in Australia. Glacial for the last 2 weeks. Have the impression that mouse actions while waiting the typical half minute each time for a new window to open, can speed progress. Like opening another address while waiting for BH. Once BH opens to the stage of showing reader comments, pace returns to normal. So the prob seems to be in navigation by the system to finally arrive at the correct IP.
(Can do a trace later if that would help. Need to be sitting at my PC when free, not tablet.)
Much slower than a wet week. Took 45 minutes to enter and edit one post today.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
108.180.183.45
Tracing route to www.bishophill.squarespace.com [198.185.159.136]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.1.254
2 12 ms 14 ms 20 ms 10.31.180.1
3 14 ms 14 ms 15 ms STTLWAWBCI01.bb.telus.com [75.154.217.108]
4 14 ms 15 ms 15 ms ix-1-2-3-0.tcore1.00S-Seattle.as6453.net [64.86.
123.117]
5 34 ms 36 ms 35 ms if-14-2.tcore1.PDI-Palo-Alto.as6453.net [64.86.1
23.22]
6 * 34 ms 34 ms if-2-2.tcore2.PDI-Palo-Alto.as6453.net [66.198.1
27.2]
7 35 ms 35 ms 36 ms if-5-2.tcore2.SQN-San-Jose.as6453.net [64.86.21.
1]
8 35 ms 35 ms 36 ms if-1-2.tcore1.SQN-San-Jose.as6453.net [63.243.20
5.1]
9 34 ms 36 ms 35 ms 63.243.205.62
10 36 ms 35 ms 36 ms 209.200.184.41
11 36 ms 36 ms 36 ms 209.200.184.164
12 98 ms 98 ms 97 ms unknown.prolexic.com [72.52.43.164]
13 97 ms 97 ms 98 ms 198.185.159.136
Trace complete.
Andrew, the blog is pretty much unusable on my mobile devices Galaxy S4, iPad and now my PC. Example it's taken about 60 secs to load this page.
Don't put up with this trace route bull**** from Sqaurespace. If the problems are across the board it's nothing to do with the users.
If they can't sort it quick, change hosting.
I have drastically reduced my visits to BishopHill as it's unusable at the current performance levels. This is a SERIOUS problem for you.
When I re-booted my BT Hub, (to obtain a new IP address because I had shown the problematic IP address), my access has been as I would expect.
If anyone has the glacial-effect, and has a BT connection that is not a business type (they seem to have static IP's) then at some point try re-booting the Hub, (thus obtaining a different IP address), and see how that goes.
Earlier today when I posted my (then) IP address I was 'glacial', after posting I rebooted to get another IP address and things went swimmingly, from my point of view.
Maybe 'stay-dynamic' is the way to go?
How many people are NOT having a problem and is there a commonality amongst us?
Try loading this image
http://bishophill.squarespace.com/picture/htdslide.png?pictureId=19181106
Once it starts loading click to stop it.
Do you get a "because it contains errors" message?
Yes but it happens with any image you stop mid load
"Yes but it happens with any image you stop mid load"
In what universe?
I put my technical architect hat on for a moment and took a slightly different approach, as I'm used to tech support asking for (possibly pointless) trace routes. ;-)
If you use Chrome and enable the Developer toolbar, there's a network tab where you can see the load times for each individual page asset when (re)loading a Bishop Hill page. From what I can see, the actual page loads pretty quickly, but any asset in /universal/scripts seems to be taking tens of seconds to load.
Given the directory name (universal), are those common scripts provided by Squarespace? If so, is there a problem with their hosting platform? If those scripts are cross-mounted using SMB, for example, then the problem might be between the web server and the file server.
Hope this helps! :-)
Throg
Sounds interesting to me - I'll point it out to Squarespace.
Many thanks
Many years experience in IT Support showed me that at least 90% of problems are caused by changes.
When was the first problem noticed/reported? What changes, hardware or software, had just been implemented?