Better to be safe than sorry. Due to a critical issue, The First Descendant 1.2.10 Update maintenance has been extended.
The already famous 1.2.10 Update is supposed to drop today. It adds a new Descendant, new weapons, a new Fellow, and a score of other changes and improvements. And, as always, the servers have to go down so the update can be implemented properly. This usually takes a couple of hours, and the devs reveal the timeframes for when the servers will be down. But now, just before the servers were supposed to be back online, Nexon announced that the maintenance would be extended for a couple more hours. In compensation, they will give out free Boosts to all players.
The First Descendant 1.2.10 Update Maintenance Extended
By the original schedule, TFD Update 1.2.10 was supposed to already be up and the servers running, allowing players to experience all that the new features this massive update has to offer. Unfortunately (or fortunately?), the devs came across a critical issue and have decided to extend the downtime so they can properly fix the problem.
According to the official post:
“#PDT 2025.03.13(Thu) 08:00 – During the server maintenance, a critical issue was identified, and to ensure stable service, we have inevitably extended the maintenance period.
We sincerely apologize for the inconvenience caused by the extended maintenance and will strive to complete the work as quickly as possible.
Additionally, as an apology for the extended maintenance, we have prepared four types of 30% boost rewards.
The schedule for distributing the rewards will be announced separately after the maintenance is completed.”
[Reward Items]
Gold Boost 1h (30%)
Kuiper Shard Boost 1h (30%)
Descendant EXP Boost 1h (30%)
Weapon Mastery Boost 1h(30%)
The updated maintenance schedule is:
| PDT | 2025.03.12 (Wed) 22:00 – 2025.03.13 (Thu) 08:00 |
| EDT | 2025.03.13 (Thu) 01:00 – 2025.03.13 (Thu) 11:00 |
| JST | 2025.03.13 (Thu) 14:00 – 2025.03.14 (Fri) 00:00 |
| CET | 2025.03.13 (Thu) 06:00 – 2025.03.13 (Thu) 17:00 |
| AEDT | 2025.03.13 (Thu) 16:00 – 2025.03.14 (Fri) 02:00 |
Just a couple of hours; no big deal. It is better that the issue is identified now than to cause more trouble when the servers are up and running.
