cancel
Showing results for 
Search instead for 
Did you mean: 

FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

Emeric
Hooked
Posts: 8
Thanks: 5
Registered: ‎14-10-2025

FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

Hi Plusnet Team,

Username: [Removed] (FTTP customer, Totnes area)

Since my fibre installation, my connection has consistently been assigned IPs
in the 147.147.130.x range, which appear to geolocate to Edinburgh.
Everything else on the line works perfectly, but Xbox Cloud Gaming has become
unplayable due to extremely high latency (~280 ms). Before fibre, it worked flawlessly.

Traceroute to xbox.com clearly shows my traffic leaving the UK through Marseille (mrs20):

10 be-26-0.ibr01.mrs20.ntwk.msn.net [104.44.29.51] 280 ms
22 20.70.246.20 (xbox.com)

Ping to Google (8.8.8.8) averages 9 ms, confirming the local line and router are fine.
This looks like a routing or Geo-IP issue with the 147.147.130.0/24 block,
causing Microsoft’s network to route my traffic via Azure’s South Europe region
instead of UK South or West Europe.

Steps tried:
• Restarted ONT + router (over 60 minutes powered off) → same IP range
• Changed DNS (1.1.1.1 / 8.8.8.8) → no change
• Tested BoosterX / VPN → only VPNs with UK exit nodes restore normal latency

Could you please escalate this to the **Network Operations Team** to:
1. Move my session to a different BNG/gateway using another IP block, **or**
2. Update the Geo-IP/routing mapping for this range so Azure traffic uses UK edges (lon20 / ams20).

Thank you very much for your help,
Emeric

 

 

Moderators Note: Personal information removed

27 REPLIES 27
dvorak
Moderator
Moderator
Posts: 30,241
Thanks: 6,874
Fixes: 1,491
Registered: ‎11-01-2008

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x


Moderators Note


This topic has been moved from Broadband to  Full Fibre

Customer / Moderator
If it helped click the thumb
If it fixed it click 'This fixed my problem'
Emeric
Hooked
Posts: 8
Thanks: 5
Registered: ‎14-10-2025

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

Thank you for placing the query in the right section of the forum.

I tried again to restart ONT and router here are the results:

Update 15 Oct 2025:
After leaving my ONT and router powered off overnight I received a new IP:
194.75.95.xxx (different block from 147.147.130.x).

Traceroute to xbox.com still shows traffic routed via Marseille (mrs20)
with ~255 ms latency. First MSN hop in London (8 ms), then direct to
be-26-0.ibr01.mrs20.ntwk.msn.net. This confirms the issue is not local
but a Geo-IP / routing problem affecting multiple Plusnet IP ranges.

Could the Network Operations team please review routing to Microsoft Azure
for these prefixes and adjust the BGP / Geo-IP so Xbox traffic enters UK
Azure edges (lon20 / ams20)?

Peter_JW
Plusnet Help Team
Plusnet Help Team
Posts: 22
Thanks: 35
Registered: ‎10-12-2024

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

Welcome to the Community, @Emeric 😊

I'm keen to see what we can do to get this investigated further, so I've just sent you over a private message so we can grab some more details.

Peter

Townman
Superuser
Superuser
Posts: 28,002
Thanks: 12,499
Fixes: 235
Registered: ‎22-08-2007

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

@Peter_JW 

Could this be a related issue?

https://community.plus.net/t5/Broadband/Connection-Issues-for-Gaming/m-p/2024830#M373487

@bobpullen / @dave  could this be a peering / routing issue?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Dan_the_Van
Superuser
Superuser
Posts: 4,221
Thanks: 2,519
Fixes: 122
Registered: ‎25-06-2007

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

@Emeric 

Using nslookup I find there are five xbox.com servers globally.

You would need to use netstat to see which xbox server you are connected to, traceroutes/ping would randomly select one of the five, where as the xbox should select the best server for your locale and device settings. 
I pinged the five xbox server as provided by nslookup.

nslookup xbox.com

Name:    xbox.com
Addresses:  
          20.236.44.162
          20.70.246.20
          20.112.250.133
          20.231.239.246
          20.76.201.171

ping 20.76.201.171
Reply from 20.76.201.171: bytes=32 time=16ms TTL=112

ping 20.231.239.246
Reply from 20.231.239.246: bytes=32 time=86ms TTL=107

ping 20.112.250.133
Reply from 20.112.250.133: bytes=32 time=107ms TTL=106

ping 20.236.44.162
Reply from 20.236.44.162: bytes=32 time=150ms TTL=106

ping 20.70.246.20
Reply from 20.70.246.20: bytes=32 time=254ms TTL=107

 

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Emeric
Hooked
Posts: 8
Thanks: 5
Registered: ‎14-10-2025

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

Thanks for the suggestion, but the issue isn’t which xbox.com IP responds – it’s that my Azure traffic from Plusnet consistently exits via mrs20 (Marseille) instead of the UK. This has been confirmed on two IP ranges, so it’s likely a routing or Geo-IP mapping issue that only the Network Ops team can correct.

Dan_the_Van
Superuser
Superuser
Posts: 4,221
Thanks: 2,519
Fixes: 122
Registered: ‎25-06-2007

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

The route used could change for a given target IP Address, both IP used are xbox.com

Here's a mtr (traceroute) to 20.70.246.20 I have included the IP Address owners

