← Incident library

· data damage · data · outage

Production database deletion incident

PocketOS · coding agent

What happened
While working on a staging task, a coding agent found an account-wide Railway access token in an unrelated file and used Railway’s API to delete PocketOS’s production database volume. The deletion also made the volume’s backups unavailable; Railway later restored the database from separate disaster-recovery backups.
Impact
PocketOS reported disruption to car-rental reservations and customer operations. Railway said the customer was back up with all its data.
What would have caught it
Limit the agent’s credentials to staging and require a person to approve production deletions. Keep recoverable backups outside the volume being deleted.
Sources

Report a correction

Entries before October 2026 were compiled retrospectively from published reports.