Some iPhone users are seeing a persistent red Settings badge tied to an “Activate iCloud Storage” suggestion, even though their iCloud+ or Apple One storage is already active. Tapping through the prompt may open subscription settings without clearing the alert.
The issue appears in multiple user reports on Reddit, including accounts with available storage. Reports cover more than one iOS version, so the evidence does not establish that iOS 27 alone caused it. Apple has not publicly acknowledged a widespread outage or published a specific fix.
This looks different from a genuine storage warning. Users should first open Settings, tap their name, and choose iCloud to confirm that the expected plan and capacity appear. Our guides explain how to check an iCloud backup and review iCloud storage usage before changing an account setting.
Don’t miss the best of The Mac Observer
Set us as a preferred source and our Apple reporting ranks higher in your Google Search results and Discover feed — one tap, no account changes.
A reported workaround has an important tradeoff
Several affected users say signing out of Media & Purchases, waiting briefly, and signing back in removes the badge. That option is under Settings > [your name] > Media & Purchases. It is not the same as signing the entire Apple Account out of iCloud.
However, this is a community workaround, not an Apple-confirmed remedy. Signing out of Media & Purchases can remove downloaded music, podcasts, or video that is available for offline use, requiring it to be downloaded again. Users who depend on offline media may prefer to wait or contact Apple Support.
Apple’s support guidance for iCloud notices recommends following the Settings prompt and authenticating when asked. If the alert remains after the account’s plan and payment status are verified, Apple Support can check for account-side problems.
Do not buy a second storage plan merely to clear the badge, and do not delete backups unless the storage screen confirms space is actually exhausted. The limited reports point to an account-state or notification glitch, but its cause and scope remain unconfirmed.
Discussion