In this update
On October 21–22, 2026, AnimGen experienced a prolonged interruption affecting uploads, animation generation, previews and downloads. Some of you could not retrieve work you had already created. We are sorry for the disruption and the time you lost.
We have restored the affected storage access and verified downloads and generation. Compensation credits have already been issued to all paying users, with details available in their in-app notices.
This update reflects our checks through October 22, 2026, 15:21 UTC. The security review remains open. All times below are in UTC.
What interrupted the service
Our infrastructure provider, Railway, disclosed a security incident on October 21 and reset storage access credentials as a precaution. During this period, the platform restricted deployments. This prevented us from immediately deploying the changes needed to restore service and prolonged recovery. Railway has published a security disclosure and incident timeline.
At around October 21, 22:42 UTC, the credentials for storage used by AnimGen were reset. Running services still held the old values, so requests to read or write assets began failing authentication. Our logs confirmed storage-signature errors on upload, preview and download paths. Animation processing also depends on that storage for inputs and results.
Keeping AnimGen usable is our responsibility. The recovery took too long, and we are sorry we could not get you back to work sooner.
How recovery progressed
| Time, UTC | Verified milestone |
|---|---|
| October 21, approximately 22:42 | AnimGen's storage credentials were reset. This event is also the reference point for the compensation calculation. |
| October 22, 06:29 | Railway announced that builds were available for Pro workspaces, including ours. |
| October 22, 09:55–10:14 | The replacement API read an existing asset successfully; the same download was then confirmed usable from a signed-in account. |
| October 22, 10:47–10:53 | Generation processing resumed. An existing user task completed and its output was verified. |
| October 22, 12:22 | A fresh backup completed successfully; the daily backup schedule was restored. |
| October 22, 15:14–15:21 | Customer compensation was credited, in-app notices were delivered, and an independent reconciliation passed. |
These are recovery milestones, not a measurement of one continuous, site-wide outage. Different functions recovered at different times. Failed tasks were not automatically rerun.
Who received compensation
This batch covers customer accounts that had a valid payment history and had not entered account deletion when the recipient list was checked on October 22 at 10:54 UTC. It includes subscription customers, credit-pack customers and customers whose subscriptions are on hold. Recent usage was not required.
The compensation has already been added to eligible accounts. There is no application to submit and no additional purchase required.
| Rule | How it was applied |
|---|---|
| Amount | The greater of 100 credits or the account's net credit usage in the preceding 7 days. |
| Usage period | October 14, 2026, 22:42 UTC to October 21, 2026, 22:42 UTC, displayed to the minute. |
| Net usage | Credits consumed in that period, less refunds recorded by the calculation snapshot on October 22 at 11:22 UTC. Usage of both purchased and granted credits counts. |
| No recent usage | Eligible accounts with zero usage still received 100 credits. |
| Expiry | 365 days after the credits were added. Each notice and credit record gives the exact expiry time. |
| Delivery | Account credit balance plus an in-app notice. No compensation emails have been sent. |
For example, net usage of 0 or 72 credits results in 100 credits of compensation; net usage of 300 results in 300. The 100-credit minimum is not an additional amount on top of usage. Later refunds do not automatically recalculate this completed batch.
The compensation was credited on October 22, 2026, at 15:14:04 UTC, with expiry on October 22, 2027, at 15:14:04 UTC. In-app notices have been delivered and the credit grants have been checked.
This compensation consists of AnimGen usage credits. It did not change payment records, orders or subscription duration.
How to check your compensation credits
Sign in and open your credit history. The in-app notice lists your calculated usage, compensation amount, crediting time and expiry. Notices are available in English, Simplified Chinese, Traditional Chinese, Japanese, Korean and German.
For an older download link that no longer works, reopen the asset in AnimGen and request a fresh link. A link signed before the credential reset can remain invalid after the service recovers. Check a failed task's status and credit history before starting it again: a new generation may consume credits.
Security review status
Functional recovery does not establish whether user data was affected. We are not treating this notice as the end of the security investigation. If we confirm an impact on your account or data, we will notify you separately.
Thank you for choosing AnimGen and for your patience. These credits cannot return the time you lost.
Erdeni and the AnimGen team