missing ip in egress ip ranges

I'm using this list of ingress ranges to identify apple private relay IPs:

https://mask-api.icloud.com/egress-ip-ranges.csv

lately I had issues because of private relay IPs that are missing in this file like: 172.56.160.23 and 172.56.161.27.

Is there any another way to detect private relay ip? why are they missing?

MacBook Pro 13″, macOS 12.5

Posted on Aug 7, 2023 5:04 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 7, 2023 7:55 AM

For those others reading along here, some background on Apple iCloud+ Private Relay:

https://www.apple.com/privacy/docs/iCloud_Private_Relay_Overview_Dec2021.PDF


And for those running networks and servers:

Manage iCloud Private Relay for specific websites, networks, or system settings - Apple Support


If you have detected Private Relay egress addresses you suspect are omitted from the list, contact Apple Support.


More generally, options are to remove or rework the existing geolocation- or blocking-related processing assuming that list can drift from reality, or to assume that Apple will keep that list current as egress ranges are changed or added or removed. I’m sure neither is a preferable choice for whatever you’re doing here, too.


As for various “why?”’s that can exist or can arise here, we don’t know. We’re other users and some are other third-party developers, and not Apple.

1 reply
Question marked as Top-ranking reply

Aug 7, 2023 7:55 AM in response to shoshi288

For those others reading along here, some background on Apple iCloud+ Private Relay:

https://www.apple.com/privacy/docs/iCloud_Private_Relay_Overview_Dec2021.PDF


And for those running networks and servers:

Manage iCloud Private Relay for specific websites, networks, or system settings - Apple Support


If you have detected Private Relay egress addresses you suspect are omitted from the list, contact Apple Support.


More generally, options are to remove or rework the existing geolocation- or blocking-related processing assuming that list can drift from reality, or to assume that Apple will keep that list current as egress ranges are changed or added or removed. I’m sure neither is a preferable choice for whatever you’re doing here, too.


As for various “why?”’s that can exist or can arise here, we don’t know. We’re other users and some are other third-party developers, and not Apple.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

missing ip in egress ip ranges

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.