If you're using this on an iPhone, the failure is quite non-informative. Trying to browse to a URL looks like you failed to input anything and it just falls to a blank screen.

On the Mac, you'll see the message "Safari can’t open the page. The error is: “The operation couldn’t be completed. No such file or directory” (NSPOSIXErrorDomain:2)".

It should fail soft - e.g. warn user that Private Relay is not available, but don't block connectivity.

This really isn't a client side issue, but the work-around is to disable the feature - which likely means that once service is restored...

Yes, it's like that.

Disagree. That is not what I would expect from a privacy perspective. What if you're in the middle of a browsing session you'd prefer to be private?

10 hours since this outage began.

There are customers out there with zero access to the internet because of this, and they don't know why (there is no error message on iOS.)

Absolutely abhorrent response time from Apple here, this is SEV0-worthy.

On iOS there was a message "iCloud Private Relay will be available tomorrow" - and things seemed to keep working for me at least.

On macOS it took 16 hours (!!) before a message finally popped up that said "Private Relay Unavailable - Private relay will automatically turn back on when it is available."

Claims to be back after 17+ hour outage. You can do better, Apple.

edit: still not working; presumably it will soon however.

“Your iPhone will be able to use Private Relay again tomorrow.” - Notification I received ~30 minutes ago