iMessage Not Delivering to One Person Only

Messages reaching everyone except one person is a specific failure with a small number of causes, and the instinct to assume you have been blocked is usually wrong. There are at least four more likely explanations, and they are all testable in about three minutes.

What makes this frustrating is that iMessage deliberately refuses to tell you which one applies. A message to a blocked number and a message to a phone in a drawer with a flat battery produce the same result on your screen, because distinguishing them would turn block lists into a surveillance tool.

So the approach is elimination rather than interpretation.

Three tests that narrow it down

Test 1 — reach them another way. Send a WhatsApp message, an email, or ring them. If they respond, their phone is on and connected, which eliminates the whole “device unreachable” family of causes.

Test 2 — message them from a different phone. Borrow one, or use a work phone. If your message arrives from the other number and not from yours, you have narrowed it to something specific between your two accounts.

Test 3 — message someone else from your phone. If your messages to everyone else are fine, your iMessage registration is healthy and the problem is not on your end.

The green bubble case

If messages to this one person go green while everyone else stays blue, the message is being sent as SMS. That means iMessage is not available for that contact, and there are three reasons:

• They moved to Android and did not deregister their number from iMessage, or did deregister, in which case green is correct and expected.
• Their iMessage is off, either deliberately or because their phone fell off Apple’s servers after a SIM change.
• You are messaging a different identifier. iMessage registers both phone numbers and email addresses. If your contact card has their email and they removed that address from their Apple ID, messages route to a dead endpoint.

Check which identifier you are using: open the conversation, tap their name at the top, and look at what is listed. Switching from an email address to the phone number, or vice versa, resolves a surprising share of these.

The classic version of this is someone who switched from iPhone to Android and left their number registered. Their number still looks like an iMessage address to Apple, so your phone sends iMessage, and nothing arrives. They fix it at Apple’s deregistration page; you cannot fix it from your side.

When it stays on Delivered and nothing happens

A blue bubble that says Delivered has reached Apple’s servers and been handed to a registered device. That device might be a Mac they never use, or an iPad in a kitchen drawer.

This is the single most misread state in Messages. Delivered means the message left the building, not that it landed in front of a person.

Things that produce a permanent Delivered with no reply and are not a block:

• They have Focus or Do Not Disturb on, with your contact not on the allow list. The message is there; the notification is not.
• They have notifications muted for your conversation specifically. The conversation shows a crescent moon icon on their end, not yours.
• Their phone is off and an iPad took delivery.
• They have Filter Unknown Senders on and you are not in their contacts, so your conversation is sitting in a separate tab they never check.

That last one catches people out constantly, particularly after someone changes phone and loses their contacts.

When the problem is your registration

If test 3 showed messages failing to everyone, fix your own setup before thinking about the contact at all.

1. Check iMessage is on and shows your details. Settings → Apps → Messages → Send & Receive. Your phone number and Apple ID email should be listed and ticked. On iOS 18 this path is under Apps; earlier versions list Messages directly in the main Settings list.
2. Toggle iMessage off, wait 30 seconds, and back on. This forces re-registration with Apple’s servers. It can take a few minutes and sometimes needs a restart to complete. “Waiting for activation” that persists for more than an hour usually means a date, time or network problem.
3. Confirm the date and time are automatic. Settings → General → Date & Time → Set Automatically. A wrong clock breaks the certificate validation iMessage depends on, and it is a real cause rather than folklore.
4. Check you have data. iMessage needs an internet connection; SMS does not. A phone on a Wi-Fi network that connects but has no working internet will fail iMessage while texts work fine, which looks very odd until you know. The diagnosis is in Wi-Fi that says connected but has no internet.
5. Reset network settings if nothing above helped. Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings. It clears every saved Wi-Fi password, so have them available.

On working out whether you are blocked

You cannot, and chasing it wastes an evening. The commonly repeated tests do not hold up:

• Ringing them and getting one ring before voicemail is sometimes cited as proof. It is also what happens when a phone is in Do Not Disturb, in a tunnel, or has call forwarding set.
• Delivered versus no status depends on their device state, not your block status.
• Sending from a different number tells you something arrived, but not why the first one did not.

If you need an answer, the reliable method is the unwelcome one: ask them through a channel that works.

Realistic expectations

Most single-contact delivery failures turn out to be the identifier problem, with the wrong email or phone number sitting on the contact card. The next most common is a recipient whose iMessage registration broke after they changed device. Both resolve once identified, though the second needs action from them.

The genuine limit is that you have no visibility into the other phone. If they have Focus on, notifications muted, or your messages filtered into the unknown senders tab, every message you send is arriving correctly and sitting unread, and nothing you change on your phone will alter that.