Manon deletes another KATSEYE Instagram post as hiatus continues
Manon deleted second post related to KATSEYE from her Instagram, marking 60th day of ongoing hiatus

Manon has deleted a second post related to KATSEYE from her Instagram account, coinciding with the 60th day of her unexplained hiatus.
The post, which was previously visible on her profile, disappeared without notice, marking the second time KATSEYE-related content has been removed during her absence.
The timing has drawn attention, as it aligns exactly with two months since she last appeared publicly or posted updates.
The post was removed on the 60th day since her withdrawal from promotions was confirmed on February 21.
It was announced that Manon would temporarily step back to focus on her health, a decision supported by both HYBE and Geffen Records.
In a joint statement, they said, “We fully support this decision. KATSEYE remains committed to showing up for one another and for the fans who mean everything to us.”
Manon also addressed fans directly, stating, “Sometimes things unfold in ways we don’t fully control, but I’m trusting the bigger picture. Thank you for standing by me,” and, “I love you endlessly and can’t wait to see you again.” She added that she is “healthy” and “taking care of myself”.
Despite these updates, her continued absence and the removal of KATSEYE-related posts have drawn attention online. This latest deletion marks the second instance of such activity during her hiatus, with fans noting the timing and pattern.
Reactions across social media have been mixed. Some fans have expressed concern and continued support, while others have questioned whether the removal of group-related content signals changes in her role. However, no official clarification has been provided regarding the deleted posts.
KATSEYE has continued scheduled activities as a group during this period, with no confirmed timeline for Manon’s return.


















COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