Three blocking AIB verification texts

Happened to me aswell on three when I was shopping around and after dealing with support for hours on end they said buying a new phone would "fix" it. Enough was enough so I switched to Vodafone as I was also with them previously and it worked again fine.

Happens on a few networks. I assume its a porting issue, since it only happens after a port.

So your theory is one of the countries main phone provider blocks texts from one of the main banks, making them incompatible for half the population. How likely is that?

It's more likely porting issue, happens occasionally and not just with three. They will have to redo the port. You probably won't get them outside of mon-fri

https://community.three.ie/t5/Bill-Pay-Plans-and-Services/Do-not-receive-text-messages-from-banks-and-Apple-and-others/td-p/775480

I have been on three for a good few years, and AIB even longer and never had this problem.

I might be porting soon, Will let you know ;)

It is a porting issue and a not uncommon one too.

Chances are people on one or more of the other networks can't call or text you either (but you'll be able to text them) nor can anyone who uses the same bulk provider as AIB, but you've only noticed AIB so far.

Each operator has a database they can look up to see where any given number resides at that time in order to route calls and texts to the correct place.

When you port each operator should receive an instruction to update their database to say your number is no longer with X network and is now with Y. Sometimes that doesn't happen properly so one or more networks will continue to try and route your calls/texts via your old operator which will fail.

If you port back to your previous operator then this often appears to "fix" the issue because the out of date database is now technically correct again.

If you port to a third operator Z this won't fix it either because the database sees an instruction coming from Y, but as far as it is concerned you are still with X, so the instruction is invalid.

Your only solution, bar going back to your previous operator, is to push Three to correct it - they can manually resubmit the update request to the various networks which will fix the problem.