My app stores alot of images. When the app pulls that data any way to make the response to custom endpoints faster?



Would be much appreciated! Thank you!

Hey Tom, Thanks for the traceroute. It looks like connectivity isn't the major issue here. Maybe you can help me break down what you're trying to do a little more so we can help you optimize. My current best guess is that it's some BL code that could use a bit of optimization.



* What version of the iOS library are you using:

* What are you trying to do and which steps are you taking to achieve that? At which step are you seeing the issue?



1. Step 1

2. Step 2

3. ...



* What are you expecting instead:



The [iOS Troubleshooting guide](http://devcenter.kinvey.com/ios/guides/troubleshooting "iOS Troubleshooting guide") may also be a good starting point.

Traceroute has started…



traceroute: Warning: baas.kinvey.com has multiple addresses; using 50.17.218.209

traceroute to kcs-https-1280834909.us-east-1.elb.amazonaws.com (50.17.218.209), 64 hops max, 72 byte packets

1 wireless_broadband_router (192.168.1.1) 1.976 ms 1.364 ms 2.462 ms

2 l300.nycmny-vfttp-163.verizon-gni.net (98.116.12.1) 5.285 ms 3.823 ms 2.803 ms

3 g1-5-3-5.nycmny-lcr-21.verizon-gni.net (130.81.191.168) 7.875 ms 7.672 ms 7.861 ms

4 so-11-0-0-0.ny325-bb-rtr1.verizon-gni.net (130.81.151.222) 6.511 ms 5.144 ms 6.714 ms

5 * * *

6 0.ae1.br3.nyc4.alter.net (140.222.229.97) 10.222 ms 7.724 ms 6.654 ms

7 xe-0-2-0-6.r06.nycmny01.us.bb.gin.ntt.net (129.250.9.77) 6.483 ms 7.646 ms 7.987 ms

8 * * *

9 54.240.229.76 (54.240.229.76) 21.135 ms

54.240.229.80 (54.240.229.80) 19.396 ms 19.439 ms

10 54.240.228.196 (54.240.228.196) 15.689 ms 14.382 ms

54.240.228.200 (54.240.228.200) 19.720 ms

11 54.240.229.223 (54.240.229.223) 15.671 ms 15.541 ms 15.889 ms

12 54.240.229.135 (54.240.229.135) 15.787 ms 15.637 ms *

13 205.251.244.114 (205.251.244.114) 16.711 ms

72.21.220.118 (72.21.220.118) 16.920 ms 15.414 ms

14 72.21.220.167 (72.21.220.167) 40.959 ms 40.208 ms 39.433 ms

15 72.21.222.87 (72.21.222.87) 31.493 ms *

205.251.245.53 (205.251.245.53) 48.503 ms

16 * * *

17 * * *

18 * * *

19 216.182.224.195 (216.182.224.195) 61.681 ms *

216.182.224.91 (216.182.224.91) 44.679 ms

20 * * *

21 * * *

22 * * *

23 * * *

24 * * *

25 * * *

26 * * *

27 * * *

28 * * *



Thank you!

Here’s the steps to do that traceroute (it will probably take a few minutes for the trace to complete):



For Windows:

1) Go to Start (start button on the lower left of the desktop)

2) Choose ‘Run’

3) Type: “cmd” (no quotes)

4) This should bring up a DOS prompt. Once there, type: “tracert baas.kinvey.com” (without quotes and including the subdomain)



For Mac:

1) Open Network Utility from your Utilities folder, select the Traceroute tab, enter “baas.kinvey.com” (without quotes and including your subdomain) and click the trace button.



The result will be text output that show hops from your computer to our server. Copy this output and send it to me. I’ll have our developers take a look and see what’s going on.



Thanks for your help with this!

how do we run a traceroute?

Hi Tom, Where are you seeing the slow down? Have you performed a traceroute to test yet?