topic Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare in Broadband & Landline

Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

tomble — Tue, 09 Jun 2026 15:40:12 GMT

Hi everyone,

I am experiencing a severe routing issue on my EE Home Broadband connection that is intermittently (sometimes totally) blocking access to dashboard.render.com (and associated hosted applications).

As a SaaS business owner who hosts my infrastructure on Render, this routing failure has entirely broken my development workflow and access to my live platform. I have just lost a full business day troubleshooting this infrastructure issue instead of driving actual value for my business, which has been incredibly frustrating.

I have performed extensive differential testing and isolated the issue entirely to the EE/BT core routing network.

The Problem

Any TCP connection over Port 443 (HTTPS) to Render's IP block (216.24.57.x) times out completely on EE Home Broadband.

Diagnostics & Cross-Carrier Testing

EE Home Broadband: 100% failure rate. Test-NetConnection on port 443 fails with a TCP timeout.
EE Mobile Hotspot: Degraded/Intermittent. It resolves via a NAT64 gateway (64:ff9b::), fails on the primary target, but occasionally succeeds on a fallback IP.
Vodafone Mobile Hotspot: 100% success rate. Instantly connects to the destination on port 443.
Local Settings: I have completely turned off EE Web Protection, Content Lock, and Parental Controls. This is not a local firewall or software block.

Traceroute Evidence (The Smoking Gun)

A tracert from my EE Home Broadband connection shows that traffic traverses the BT core network perfectly fine until it hits the Global Internet Access (GIA) edge network, where it dies immediately at hop 8 (166-49-135-83.gia.bt.net). It never leaves the BT network to be handed off to the destination:

Plaintext

Tracing route to gcp-us-west1-1.origin.onrender.com.cdn.cloudflare.net [216.24.57.7]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  ************
  2     4 ms     3 ms     4 ms  ************
  3     *        *        *     Request timed out.
  4     *        6 ms     *     62.172.102.140
  5     6 ms    14 ms     6 ms  peer7-et-3-0-3.telehouse.ukcore.bt.net [62.6.201.226]
  6     7 ms     7 ms     6 ms  transit1-xe-000.telehouse.ukcore.bt.net [194.72.16.177]
  7     6 ms     6 ms     7 ms  166-49-214-166.gia.bt.net [166.49.214.166]
  8     9 ms     8 ms     8 ms  166-49-135-83.gia.bt.net [166.49.135.83]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
[...times out continuously up to 30 hops...]

Next Steps

Because this is happening deep within the gia.bt.net transit layer, this appears to be a broken BGP route or an issue at a major peering exchange point between BT/EE and Cloudflare/Render's upstream network.

Could a forum moderator please escalate this traceroute directly to the Tier 2/Tier 3 Network Engineering/NOC teams? Standard customer service handles cannot resolve backbone routing table issues.

I suspect this affects many other internet services hosted on that IP range that Cloudflare/Render uses.

Thank you.

[Mod edit: Personal details redacted. Please do not share personal details as your posts are visible to the public. Thanks!]

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

XRaySpeX — Tue, 09 Jun 2026 15:55:05 GMT

It traces fine here over EE FF150 (the Blank Bullet):

16:44:50.34 C:\>tracert http://dashboard.render.com/
Unable to resolve target system name http://dashboard.render.com/.
16:45:19.30 C:\>tracert dashboard.render.com
Tracing route to gcp-us-west1-1.origin.onrender.com.cdn.cloudflare.net [216.24.57.251]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms OrangeRouter2 [192.168.1.2]
2 2 ms 2 ms 2 ms 172.16.14.26
3 * * * Request timed out.
4 4 ms 3 ms 3 ms 62.172.102.78
5 4 ms 4 ms 4 ms 213.121.193.153
6 4 ms 4 ms 4 ms transit1-xe-0-0-1.telehouse.ukcore.bt.net [194.72.16.179]
7 5 ms 4 ms 4 ms 166-49-214-192.gia.bt.net [166.49.214.192]
8 7 ms 5 ms 5 ms t2c3-et-8-3-0.uk-lof.gia.bt.net [166.49.195.182]
9 5 ms 5 ms 5 ms t2c4-et-3-0-5-1.uk-lof.gia.bt.net [166.49.250.59]
10 6 ms 6 ms 5 ms linx-lon1.as13335.net [195.66.225.179]
11 6 ms 6 ms 6 ms 141.101.71.1
12 5 ms 5 ms 5 ms 141.101.71.133
13 5 ms 5 ms 5 ms 216.24.57.251
Trace complete.

