Invalid "user not found" bounces from Apple iCloud / Private Relay addresses

Incident Report for Bird

Postmortem

If you maintain your own suppression list

Our cleanup removed these entries from SparkPost's suppression list. If you also keep your own list, you may need to remove affected addresses there too. Which addresses depend on how you build your list:

  • If you copy suppressions from SparkPost (Suppression List API or export): remove entries with source "Bounce Rule" for recipients at privaterelay.appleid.com that were created on November 17 between 13:00 and 21:05 UTC (8:00 AM–4:05 PM ET). For EU accounts, the end of the window is 21:16 UTC (4:16 PM ET). From those times on, SparkPost no longer added these addresses to its suppression list.
  • If you suppress addresses based on bounce events (webhooks or Events API): look for bounce events to privaterelay.appleid.com with bounce class 10 and the response "550 5.1.1
    : user not found", starting November 17 at 13:00 UTC (8:00 AM ET). Apple is still returning some of these errors intermittently, so you should take steps to prevent these additions going forward.
Posted Nov 18, 2026 - 01:06 CET

Resolved

We have finished removing the suppressions created by today's incorrect "user not found" bounces from Apple Private Relay (privaterelay.appleid.com). The affected addresses can receive email again.

We have also made a change so that if Apple returns these errors again, the addresses will not be added to your suppression list. No action is needed from you. This incident is resolved.
Posted Nov 17, 2026 - 23:54 CET

Update

We are continuing to work on a fix for this issue.
Posted Nov 17, 2026 - 23:44 CET

Identified

We have confirmed that this morning's "user not found" bounces for Apple Private Relay (privaterelay.appleid.com) addresses were caused by an issue on Apple's side, and that the affected addresses are valid. Apple has returned these errors in several waves today. Volume is well below its peak, but some are still occurring.

We have begun removing the suppressions created by these bounces. Because of the number of addresses involved, we expect the cleanup to take several hours. Any additional addresses suppressed by this issue will be included in the cleanup. No action is needed from you.

We will post another update when the cleanup is complete.
Posted Nov 17, 2026 - 23:09 CET
This incident affected: Bird Platform.