network problem

Hey there — if you haven't done so already, please open a Support Ticket and we'll be able to check and confirm for potential contributing issues on our end.

After running some of my own diagnostics, I'm not seeing networking issues to that IP from my test Linode in Newark, NJ:

$ ping -c 5 139.162.234.140
PING 139.162.234.140 (139.162.234.140) 56(84) bytes of data.
64 bytes from 139.162.234.140: icmp_seq=1 ttl=60 time=67.5 ms
64 bytes from 139.162.234.140: icmp_seq=2 ttl=60 time=67.6 ms
64 bytes from 139.162.234.140: icmp_seq=3 ttl=60 time=67.5 ms
64 bytes from 139.162.234.140: icmp_seq=4 ttl=60 time=69.2 ms
64 bytes from 139.162.234.140: icmp_seq=5 ttl=60 time=67.5 ms

--- 139.162.234.140 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 10ms
rtt min/avg/max/mdev = 67.485/67.851/69.154/0.692 ms

$ mtr -rwzbc10 139.162.234.140
Start: 2020-03-12T13:27:16-0400
HOST: tester                                              Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. AS8001   router1-nac.linode.com (207.99.1.13)              0.0%    10    0.7   0.8   0.5   1.1   0.2
  2. AS63949  173.255.239.50                                    0.0%    10    1.0   1.0   0.5   4.3   1.1
  3. AS???    213.52.131.207                                    0.0%    10   67.4  71.4  67.4 106.7  12.4
  4. AS63949  109.74.207.31                                     0.0%    10   67.7  68.0  67.7  68.9   0.4
  5. AS63949  li1519-140.members.linode.com (139.162.234.140)   0.0%    10   67.8  67.6  67.4  68.0   0.2

I am, however, seeing filtered ssh and mysql ports:

$ nmap -FPn 139.162.234.140 --reason
Starting Nmap 7.70 ( https://nmap.org ) at 2020-03-12 13:26 EDT
Nmap scan report for li1519-140.members.linode.com (139.162.234.140)
Host is up, received user-set (0.069s latency).
Not shown: 98 closed ports
Reason: 98 conn-refused
PORT     STATE    SERVICE REASON
22/tcp   filtered ssh     no-response
3306/tcp filtered mysql   no-response

Nmap done: 1 IP address (1 host up) scanned in 1.30 seconds

This indicates that a firewall configuration may be related to connection issues.

Otherwise, additional details on your client's location, as well as MTR reports to and from their location, may show routing problems that me be related.