RIIZE’s Shotaro to Skip Macau Concert Due to Sino-Japanese Tensions

Shotaro, the Japanese-nationality member of group RIIZE, will not appear at the scheduled Macau show as part of their “RIIZING LOUD” concert tour. On the 6th, the production company issued an official statement saying, “All relevant parties had completed preparations in advance to ensure all members could attend, but unfortunately, due to unforeseen circumstances, member Shotaro will be unable to participate in the RIIZE concerts scheduled for February 7th and 8th in Macau.”
The reason for Shotaro’s absence has not been clearly disclosed, but it is believed to be related to the recent intensification of Sino-Japanese tensions. As a result of measures imposed by Chinese authorities targeting South Korea and Japan, performances and fan meetings by K-pop idol groups, including those with Japanese members, have been canceled one after another. Specifically, “Dream Concert 2026 in Hong Kong” and MBC’s “Show! Music Core in Macau” were abruptly cancelled, and there has been an increase in cases where Japanese-nationality members of various groups are unable to perform due to visa issues.

Notably, despite having traveled to Macau with the other members, Shotaro will not be attending the concert. The production company requested “the understanding of fans who have long awaited RIIZE” and said, “We sincerely apologize for the inconvenience caused by this change in the concert lineup.”
RIIZE’s “RIIZING LOUD” tour began last July at the KSPO Dome in Seoul and has since taken place in Japan, Hong Kong, Malaysia, Taiwan, Thailand, the United States, Mexico, Indonesia, and other locations. With the Macau show already canceled, the tour still includes performances at Tokyo Dome from the 21st to the 23rd, followed by shows at the Jogyesu Gymnasium from March 6th to 8th.
발행·편집 책임: 국기봉 · KPOP Signal editorialThis article was written with AI from verified source material and passed automated checks before publication. It may contain factual errors. AI disclosure · Request a correction
Comments (0)
No comments yet — be the first to start the conversation.