Problems accessing our service?

Time-outs on some networks but not others, such as failing at work, but successfully connecting via VPN, or a cell network?

Typical Causes

Some local networks use overly aggressive policing or filtering - making the internet difficult to access and use.
Or it may be accidental and the local provider simply has a VPN/firewall misconfiguration.
If you use custom domains it is possible your particular DNS service doesn't play well with all internet providers.
Request help from the internet provider, who is failing to "provide" proper functionality of basic HTTP services.

Solving Network Issues

What value are you using for timeout? We advise using 15-30 seconds. 15s should be enough for almost all API responses. Otherwise, you should see our server respond with a 503 error code (30s is a worst-case scenario for severe networking lag).

One method of locating the problem network is by tracing the route. This traces the route of packets to a destination host.
Compare output of times with a "good" connection to tinycc.com and output of times when connection to tinycc.com breaks down or times out. Depending on your OS, there are different command-line tools to pick from:
tracert
traceroute
tracepath

Sometimes complex AWS setups can result in rather long routes to our servers and IP-packet losses.

To reduce the rate of IP-packet loss We suggest decreasing the MTU parameter of the network interface of your server. In many cases MTU=1500 by default. But for long routes it may be feasible to set it in the area of 1200-1400. Of course after this change, network connections should be re-tested. We expect it will give better reliability of access to tinycc.com. Possible negative effect - somewhat reduced bandwidth of network interface (because of increased IP-packet headers overhead).

A way of testing different MTU parameter values:
ping -M do tinycc.com -s
- should be set at 1500 initially (this is where you have experienced failure). Next values to try 1480, 1460 etc. Until ping succeeds.

Basic Commands and Tools

Run this command on your server with bad connections:
mtr -w -c 1000 -s 1000 -r tinycc.com
It will work for about 17 minutes and provide a report about lost IP-packets. It lets you see which host in the route loses IP-packets.

Run cURL with "v" key to get more info, Like this:
curl -Iv --connect-timeout 10 https://tinycc.com

Where cURL fails run curl ifconfig.me