Why this question matters and how this guide helps
A text message that will not send stops communication, creates confusion, and can feel personal even when the cause is technical. This evergreen explainer covers the most common reasons a message fails to deliver and how to identify the correct cause. We focus on verifiable technical and network factors, device settings, and carrier behaviors that are stable over time. By following structured diagnostics, you can efficiently restore reliable texting without unnecessary trial and error.
Quick answer: top reasons a text fails to send
At a high level, a text message fails when the path from sender to recipient cannot complete end-to-end signaling or delivery. The most common causes are device settings (Do Not Disturb, Airplane Mode, incorrect APN), network coverage or roaming issues, carrier provisioning or account problems, iMessage-specific failures between Apple devices, blocked or filtered content, and temporary outages or congestion. Less often, compatibility issues, full message storage, or bugs in the messaging app or OS contribute. The next sections break these into device, network, carrier, and content factors and provide prioritized fixes.
Device-level causes and fixes
Airplane Mode and basic connectivity
Airplane Mode disables radios for cellular and Wi‑Fi, which immediately prevents any SMS or MMS transmission. If Airplane Mode is on or cellular radio is off, sent messages remain in "Sending" or show an error. Quick fixes include toggling Airplane Mode off, ensuring mobile cellular is enabled in Settings, and confirming signal bars appear in the status bar.
Do Not Disturb and focus modes
Do Not Disturb and focus modes can suppress message notifications and, in some configurations, delay or prevent new message delivery UI, though they rarely block the actual network submission. If messages seem stuck, temporarily disable Do Not Disturb to test. Also check Focus filters that hide notifications from Messages and background app refresh settings that may restrict the messaging app.
APN, carrier settings, and time/date
Incorrect APN (Access Point Name) or carrier settings can block SMS/MMS paths, especially after a SIM change or carrier update. Verify that your carrier’s APN appears in Settings > Cellular > Cellular Network, and confirm carrier updates are installed. Additionally, ensure the device clock, time zone, and date are set correctly; a wrong clock can break secure signaling used by some networks.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Airplane Mode | Disables cellular radios; prevents all SMS/MMS transmission | Device specification |
| Do Not Disturb | Suppresses notifications; rarely prevents network delivery but can mask failures | Platform behavior docs |
| APN/carrier settings | Incorrect values can block SMS/MMS routing | Carrier engineering specs |
| Device clock | Incorrect time/date may interfere with secure signaling and TLS | System security guidelines |
Network and coverage factors
Coverage, roaming, and signal quality
SMS and MMS require reliable cellular signal and, for MMS, data connectivity. In weak coverage or tunnels, messages may stay in sending or fail with an error. When roaming, confirm that roaming is enabled on the plan and device; some carriers restrict SMS/MMS while roaming unless explicitly allowed. In dual-SIM devices, ensure the correct line is set as default for messaging and has active service.
Throttling, congestion, and MTU/MMS size limits
Carriers and devices impose practical limits and may throttle during peak load or temporarily blacklist numbers after suspected spam. MMS is especially sensitive to size (often capped around 1–3 MB depending on carrier) and requires accurate MTU settings; packets that exceed the network MTU can be dropped, causing MMS failures. If MMS works on Wi‑Fi but not cellular, MTU or path MTU issues on the cellular path are likely.
VoLTE and fallbacks
Voice over LTE (VoLTE) keeps voice and SMS pathways coordinated on LTE; if VoLTE is disabled on a device or not provisioned by the carrier, SMS may fall back to 3G/2G, which can be slower or unreliable in some regions. Verify VoLTE is enabled where supported, and ensure the device registers on LTE/LTE Advanced for best messaging performance.
| Metric | Estimate or Range | Context |
|---|---|---|
| MMS size limit | Typically 1–3 MB, varies by carrier | Carrier policy; affects delivery success |
| MTU standard | 1500 bytes Ethernet; cellular often 1500 or lower | Path MTU issues can fragment MMS |
| VoLTE impact | Improves SMS session continuity on LTE | Depends on device and carrier support |
Carrier and account-related causes
Account status and provisioning
Suspended lines, unpaid balances, or incomplete provisioning can stop SMS/MMS. Verify the account is active, messaging services are enabled, and there are no blocks on the line for SMS. For postpaid plans, payment holds can trigger suspensions; for prepaid, insufficient balance can block outbound messaging.
iMessage and service-specific routing (Apple)
On Apple devices, iMessage routes texts over data when available and falls back to SMS when needed. If iMessage signing or server handshakes fail, messages may send as green SMS or not send at all. Check that iMessage is enabled, the device can reach Apple’s iMessage servers, and send as SMS is allowed as a fallback. Resetting network settings can clear stale iMessage session data.
Content, filtering, and blocking
Blocked contacts and carrier filtering
Recipient-side blocks prevent delivery; similarly, carrier-level content filtering may block certain keywords, short codes, or suspicious patterns. If you suspect blocking, verify with another number or ask the recipient to check blocks and allowed senders. Some compliance filters also strip or reject messages with specific characters or headers.
Message length and concatenation issues
Long messages are split into segments (concatenated SMS), and if a segment drops, the whole conversation can stall. Very long texts or messages with certain media can also be truncated or rejected by carrier buffers. Keeping messages under typical segment limits and avoiding mixing media unexpectedly can reduce failures.
Practical diagnostics and step-by-step fixes
Use a prioritized checklist to isolate the cause efficiently.
- Confirm basic connectivity: Airplane Mode off, cellular signal present, mobile data enabled for MMS.
- Check account status and messaging add-ons with your carrier; verify no suspensions or blocks.
- Validate device settings: correct APN, updated carrier settings, correct default line on multi‑SIM devices.
- Test across conditions: try sending in different locations, on Wi‑Fi calling if supported, and with iMessage toggled on/off as appropriate.
- Review content and recipient: confirm you aren’t blocked, the recipient’s device isn’t limiting you, and the message content isn’t triggering filters.
- Inspect logs when possible: message app delivery errors, carrier settings update prompts, or system notifications can point to the specific failure reason.
When to involve your carrier or device support
If the above steps do not resolve the issue and network diagnostics point to provisioning or routing problems, contact your carrier with ESN/IMEI, line number, time stamps, and observed behavior. For persistent device-level failures, back up and update or reinstall the OS, or contact device support with device logs. Keep records of error codes and time stamps; they help support teams trace inter-network signaling issues.
Summary and key takeaways
Message failures are rarely a single universal cause; they arise from device settings, coverage and roaming, carrier provisioning, and content or network limits. By understanding each layer—device, network, carrier, and content—you can run structured checks and resolve most issues without repeated guesswork. For ongoing reliability, keep device software current, use correct APN and VoLTE where supported, maintain healthy account status, and review carrier policies for MMS and roaming. These measures make most texting problems easier to diagnose and fix the first time.