HOST: wireguard-v                 Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. AS???    Archer_AX53          0.0%     1    0.5   0.5   0.5   0.5   0.0
  2. AS6871   250.core.plus.net    0.0%     1    5.2   5.2   5.2   5.2   0.0
  3. AS2856   217.32.25.144        0.0%     1    5.3   5.3   5.3   5.3   0.0
  4. AS2856   109.159.255.34       0.0%     1    6.0   6.0   6.0   6.0   0.0
  5. AS2856   194.74.16.199        0.0%     1   16.1  16.1  16.1  16.1   0.0
  6. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
  7. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
  8. AS8075   51.10.14.5           0.0%     1  251.9 251.9 251.9 251.9   0.0
  9. AS8075   51.10.23.142         0.0%     1  250.6 250.6 250.6 250.6   0.0
 10. AS8075   be-31-0.ibr02.mrs20  0.0%     1  252.5 252.5 252.5 252.5   0.0
 11. AS8075   be-14-0.ibr02.sg2.n  0.0%     1  251.5 251.5 251.5 251.5   0.0
 12. AS8075   51.10.8.229          0.0%     1  253.2 253.2 253.2 253.2   0.0
 13. AS8075   51.10.23.9           0.0%     1  250.6 250.6 250.6 250.6   0.0
 14. AS8075   51.10.25.235         0.0%     1  251.4 251.4 251.4 251.4   0.0
 15. AS8075   51.10.11.212         0.0%     1  251.9 251.9 251.9 251.9   0.0
 16. AS8075   51.10.4.250          0.0%     1  250.1 250.1 250.1 250.1   0.0
 17. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 18. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 19. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 20. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 21. AS8075   20.70.246.20         0.0%     1  251.2 251.2 251.2 251.2   0.0

Here's a mtr to 20.76.201.171

HOST: wireguard-v                 Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. AS???    Archer_AX53          0.0%     1    0.5   0.5   0.5   0.5   0.0
  2. AS6871   250.core.plus.net    0.0%     1    5.1   5.1   5.1   5.1   0.0
  3. AS2856   217.32.25.144        0.0%     1    5.3   5.3   5.3   5.3   0.0
  4. AS2856   109.159.255.34       0.0%     1    6.0   6.0   6.0   6.0   0.0
  5. AS2856   peer3-et3-1-1.redbu  0.0%     1    5.5   5.5   5.5   5.5   0.0
  6. AS8075   ae64-0.lts-96cbe-1a  0.0%     1   24.1  24.1  24.1  24.1   0.0
  7. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
  8. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
  9. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 10. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 11. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 12. AS8075   104.44.53.84         0.0%     1   13.5  13.5  13.5  13.5   0.0
 13. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 14. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 15. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 16. AS???    ???                 100.0     1    0.0   0.0   0.0   0.0   0.0
 17. AS8075   20.76.201.171        0.0%     1   15.5  15.5  15.5  15.5   0.0

AS6871 is plusnet

AS2856 is BT

AS8075 is Microsoft Corp.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Emeric
Hooked
Posts: 8
Thanks: 5
Registered: ‎14-10-2025

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

Thanks for running those MTRs — they actually illustrate the issue well.
Your trace to 20.76.201.171 hits UK South (≈ 15 ms), while mine — and your trace to 20.70.246.20 — goes through Marseille (≈ 250 ms).
My Plusnet IP range seems to be tagged for Azure South Europe.
Could the Network Operations team please check the Geo-IP / routing entry for Plusnet prefixes 147.147.130.0/24 and 194.75.95.0/24 so that Microsoft routes them via UK South or West Europe instead?

Dan_the_Van
Superuser
Superuser
Posts: 4,221
Thanks: 2,519
Fixes: 122
Registered: ‎25-06-2007

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

What I'm trying to understand why you using an off region site, a search provides this answer.

The Microsoft IP address 20.70.246.20 is assigned to a region in Australia.

Specifically, the geolocation data points to:

  • Country: Australia (AU)

  • State/Region: New South Wales

  • City: Sydney

This IP address is part of the Microsoft Corporation's network (AS8075) and is commonly associated with the Microsoft Azure cloud platform in the Australia East region.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Emeric
Hooked
Posts: 8
Thanks: 5
Registered: ‎14-10-2025

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

Thanks for checking, but that IP isn’t in Australia.
According to Microsoft’s own published Azure IP ranges, 20.70.240.0/20 belongs to the South Europe region (Marseille).
The traceroutes confirm this — all routes pass through mrs20.ntwk.msn.net, which is Microsoft’s Marseille data centre.
The latency (~250 ms) matches France, not Sydney (which would exceed 350 ms).
This supports the conclusion that my Plusnet IP range is being mapped to Azure’s South Europe region instead of UK South or West Europe, causing the high latency in Xbox Cloud Gaming.
Could this please be reviewed by the Network Operations team?

Townman
Superuser
Superuser
Posts: 28,002
Thanks: 12,499
Fixes: 235
Registered: ‎22-08-2007

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

@James_B 

Can you ask for engagement on this thread please (and the linked to one) as this potentially looks like a routing / peering issue requiring big guns attention.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Dan_the_Van
Superuser
Superuser
Posts: 4,221
Thanks: 2,519
Fixes: 122
Registered: ‎25-06-2007

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

@Emeric 

while we're waiting for some feedback, are you able to confirm the destination IP Address/s of the cloud server you are connecting to, also can you please share a traceroute ?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

James_B
Community Gaffer
Community Gaffer
Posts: 373
Thanks: 776
Fixes: 10
Registered: ‎10-09-2024

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

On it, @Townman 

Peter has reached out to the OP to arrange some single user diagnostics and I've flagged the issue internally with our technology team.

James

Dan_the_Van
Superuser
Superuser
Posts: 4,221
Thanks: 2,519
Fixes: 122
Registered: ‎25-06-2007

Re: FTTP – Routing via Marseille (mrs20) – 280ms latency to Xbox Cloud / Azure – IP 147.147.130.x

@James_B 

I have an interest in the resolution, can I be kept informed please?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.