Messaging
Why some text messages never arrive on a travel number
Bank codes and delivery notifications often fail on a travel number while ordinary messages arrive fine. The reason is filtering, not signal.
Most travellers assume a text is a text. In practice there are two very different kinds moving through the network, and only one of them is reliably delivered to a number you picked up for a trip. Understanding which is which explains why your friend's message arrives instantly and your bank's verification code never does.
Quick takeaways
- Person-to-person and application-to-person messages travel different routes with different rules.
- Automated senders are registered, filtered, and frequently blocked from delivering to numbers they do not recognise.
- A code that never arrives is usually refused upstream, not lost in transit.
- Any account you might need to verify abroad should be moved to an app-based method before you leave.
Two kinds of text message
A message from another person is person-to-person traffic. It moves between subscribers and carriers deliver it with few questions asked. A message from a bank, an airline, or a delivery service is application-to-person traffic: it originates from a platform, is sent in bulk, and is subject to registration rules, sender vetting, and filtering that ordinary messages never encounter. That second category is where travellers run into trouble. The filtering exists for good reasons — it is what keeps bulk fraud off the network — but it is tuned around expected patterns, and a number that has just started receiving traffic in a new country does not look like an expected pattern.
Why the code specifically fails
Several things can stop an automated message and none of them look like an error to you.
In every one of those cases the message is refused somewhere upstream. Your phone was never offered it, so there is nothing to retrieve, resend, or wait for.
- The sender may not be registered to deliver to the country your number belongs to.
- The route the sender's platform chose may not support delivery to your number type at all.
- The message may be filtered as suspected bulk traffic before it reaches your carrier.
- Your own bank may refuse to send codes to a number it has not seen on the account before.
Set up before you leave, not after
The fix is almost entirely preparation, because every alternative to SMS has to be enabled from a device that is already trusted. Move any account you might genuinely need while travelling to an authenticator app, a passkey, or a hardware key. These generate or hold credentials on the device itself and do not depend on a message crossing a network at all. Where an account offers backup codes, print them or store them somewhere reachable without a connection. Keep one channel that does not rely on your travel number. That might be your home line kept active for messages only, or an email-based recovery route you can reach over Wi-Fi.
What a travel number is good for
None of this makes a travel number less useful — it makes it useful for the right things. Calls, ordinary messages with people, restaurant bookings, drivers, and local services all work exactly as expected. The limitation is narrow and specific: automated senders that vet their destinations. Once you stop asking a travel number to carry your bank's verification traffic, the rest of what it does becomes reliable.
A missing verification code is a filtering decision, not a coverage problem. Move the accounts that matter to app-based verification before you travel, and let your travel number do the things it is genuinely good at.
Explore Globalia plansSources & further reading
- Roaming: using your mobile in the EU (European Commission)
- Mobile device guidance (UK National Cyber Security Centre)