Works fine from Community Fibre, but it may of been resolved now:

> ping 185.17.24.90

Pinging 185.17.24.90 with 32 bytes of data:
Reply from 185.17.24.90: bytes=32 time=5ms TTL=57
Reply from 185.17.24.90: bytes=32 time=5ms TTL=57
Reply from 185.17.24.90: bytes=32 time=5ms TTL=57
Reply from 185.17.24.90: bytes=32 time=5ms TTL=57

Ping statistics for 185.17.24.90:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 5ms, Average = 5ms

---
Paul

I've not come across community fibre before. I assume they are a part of BT?

Just a suggestion, but is it maybe BT Wholesale NOC you need to contact ?

How you do that, I don’t know.

As I say, just an idea.

Pinging this morning fine through an Entanet connection

That IP leads to a CPanel landing page, there is no site to resolve .......

In reply to a post by AndreiV:

That IP leads to a CPanel landing page, there is no site to resolve .......

That's the expected behaviour. Can you just confirm you are on a BT connection? Sounds like something has happened overnight to resolve the issue.

No, not BT , I am on Trooli.
Pinging that IP earlier this morning saw packet loss due to hops timing out.

Now it is clear.

Works from AAISP.

Reply from 185.17.24.90: bytes=32 time=8ms TTL=59
Reply from 185.17.24.90: bytes=32 time=7ms TTL=59
Reply from 185.17.24.90: bytes=32 time=7ms TTL=59
Reply from 185.17.24.90: bytes=32 time=8ms TTL=59

Given someone has confirmed the BT looking glass can ping it, maybe check with the BT broadband customers if they have the family safe browsing filter enabled or not.

Also

https://www.globalservices.bt.com/en/my-account/serv...

Thats the global operation, but they may offer to pass it on to UK operations or even give contact for UK operations.

Edited by Chrysalis (Sat 27-Apr-24 14:41:53)

I'm using BT's FTTC

Connection: Native BT

PING.
Pinging 185.17.24.90 with 32 bytes of data:
Request timed out.

TRACERT.
C:\>tracert 185.17.24.90

Tracing route to nash.hyliahub.com [185.17.24.90]
over a maximum of 30 hops:

1 3 ms 3 ms 2 ms BTHUB5 [192.168.1.254]
2 8 ms 8 ms 8 ms 172.16.14.86
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C
__________________________________________

Connection via VPN (CyberGhost):

PING.
C:\>ping 185.17.24.90

Pinging 185.17.24.90 with 32 bytes of data:
Reply from 185.17.24.90: bytes=32 time=20ms TTL=58
Reply from 185.17.24.90: bytes=32 time=22ms TTL=58
Reply from 185.17.24.90: bytes=32 time=22ms TTL=58
Reply from 185.17.24.90: bytes=32 time=21ms TTL=58

TRACERT.
C:\>tracert 185.17.24.90

Tracing route to nash.hyliahub.com [185.17.24.90]
over a maximum of 30 hops:

1 15 ms 15 ms 14 ms 10.71.4.1
2 15 ms 15 ms 17 ms ae2-590.cr1-lon1.ip4.gtt.net [92.60.245.189]
3 16 ms 27 ms 23 ms ae22.cr10-lon1.ip4.gtt.net [89.149.185.49]
4 14 ms 15 ms 14 ms ae15-to-GTT.mx0thw.as42831.net [46.33.70.2]
5 22 ms 19 ms 18 ms mx0.cov205-from-mx0.thn2.as42831.net [5.101.143.10]
6 19 ms * 19 ms nash.hyliahub.com [185.17.24.90]

Trace complete.

Reverse IP lookup:

Hostname nash.hyliahub.com ISP UK Dedicated Servers Limited
Continent Europe Flag GB
Country United Kingdom Country Code GB
Region England Local time 27 Apr 2024 16:05 BST
City London Postal Code EC4R
IP Address 185.17.24.90 Latitude 51.509
Longitude -0.093
___________________________________________
<end>

Doesn't work on 2 different BTNet leased lines - neither my EE mobile. Works from my home Gigaclear line though.