BT blocking access to IP address

I work for a small web hosting company and have come across a funky issue that only impacts BT broadband customers.

For some unknown reason the following IP address is unroutable from the BT end:

185.17.24.90

All other IPs in the /29 work fine with BT (185.17.24.91 for example)..

I have seen this issue with 3 different BT internet customers but it would be helpful if any other BT users could just to a quick ping or MTR in that problem IP for me just to confirm it is widespread within the BT network.

Second question is does anyone know of anyway to contact the BT NOC team? I've been on the phone to various departments all morning but am unable to get past the first line of defence!

I'm on BT and I can't ping or traceroute to that address. 89 and 91 work fine.

In a reply to a similar (but not identical query) BT say

If you think a site shouldn’t be categorised as potentially harmful, you can contact us at [email protected] providing the details of the site you believe is being incorrectly categorised and we'll send this to our third-party supplier for further investigation. If it is verified as potentially harmful, you will need to contact your site administrator to resolve the issue on your website.

Edited by TinyMongomery (Fri 26-Apr-24 14:05:20)

I feel quite strongly about this. It is not for ISPs to classify sites as harmful or not. ISP's should be providing connectivity to all IP addresses without fear or favour. Classifying sites as good or bad should be done by other means at the customer's option.

I'm on BT..

Same here.

Same for PlusNet - yes BT owned but still have their own network management.

No Ping or Tracert

Just for completeness, 185.17.24.90 is definitely pingable from a Zen connection.
John

You can ping that IP from the BTnet Looking Glass so it seems like only broadband customers are affected

http://lg.bt.net/cgi-bin/welcome

In reply to a post by TinyMongomery:

I'm on BT and I can't ping or traceroute to that address. 89 and 91 work fine.

In a reply to a similar (but not identical query) BT say

If you think a site shouldn’t be categorised as potentially harmful, you can contact us at [email protected] providing the details of the site you believe is being incorrectly categorised and we'll send this to our third-party supplier for further investigation. If it is verified as potentially harmful, you will need to contact your site administrator to resolve the issue on your website.

Thanks for the suggestion. I've sent them an email so will see if I get a response. Although there aren't actually any websites on that IP, its main use was as a DNS server although not beyond the realms of possibility that a previous user of that IP hosted something dodgy in there as we only started using the IP this past Tuesday.

Also not accessable from EE (again no surprise as linked with BT)

OK from an A&A connection

Edited by nrb501 (Fri 26-Apr-24 21:00:28)

In reply to a post by nrb501:

Also not accessable from EE (again no surprise as linked with BT)

OK from an A&A connection

Same here on EE.

PING 185.17.24.90 (185.17.24.90): 64 data bytes

Request timed out!

Request timed out!

Request timed out!

Request timed out!

--- Ping Statistic "185.17.24.90" ---

Packets: Sent=4, Received=0, Lost=4 (100.00% loss)

ping is stopped.

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.

Works fine on YouFibre, can't test on leased lines until next week,

In reply to a post by DantD9:

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

Nope, they are noting to do with BT what's so ever, they install their own infrastructure but only provide for the London area.

---
Paul

Just a quick update to say that there isn't really an update!

Still awaiting a reply from anyone within BT to the numerous departments I have tried to contact and still no ping from that single IP. So frustrating trying to deal with a company that doesn't have any solid point of contact for issues like this.

I don't like giving up but it may just be time to do away with the IP and use a different one.