What is the name of the EE BB plan you are on including its speed? Which EE router & WiFi extenders, if any, do you have (read label or post a pix)?

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

XRaySpeX — Tue, 09 Jun 2026 16:00:33 GMT

This user discussion group is not the correct platform for formally escalating issues & requiring their fix in EE systems. You need to report your issues to CS. Failing any progress that way you could raise a complaint.

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

JimM11 — Tue, 09 Jun 2026 16:08:50 GMT

@tomble Good on the vodafone broadband network also.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| ZenWiFi_XT8-BBD0 - 0 | 61 | 61 | 1 | 1 | 3 | 1 |
| 90.247.128.1 - 0 | 61 | 61 | 4 | 163 | 326 | 155 |
| 63.130.172.35 - 58 | 19 | 8 | 11 | 12 | 14 | 11 |
| 90.255.251.37 - 0 | 61 | 61 | 12 | 14 | 30 | 12 |
| 162.158.32.45 - 0 | 61 | 61 | 11 | 15 | 78 | 13 |
| 216.24.57.251 - 0 | 61 | 61 | 11 | 12 | 18 | 12 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

Steve_BT — Wed, 10 Jun 2026 08:50:18 GMT

It's working fine from my EE connection at home. Are you still seeing the issues? As you can see from @XRaySpeX traceroute, the next hop is a direct peering to linx-lon1.as13335.net so we'd have no control once traffic leaves our network. Maybe they were blocking our IP ranges or something.

Steve

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

matthubbert77 — Sat, 13 Jun 2026 18:50:29 GMT

I'm glad to find this post - I've been suffering with the same issue, seemingly affecting only EE/BT connections. My client I host websites for has been really angry and struggled to accept it's a BT issue, despite Render support providing proof of this.

@Steve_BT if you keep refreshing pages for long enough, you'll find it eventually takes a minute to load. This happens multiple times an hour for me (on EE). It's unacceptable.

I did my own troubleshooting and found in my logs theres nothing wrong with my app - once the request hits the app it processes instantly. But something is preventing the request from reaching the app in the first place.

Render have apparently been hit with an inrush of support tickets, all coming from BT customers, and have pushed it back to me saying to raise a case with BT. This is hard since I'm not a BT customer. They provided some tests they did which proves other internet providers work fine, while there is consistently intermittent problems with BT connections. This is their response to my ticket and how they ran their test with globalping:

You can provide this output to your client who disputes a BT-specific issue:

> London, GB, EU, British Telecommunications (AS2856), u-wii747
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:12 GMT

> Levisham, GB, EU, British Telecommunications (AS2856)
Request timeout.

> Middlesbrough, GB, EU, British Telecommunications (AS2856), u-PS6
Request timeout.

> Blackpool, GB, EU, British Telecommunications (AS2856)
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:11 GMT

> Woking, GB, EU, British Telecommunications (AS2856)
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:13 GMT

> London, GB, EU, YouFibre (AS212655), u-temilash
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:11 GMT

> Bridgend, GB, EU, YouFibre (AS212655), u-matthewgall
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:11 GMT

> Manchester, GB, EU, YouFibre (AS212655), u-matthewgall
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:11 GMT

> Tipton, GB, EU, YouFibre (AS212655)
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:11 GMT

> Cardiff, GB, EU, YouFibre (AS212655)
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:47:11 GMT

The issue as we've seen is sporadic request failures when using BT. This output displays 100% success via another ISP (YouFibre), and 3/5 successes across BT when accessing https://***.onrender.com

The system I'm using for generating these pings is globalping.io, running it a second time, BT only:

> London, GB, EU, British Telecommunications (AS2856)
Request timeout.

> Levisham, GB, EU, British Telecommunications (AS2856)
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:50:24 GMT

> Woking, GB, EU, British Telecommunications (AS2856)
Request timeout.

> Middlesbrough, GB, EU, British Telecommunications (AS2856), u-PS6
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:50:24 GMT

> Blackpool, GB, EU, British Telecommunications (AS2856)
Request timeout.

> London, GB, EU, British Telecommunications (AS2856), u-wii747
HTTP/1.1 302
Date: Thu, 11 Jun 2026 01:50:24 GMT

> London, GB, EU, British Telecommunications (AS2856)
Request timeout.

