topic Re: Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts) in Broadband

Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts)

Exilax — Tue, 04 Aug 2026 21:14:52 GMT

Hi team, my line is currently provisioned on MAP-T CGNAT with address sharing. This is causing severe TCP handshake timeouts, packet fragmentation, and load failures on secure banking APIs (like Amex) and HTTPS streaming endpoints. I need a reactive opt-out from MAP-T IPv4 address sharing to assign my connection back to a standard dual-stack / unshared 1:1 IPv4 profile. Please escalate this to the internal network team.

Many thanks in advance!

Re: Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts)

Chrisee — Wed, 05 Aug 2026 05:45:37 GMT

@Exilax you are not talking to Sky by posting in this forum. Sky's use of MAP-T is restricted to customers who have the white Sky Max and Sky Gigafast+ hubs. Most issues caused by sharing of IP4 addresses can be sorted by enabling UPnP which swiitces the share to 1:1 . See UPnP set up

The issues you post have never previously been linked to MAP-T to my knowledge and given they would inevitably affect many customers this would have come up before. Why do you think they are linked?

Re: Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts)

Exilax — Wed, 05 Aug 2026 06:47:36 GMT

Thanks for the reply. To clarify, my router status explicitly shows MAP-T Sharing Ratio: 1:1 already, so port sharing isn't the issue. UPnP handles local port forwarding, but it cannot fix the MTU packet fragmentation and TLS handshake timeouts introduced by MAP-T encapsulation on secure HTTPS/API endpoints (such as banking apps like Amex).

I have already disabled Broadband Shield and tested all local options. This is a known protocol-level issue with MAP-T handling MTU overhead. I am requesting a Sky Community employee/moderator to escalate this thread to Tier 2 Support for a manual reactive opt-out from the MAP-T profile.

Re: Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts)

Chrisee — Wed, 05 Aug 2026 07:04:48 GMT

@Exilax I do not agree with your diagnosis as MAP-T does not cause fagmentation based on my technical knowledge. However I am escalating your post to the Sky team who support the forum who should be in touch soon to offer you a private online chat session to get look into this isdue. Keep an eye on the forum as if you miss the message just click the brightly coloured chat icon which will be added to the forum pages for you to use.saving a long phone call.

Escalating a post to a Sky expert | Sky Community

Re: Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts)

Exilax — Wed, 05 Aug 2026 07:10:45 GMT

Thank you, Chrisee. Much appreciated! I will keep an eye on this thread and join the chat session once it will become available.

Re: Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts)

Exilax — Sat, 08 Aug 2026 11:50:58 GMT

The automated system closed my ticket with a generic text stating 'no network issue found' because the physical fiber line sync is healthy (760 Mbps). However, this is a protocol-layer MAP-T encapsulation issue breaking HTTPS/TLS handshakes, not a physical line fault. Could a Sky moderator please re-open this ticket and specifically flag it for a human Tier 2 / Network Operations engineer to process a Reactive Opt-out from MAP-T IPv4 Address Sharing?

Re: Requesting Reactive Opt-Out from MAP-T IPv4 Sharing (Packet Loss & Banking Timeouts)

SuperMatt — Sat, 08 Aug 2026 13:30:50 GMT

Hello again, @Exilax. I'll send you an invite to a private chat shortly and we can help you.

Just look out for the colourful bubble to start the conversation. Please be aware conversations automatically close if there is no response within 48 hours. Here's more information on how Community Messaging works - https://helpforum.sky.com/t5/Did-you-know/Escalating-a-post-to-a-Sky-expert/ba-p/3711147#M141