How SMS Routing Works: Why Your Code Takes 3 Seconds or 90

The Path From Platform to Handset

Almost no platform runs its own SMS infrastructure. When you request a code, the platform's backend makes an API call to a communications provider, of which Twilio, Sinch, Infobip, Vonage, and MessageBird carry most of the world's verification traffic. The provider accepts the message, decides which route to use for the destination number, and hands it to either a direct carrier connection or an aggregator that has one.

Aggregators are wholesalers. They buy SMS termination from carriers in bulk and resell it to providers and to each other. A message to a number in a country where the provider has no direct carrier link may pass through two or three aggregators before reaching the carrier. Each hop adds a queue and each aggregator may apply its own filtering.

The carrier receives the message at its SMSC, the short message service centre, checks that the number is active and reachable, and pushes it to the handset over the signalling network. For a temp number on TempNumber.me, the handset is a SIM in a rack, and the message appears on the dashboard within a second or two of the carrier delivering it. The dashboard delay is the smallest part of the total.

Why the UK Takes 3 Seconds

A code to a UK number from a large platform travels the shortest possible path. Twilio, Sinch, and Infobip all have direct connections to EE, Vodafone, O2, and Three, so there is no aggregator between the provider and the carrier. UK carriers apply light filtering to A2P traffic from registered senders, and the platform's sender identity is pre-registered on those routes.

The same is true for the United States, Canada, Germany, the Netherlands, France, and most of Western Europe. The provider has a direct route, the carrier trusts the sender, and the only delay is queueing during peak traffic. Three to ten seconds is normal, and anything under a minute is within specification.

Why Nigeria Takes 90 Seconds, or Never Arrives

A code to a Nigerian number often travels a longer path. Providers have fewer direct connections to MTN, Airtel, Glo, and 9mobile, so the message goes through an aggregator, sometimes two. Nigerian carriers also apply heavy filtering to international A2P traffic, in part because the NCC requires sender-ID registration and in part because the carriers charge a premium for international termination and filter messages that look like they are avoiding it.

Providers respond to the premium by using cheaper routes when they can, and cheaper routes are slower and less reliable. A message that leaves the provider at second zero can sit in an aggregator queue for a minute before the carrier accepts it, and some are dropped by the carrier's filter without any bounce back to the platform. The platform shows "code sent" because the provider accepted the message, and the user waits for something that will not come.

India, Pakistan, Bangladesh, Indonesia, the Philippines, Kenya, Ghana, and Egypt have versions of the same picture. Each has a regulator with sender-ID or template registration rules, carriers that filter international traffic, and providers that route around the cost. The delay is not random; it is the sum of the hops and the filters on that route on that day.

A2P Filtering and Grey Routes

A2P means application-to-person, which is what a verification code is. Carriers price A2P higher than P2P, person-to-person, and they run filters to catch A2P traffic sent over P2P routes. Those P2P routes used for A2P are called grey routes. They are cheaper for the provider, they work most of the time, and they fail without warning when the carrier's filter catches a batch of messages that all look like verification codes from the same source.

A message on a grey route can be delayed while the filter decides, delivered with the sender changed to a random number, or dropped. Platforms that pay for clean A2P routes on every country deliver more reliably. Platforms that optimise cost route some countries over grey routes and accept a share of failures. Users cannot see which is happening, but the symptom is consistent: fast, reliable delivery in some countries and unpredictable delivery in others from the same platform.

On TempNumber.me, the country list for each service reflects this. Countries where a platform's route is clean are stocked and marked as working; countries where the route is unreliable are either not offered for that service or carry a lower success rate. Picking a well-routed country is the single biggest thing a user can do about delay, and the guide at /blog/how-to-choose-country-for-verification covers which countries those are per platform.

Sender-ID Rules by Country

The sender ID is the name or number that shows as the source of the SMS. Some countries let a platform use an alphanumeric sender such as the brand name; others force it to a short code, a long number, or a registered ID. India requires every sender and template to be registered on the DLT platform before a message will be delivered. Nigeria, the Philippines, Vietnam, Saudi Arabia, the UAE, Egypt, and Turkey have registration rules of their own. The United States requires 10DLC registration for A2P traffic on long numbers, which is why many platforms send US codes from a short code.

A platform that has not registered in a country either has its messages dropped or has them rewritten by an aggregator to a generic sender, which is why a code sometimes arrives from a random local number rather than the brand. Both outcomes look like a routing failure to the user. Large platforms register in every country they serve; smaller ones register in their main markets and accept losses elsewhere, which is why a small app's code may never arrive on a number in a country where WhatsApp's arrives in seconds.

Why Some Platforms Call Instead

When a provider's data shows SMS delivery rates below a threshold for a country, the platform can switch that country to voice OTP: an automated call that reads the code aloud. Voice termination is routed differently, is filtered less, and reaches carriers that block or delay international SMS. WhatsApp, Telegram, Google, Facebook, and Microsoft all fall back to a call in some countries, and some offer it as an option on the first attempt where SMS is known to be poor.

A temp number that receives SMS only cannot take that call, which is why a platform that has moved a country to voice-first will appear to fail on a temp number there. The fix is a country where the platform still sends SMS, which is usually a well-routed one. Where a platform sends SMS first and offers a call only after a failure, the SMS attempt still works normally on the temp number.

Where Codes Are Lost, Hop by Hop

At the platform: rate limits after several requests from one account or IP, and fraud scoring that decides not to send at all while still showing "code sent". At the provider: a route selection that picks a cheap path for the destination country. At the aggregator: queueing, filtering, and sender rewriting. At the carrier: A2P filters, sender-ID registration checks, and spam heuristics that drop batches of similar messages. At the handset or SIM bank: almost never, which is why the dashboard on a temp number service reports the arrival time honestly.

The practical consequence is that a code that has not arrived in ninety seconds on a poorly routed country is unlikely to arrive at all, and a code that has not arrived in fifteen seconds on a well-routed one is worth waiting another minute for. The troubleshooting sequence for a missing code is at /blog/sms-not-arriving-troubleshooting, and why the code has expired by the time a slow route delivers it is explained at /blog/why-sms-codes-expire.

What This Means When Picking a Number

Delay is a property of the route between a platform and a country, not of the number. The same TempNumber.me number receives a WhatsApp code in seconds and a small app's code a minute later because the two platforms use different providers on different routes. Choosing a country where the platform has a direct, registered route removes most of the delay and nearly all of the drops.

The countries with clean routes for the major platforms are the United States, United Kingdom, Canada, Netherlands, Germany, France, Poland, and a handful of others, and they cost more than countries on grey routes because carrier termination there is priced for A2P. The lookup the platform runs before deciding whether to send at all is a separate step, explained at /blog/carrier-lookup-explained. A cheap number in a country where the platform routes badly saves nothing if the code does not come; credit for activations that received no SMS is reviewed case by case via support@tempnumber.me, but the time is gone either way.