CompaniesMessageBird (Bird)Incidents
MessageBird (Bird): Invalid "user not found" bounces from Apple iCloud / Private Relay addresses
Affected components: Bird Platform
Timeline of updates
- 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. - identified
We are continuing to work on a fix for this issue.
- 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. - 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.
Changes Rewindex caught on this incident
- Incident updated: Invalid "user not found" bounces from Apple iCloud / Private Relay addresses
- Incident updated: Invalid "user not found" bounces from Apple iCloud / Private Relay addresses
- Incident updated: Invalid "user not found" bounces from Apple iCloud / Private Relay addresses
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
63bdb60b24f40f10…Version 2 captured
In the 2026-11-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
373602d50984f01e…Version 3 captured
In the 2026-11-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
723a237f1daf8e0e…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.bird.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by MessageBird (Bird), started 2026-11-17 22:09 UTC, resolved after 46 min, 4 update(s); edited after publishing.
- Title
- Invalid "user not found" bounces from Apple iCloud / Private Relay addresses
- Vendor
- MessageBird (Bird)
- Date
- URL
- https://rewindex.com/company/messagebird-bird/incidents/9ldnf5hggdpk
MessageBird (Bird) profileRecent MessageBird (Bird) incidentsAll outages on November 17, 2026MessageBird (Bird) in November 2026MarkdownJSON