First, let me preface this that it may not be a Storj issue at all, however I’m a bit unsure how to debug this.
One of the users of my app is reporting very slow file uploads. They’re on a 500/500 connection so uploads should be very quick, however, they’re reporting speeds which are about twice as long as what it’s taking my 50/20 connection to make.
I asked the user for traceroute to the gateway and they’ve come back with:
1 <1 ms <1 ms <1 ms 2a02:6b67:64a3:0:daec:5eff:fe7d:c9f
2 2 ms 2 ms 2 ms 2a02:6b60:0:1
3 2 ms 2 ms * lag-7.acc1.thu.lon.network.as201838.net [2a02:6b60:0:1:4::13]
4 3 ms 2 ms 2 ms xge-0-2-1.acc1.ld8.lon.network.as201838.net [2a02:6b60:0:1:1::72]
5 2 ms 2 ms * lag-4.agg-rr1.avo.lon.cisco.network.as201838.net [2a02:6b60:0:1:1::229]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 69 ms 69 ms 69 ms 100ge4-1.core1.nyc4.he.net [2001:470:0:2cf::2]
10 * * * Request timed out.
11 78 ms 79 ms 79 ms storj-labs-inc.e0-6.switch1.tor3.he.net [2001:470:1:209::2]
12 78 ms 79 ms 79 ms 2a10:c640:0:1::4
You can see a few dropouts here. They’re based in London and the ISP is CommunityFibre. They mentioned the traceroute taking a long time to run.
I obtained two other traceroutes from users in London, this one on Sky
traceroute: Warning: gateway.storjshare.io has multiple addresses; using 185.244.226.3
traceroute to gateway.storjshare.io (185.244.226.3), 64 hops max, 52 byte packets
1 skyrouter (192.168.0.1) 5.668 ms 5.074 ms 27.939 ms
2 * * *
3 02780b94.bb.sky.com (2.120.11.148) 408.165 ms 13.441 ms 11.024 ms
4 195.66.239.188 (195.66.239.188) 9.614 ms 13.388 ms *
5 e0-36.cr2.lon2.gb.unitasglobal.net (50.115.91.37) 83.266 ms 10.884 ms 9.321 ms
6 e0-15.cr1.fra1.de.unitasglobal.net (50.115.91.200) 22.445 ms 21.415 ms *
7 ae1-3.cr2.fra1.de.unitasglobal.net (50.115.90.105) 21.113 ms 20.702 ms 20.836 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
and this one on plusnet (BT)
traceroute: Warning: gateway.storjshare.io has multiple addresses; using 185.244.226.4
traceroute to gateway.storjshare.io (185.244.226.4), 64 hops max, 52 byte packets
1 dsldevice (192.168.1.254) 2.478 ms 4.105 ms 2.087 ms
2 * * *
3 * * *
4 140.hiper04.sheff.dial.plus.net.uk (195.166.143.140) 7.622 ms
136.hiper04.sheff.dial.plus.net.uk (195.166.143.136) 7.633 ms 7.355 ms
5 peer8-et-7-0-5.telehouse.ukcore.bt.net (62.172.103.178) 7.028 ms
peer8-et-7-0-2.telehouse.ukcore.bt.net (109.159.252.100) 7.707 ms
peer8-et-0-1-7.telehouse.ukcore.bt.net (194.72.16.146) 7.108 ms
6 195.66.239.188 (195.66.239.188) 7.433 ms 8.063 ms
195.66.224.81 (195.66.224.81) 10.993 ms
7 e0-36.cr2.lon2.gb.unitasglobal.net (50.115.91.37) 7.751 ms 8.988 ms
e0-14.cr2.lon1.gb.unitasglobal.net (50.115.90.161) 9.573 ms
8 * e0-15.cr1.fra1.de.unitasglobal.net (50.115.91.200) 22.514 ms 18.324 ms
9 e0-15.cr1.fra1.de.unitasglobal.net (50.115.91.200) 20.114 ms
ae1-3.cr2.fra1.de.unitasglobal.net (50.115.90.105) 19.693 ms
e0-15.cr1.fra1.de.unitasglobal.net (50.115.91.200) 19.996 ms
10 ae1-3.cr2.fra1.de.unitasglobal.net (50.115.90.105) 20.914 ms
storj.cust.fra1.de.unitasglobal.net (45.15.192.34) 18.722 ms
ae1-3.cr2.fra1.de.unitasglobal.net (50.115.90.105) 20.359 ms
11 storj.cust.fra1.de.unitasglobal.net (45.15.192.34) 20.606 ms 19.747 ms 20.375 ms
12 * * *
13 * * *
The latter two don’t seem to have any timeouts (although that’s not 100% indicative of a problem).
Any ideas on what to try next to figure out why the performance is so bad for them? They don’t have any issues with other sites and play a lot of online games so they’d be sensitive to a poor connection.