You’ve dialled an incorrect number!

[Ted845]

Hello all. I know we've had this issue before a few times, the last time was around Christmas. 

Today I'm suddenly not able to receive or make calls - getting the 'you've dialled an incorrect number' message. The previous solution was to toggle 'flight mode' on and off and that works for a while before it fails again.

Are others are experiencing this too? Tbh I'm strongly considering leaving Sky after years with them - as others have noted, it's virtually impossible to get through to a real person now and the service seems to be more and more unreliable,

Does anybody know if there's a permanent fix for this or whether this is something we have to live with now?!

Many thanks.

[caesarome]

@Ted845 

Do any issues appear here for you:

https://www.sky.com/help/servicestatus/mobile

If not are you able to call Dky on 150 about this ?

[Ted845]

I haven't called them yet, I've decided to see if it corrects itself. Tbh I find getting through to a real person at Sky pretty hard - it never used to be so - and the language skills of the most recent attempts have been so poor I gave up. 

Looking back on this forum there were the same issues last year in July, and then again for days over Christmas affecting a lot of people. I'm assuming some of the 'no signal' threads on here over the last day or so may be the same issue under a different banner.

If it's still a problem tomorrow morning I'll call them and see what they say. Until then I'll use the advice given in both July and December and toggle 'flight mode' on an off which makes it work for a while.

[Ted845]

Sorry, just to add the signal checker - in common with others commenting on different threads - shows no issues here.

[Ted845]

This seems to have resolved itself - started working properly yesterday afternoon and able to make and receive calls this morning.

The exact same issues previously, in July 2025 and again in December 2025, made me expect it to be a more widespread issue as before. I guess this time it was a local 'glitch.'