Cygames Scheduled the Outage for the Patch, Then Moved It Earlier

Cygames did not bury the cause in "emergency maintenance." The posts named PHP.

On 21 October the company said Umamusume: Pretty Derby, Granblue Fantasy, Shadowverse: Worlds Beyond, and other live titles would go down so the servers could be made safe. The Umamusume account told players they would not be able to start or play during the work. Famitsu reported the original window as about 23:00 Japan time on the 21st, lined up with the PHP fix publication expected that hour. Granblue was planned through 07:00 on 22 October, with a warning the end time could move. Umamusume and Shadowverse did not publish an end time.

Then the start moved. A later Umamusume notice pulled maintenance forward to about 22:00, and said it might move again. That is what a broken embargo looks like from the operator side. You planned the outage for the patch. The patch, and the exploit talk, showed up early. You start early.

One company, three clocks

This is a useful contrast with Saylor, which had one host and one overnight window, and with FFXIV, which froze new logins and left existing sessions alone. Cygames had several games on the same language bug and did not pretend they would return together. Granblue got a planned end. The others got "we will tell you." That is better than a fake 7:00am that slips for six hours while players refresh a status page.

The fix they were waiting on is the same four releases as everyone else: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35, from the 21 October security release. A game server that still answers on an older worker after that release is not "in maintenance." It is late.

If you operate more than one PHP front, write the notice per product. Shared cause, separate end times, and a sentence that the start can move if the patch moves. Players can forgive a dark game. They do not forgive a countdown you already knew was fiction.

Sources: Famitsu, 21 October 2026; PHP advisory.