Tapestry Speed Test

This page can test how fast your connection to the Tapestry servers is and report any connection errors as best as it can.

It connects in the same way as the iOS, Android and Fire apps so you can use it to try and diagnose connection problems with the apps by using this page on your tablet or phone.

Start the test Email the results to Tapestry customer services

Interpreting the results

The results of this test are likely to vary from generic internet connection speed tests:

• Generic speed tests are typically designed to test the speed of your connection to somewhere nearby on the internet, whereas what matters for using Tapestry is the speed of the connection to our servers which will (for most people) be further away.
• Generic speed tests emphasise download speeds and ping times whereas for Tapestry ping times are fairly irrelevant and upload speeds are equally important as download speeds (because, on any given day, we tend to have as much data uploaded to us as downloaded).

In all cases it will vary by the number of people online at any given moment on your local WiFi, using your internet provider, using the internet in general and using our servers. It is therefore worth running the test at times of day when you would typically use Tapestry.

If you are getting errors:

• If our servers are down then we will tend to report this on our status page at tapestryjournalstatus.com.
• If you have a proxy or connection filter, please check it is configured to allow uploads and downloads to https://tapestryjournal.com.

If your connection is too slow, then the first step is to figure out where the bottleneck is:

• If you are using WiFi try moving right next to the WiFi router or using a wired connection and giving the test another go. If that makes it fast enough, then it is likely that the WiFi is the problem.
• Try taking your tablet, phone or computer somewhere where it can use a different internet connection (e.g., your home; or on a good 4G network if you have a suitable phone). If that makes it fast enough, then it is likely that the ISP is the problem.
• Failing that, you may need to get an IT person to use some more specialist programs (like traceroute) to try and estimate where the bottleneck lies (once you've traced as far as an AWS ip, then you are in our data center)