3/7 successful. This problem is localized to BT, and BT needs to address it.

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

JimM11 — Sat, 13 Jun 2026 19:51:15 GMT

@matthubbert77 Are you on a business or residential EE connection?

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

matthubbert77 — Sat, 13 Jun 2026 19:56:41 GMT

Personally I'm on a 4G router, my clients who use the website are likely on a Business (BT) connection.

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

JimM11 — Sat, 13 Jun 2026 20:03:51 GMT

@matthubbert77 Business Broadband | Fibre | Small Business | EE Business

Business Broadband & Connectivity solutions | BT Business

Places that may be better to start, Are you a EE or BT customer at all?

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

JimM11 — Sat, 13 Jun 2026 20:10:52 GMT

@matthubbert77 Still clear this end vodafone BB connected network so you know.

C:\Windows\System32>tracert dashboard.render.com

Tracing route to gcp-us-west1-1.origin.onrender.com.cdn.cloudflare.net [216.24.57.9]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ZenWiFi_XT8-BBD0 [192.168.50.1]
2 6 ms 5 ms 4 ms 90.247.128.1
3 11 ms 12 ms 13 ms 63.130.172.35
4 14 ms 13 ms 13 ms 90.255.251.37
5 20 ms 20 ms 23 ms 162.158.32.45
6 12 ms 13 ms 12 ms 216.24.57.9

Trace complete.

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

XRaySpeX — Sat, 13 Jun 2026 20:54:38 GMT

@matthubbert77 : Please explain what those tables of entries are. Are they:

A tracert sequence with no timings?
Targets of pings with failures?
Origins of pings with failures?

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

matthubbert77 — Sat, 13 Jun 2026 21:13:07 GMT

It looks to be a test performed by globalping.io - Render support sent them to me to demonstrate how out of 7 attempts, 3 were successful.

I just tried it myself out of curiosity, and sure enough I see intermittent results when I select British Telecommunications. A lot of timeouts.

Similar with a tracert. Sometimes they each, often they hang after 166-49-135-83.gia.bt.net

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

matthubbert77 — Sat, 13 Jun 2026 21:18:55 GMT

Render sent them to me, I believe they're a test using globalping website to demonstrate how out of 7 attempts, 3 were successful.

Out of curiosity I just tried it myself and sure enough see intermittent results when selecting British Telecommunications, targetting dashboard.render.com. Lots of timeouts.

Similarly with tracert, sometimes it reaches but often it doesn't, hanging after 166-49-135-83.gia.bt.net

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

matthubbert77 — Sat, 13 Jun 2026 21:49:37 GMT

I googled the address the traceroutes get hung up on, and it looks like it's starting to pop up in other places too. Here's a recent thread on Plusnet, with someone unable to access a specific site (Pushsafe?) with the same apparent symptoms.

https://community.plus.net/t5/Broadband/I-can-no-longer-access-pushsafer-com-via-Plusnet/td-p/2048276

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

XRaySpeX — Sun, 14 Jun 2026 00:51:06 GMT

@matthubbert77 : So to be clear they are the results of pinging a specific target, gcp-us-west1-1.origin.onrender.com.cdn.cloudflare.net [216.24.57.251], from various sources, automated somewhat by globalping.io,

There are often reports of users not being able to reach a site for many numerous varied reasons.

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

JimM11 — Sun, 14 Jun 2026 14:13:27 GMT

@matthubbert77 If you need to take it up with someone then see the info link.

https://www.bt.net/peering-information.html

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

matthubbert77 — Sun, 14 Jun 2026 14:27:52 GMT

Interestingly, I've been checking all day and not seen the issue yet. I wonder if something changed in the past 12 hours. Using globalping for pings and traceroutes has had 100% success every time, whereas last night, the opposite. Specifically, 166-49-135-83.gia.bt.net isn't showing up in the hops any more. Maybe it's a timing thing, but will continue to monitor.

Re: Routing failure on BT/EE Backbone blocking access to Render.com / Cloudflare

JimM11 — Sun, 14 Jun 2026 14:32:26 GMT

@matthubbert77 As it's BT peering and know idea what or way it goes after the hop ceases, unless you have the exact same route followed and all are/can be different at one snapshot in time, then again if it was an Equipment issue, it may have just been reset overnight. My VF connection seemed to be very consistent on the two individual days one on MTR and the other as Tracert.