Page 1 of 1

Wurfl Cloud IP with delayed TCP response

Posted: Tue Oct 11, 2016 6:40 pm
by sofiane.latoui
Hi,

Currently we have in our server an interface connected to Wurfl Cloud IP 50.57.185.227. During tcp handshake we have noticed some response times above 3 min.

1. Could you kindly let us know why is this happening?
2. What should be done in your side to decrease the response times?

If possible, please share an engineer contact so we can do troubleshooting faster and share complete information.

Best regards,

Re: Wurfl Cloud IP with delayed TCP response

Posted: Tue Oct 11, 2016 6:46 pm
by kamermans
Hi,

That is very strange indeed - can you please send us an email at support @ our domain and share with us the IP that you are connecting from? Please note that the IPs can change if we launch instances in other regions, etc, so it is best to connect to `api.wurflcloud.com`. It's possible that you are connecting to a hot-standby load balancer or something like that. We are planning to move most of our WURFL Cloud servers from Rackspace to AWS and possibly our datacenter in the Washington DC area in the coming weeks, so I can probably get you setup on the new infrastructure if you'd like to test that out.

Thanks,

Steve Kamerman
ScientiaMobile, Inc.

Re: Wurfl Cloud IP with delayed TCP response

Posted: Tue Oct 11, 2016 7:05 pm
by sofiane.latoui
Thanks for your prompt reply. Yes we are connected to `api.wurflcloud.com, the IP was obtained through a packet capture.

Please confirm the email is support@scientiamobile.com.

Best regards,

Re: Wurfl Cloud IP with delayed TCP response

Posted: Tue Oct 11, 2016 7:53 pm
by aaronp
Hi!

I can confirm that the email is indeed support@scientiamobile.com

Look forward to hearing from you soon.

Regards,

Aaron