Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Railway had a similar reliability issue two weeks ago when an AI agent deleted a customer's production database via their API — no confirmation step, no environment scoping. Now this. Both incidents suggest the same pattern: infrastructure decisions made without thinking through failure modes, fixed reactively after damage is done.


I wouldn't blame that incident on Railway.. you can delete your prod database on AWS just as easily with their API.


That incident wasn't Railways fault at all. Don't use AI in your staging and prod tools.


Agree. The author of that article took 0 responsbility and despite the warnings of "Hey, AI with power in prod is a bad idea" thought "This wouldn't happen to me!" and then when it does "HOW COULD IT DO THIS?!"


If everyone can delete your prod database via API or by any other means - you need to sack CTO without severance package.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: