Apple has announced that the Apple Support Community, a long-standing forum where customers provided peer-to-peer assistance for products like the iPhone and macOS, will permanently close on November 20, 2026. Starting on that date, the platform will no longer accept new posts, effectively ending its role as an active space for community-led troubleshooting.

A collection of various iPhone models in different colors.
The Apple Support Community previously hosted peer-to-peer troubleshooting for a wide range of devices, including the iPhone family.discussions.apple.com

The forum served as a primary hub for users seeking community-led assistance for hardware and software issues across the Apple product lineup.

A series of Mac computers including laptops and desktops.
Community members provided peer-to-peer support for macOS and other desktop software products.discussions.apple.com

The article notes that the forum was a long-standing space for troubleshooting products like macOS.

Transition to Read-Only Access

The Apple Support Community is moving into a permanent read-only state. While the site will remain accessible for users to browse existing threads and historical data, it will no longer accept new questions or posts from the public.

Example Community User Points: LD150 107,652 points; etresoft 60,830 points; Richard.Taylor 25,456 points
Example Community User Pointsdiscussions.apple.com

Chart drawn by HN Digest from figures reported by discussions.apple.com; values are shown as written in the source.

This change effectively freezes the repository of community-generated knowledge. Users who previously relied on the forum to ask real-time questions about hardware or software issues will need to seek alternative avenues for active support.

“The Apple Support Community will permanently close on November 20, 2026.”

— Official Apple Support Community

Redirection to Official Support Channels

Apple is directing users to its official Apple Support site for continued assistance. This move centralizes the support experience, moving away from the decentralized model where users helped one another through community-driven threads.

The official site serves as the primary destination for trusted guidance, ensuring that the information provided to customers comes directly from Apple's verified support infrastructure rather than from other customers.

Impact on Community Contributors

The forum served as a platform where dedicated community members contributed their expertise to help others. These contributors often earned points, leveled up, and achieved 'product specialties' based on their helpfulness and engagement with specific product areas.

The closure ends the active participation of these volunteers. While the site remains available for reading, the mechanism for earning rewards and building a reputation within the Apple ecosystem through peer support is being retired.

Unresolved Questions and Limitations

The source material does not specify the underlying reasons for the closure or the specific timeline for the decommissioning of the backend infrastructure.

It remains unclear what specific features or tools on the official Apple Support site will be introduced to replace the interactive, peer-to-peer troubleshooting experience that the community forum provided.

What Hacker News readers are saying

  • Experience: One commenter shared that they successfully used the forum to find a specific workaround for a hardware connection issue that Apple's official support could not resolve. comment ↗
  • Skeptical: Several commenters expressed frustration with the forum's quality, claiming that many threads were filled with useless information, trolls, or repetitive instructions to contact official support. comment ↗
  • Experience: Another user noted that while the forum was often unhelpful, it occasionally contained buried technical knowledge and specific solutions for OS flaws and third-party app frictions. comment ↗
  • Skeptical: Some users observed that the forum often resulted in long, multi-page threads where users shared the same problem without ever reaching a definitive solution. comment ↗

Summarized opinions from the Hacker News thread, not verified facts. Read the full discussion ↗