Hi, we are a mobile development team that we have some customers with apps located in Parse. We have been doing some tests with your service and the latency is very slow for each transaction in Spain (2-3 seconds).
Currently, we are developing a new project for a customer with your platform, and we are testing the queries with poor latency.
Please, can you confirm us if there is a solution for this? I guess that the solution is to improve the account to a monthly payment.
Can you explain us how we can improve the latency speed with your service?
Thanks.
Could you try the following two commands and let us know the results?:
ping api.backendless.com
traceroute api.backendless.com
Hi Mark,
Thank your for your answer.
Here you are the results:
Traceroute -> api.backendless.com
traceroute: Warning: api.backendless.com has multiple addresses; using 54.84.253.252
traceroute to horsesrv-225955670.us-east-1.elb.amazonaws.com (54.84.253.252), 64 hops max, 72 byte packets
1 10.0.1.1 (10.0.1.1) 1.613 ms 1.343 ms 1.117 ms
2 192.168.1.1 (192.168.1.1) 3.069 ms 2.071 ms 2.454 ms
3 184.red-80-58-67.staticip.rima-tde.net (80.58.67.184) 31.549 ms 32.380 ms 31.837 ms
4 * * *
5 166.red-80-58-76.staticip.rima-tde.net (80.58.76.166) 60.403 ms 60.281 ms 60.507 ms
6 et5-0-0-400-grtmadad1.net.telefonicaglobalsolutions.com (84.16.11.37) 59.151 ms 73.035 ms 59.399 ms
7 xe10-0-0-0-grtlontc1.net.telefonicaglobalsolutions.com (5.53.7.10) 90.143 ms 107.713 ms 91.269 ms
8 * xe-2-0-1-0-grtnycpt2.net.telefonicaglobalsolutions.com (94.142.126.61) 161.929 ms 162.129 ms
9 ae-11.r07.nycmny01.us.bb.gin.ntt.net (129.250.9.1) 163.053 ms 164.740 ms 163.252 ms
10 ae-8.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.126) 158.916 ms 158.609 ms 159.411 ms
11 * * *
12 * * *
13 54.239.42.184 (54.239.42.184) 171.154 ms 170.371 ms 169.580 ms
14 * * *
15 * * *
16 54.239.110.161 (54.239.110.161) 167.114 ms 163.024 ms 160.157 ms
17 54.239.108.61 (54.239.108.61) 167.368 ms 168.889 ms 167.648 ms
18 72.21.222.149 (72.21.222.149) 162.961 ms 163.723 ms 162.888 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * *
Ping -> api.backendless.com
MacBookProRetina-de-Jose-Miguel-Galvan:~ josemiguelgalvan$ ping api.backendless.com
PING horsesrv-225955670.us-east-1.elb.amazonaws.com (54.84.253.252): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
Request timeout for icmp_seq 46
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
Request timeout for icmp_seq 50
Request timeout for icmp_seq 51
Request timeout for icmp_seq 52
Request timeout for icmp_seq 53
Request timeout for icmp_seq 54
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59
Request timeout for icmp_seq 60
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62
Request timeout for icmp_seq 63
Request timeout for icmp_seq 64
Request timeout for icmp_seq 65
Request timeout for icmp_seq 66
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
Request timeout for icmp_seq 69
Request timeout for icmp_seq 70
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
Request timeout for icmp_seq 73
Request timeout for icmp_seq 74
Request timeout for icmp_seq 75
Request timeout for icmp_seq 76
Request timeout for icmp_seq 77
Request timeout for icmp_seq 78
^C
— horsesrv-225955670.us-east-1.elb.amazonaws.com ping statistics —
80 packets transmitted, 0 packets received, 100.0% packet loss
I think there is an issue with api.backendless.com from Spain, ping results are weird.
Many thanks.
King regards,
Jose
Hi Jose,
I just ran a test for our API endpoint from test machines in Europe. Below are the results. I suspect there must be something with your Internet provider:
http://support.backendless.com/public/attachments/bd1a3a73721b9971a1e970516b12c86b.jpg</img>
You can run the test for “api.backendless.com” yourself using this tool:
https://www.dotcom-tools.com/website-speed-test.aspx
Hi Mark,
Thank you for your response.
I will take a look with my internet provider.
King regards,
Jose
It’s about a second now:
Europe:
http://support.backendless.com/public/attachments/ca0b652c0a47eb028495dd282a6ed2cc.png</img>
Worldwide:
http://support.backendless.com/public/attachments/27b2aec921599ccc5867b0bd319243d0.png</img>
I keep recommending Backendless to my clients (mostly based in the USA), but recently we’re facing the performance issues, so I wonder what could we do on our side.
Thank you for support!
We’ve run into this now today and yesterday here in Finland. It ran quite nice for a while, but now again it’s very slow. I have several users reporting slow response…
What is causing this? It’s not our networks, as they are fast (in Finland) and all other pages load immediatle.
Cheers Juha
Hi Juha,
I just ran a connection test from Brussels and am getting 108 ms response time for api.backendless.com. However, the only guaranteed way to get consistent response time as well as uptime is to get Managed Backendless. If you’re targeting customers in Europe, we offer Managed Backendless in our European data center.
http://support.backendless.com/public/attachments/50d32b1a2f0faf9ed9c72b86f034ca45.jpg</img>
Regards,
Mark
