Pingingwww.sailwave.com[188.8.131.52] with 32 bytes of data: Reply from 184.108.40.206: bytes=32 time=23ms TTL=244 Reply from 220.127.116.11: bytes=32 time=25ms TTL=244 Reply from 18.104.22.168: bytes=32 time=20ms TTL=244 Reply from 22.214.171.124: bytes=32 time=21ms TTL=244
Ping statistics for 126.96.36.199: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 25ms, Average = 22ms
Sorry @sykesk01 / Jen_A as it is likely I am responsible for this confusion with my initial posts where I mistakenly wrote about website access.
@Jen_A, nslookup sailwave.com confirms the observation made by sykesk01 that Web Safe is blocking access by resolving the address to 188.8.131.52 (know-sspiprxy-vip.network.virginmedia.net). FYI, HTTP / HTTPS traffic is proxied onward by Web Safe to 184.108.40.206 (sailwave.com) but FTP traffic is not; hence the website server is accessible but not the ftp server.