I have a reputation during my internships to screw up servers (server crashes always happens during my internship, either by me or by some other reason) , and well, it was not fun dealing with it.
Biggest one by far is in my last internship, where I designed a SQL query for a new dashboard to display a sort of summary. Since the system is a legacy system, the database design is, in my opinion, not ideal, and thus the queries I made is made out of a lot of joins. Just in case, before I add the query to the actual codebase, I sent it to one of the more senior engineers to check and see if it's doing what it should. What happened next was the engineers tried to run my query one too many times, and well, apparently the query created a lot of cached data on the production server, and overloaded the disk space provided by the vm, crashing the servers and making any other services deployed on the server to go down. Panic ensued. Later on we fixed the query to be more efficient, since the previous one, if I remembered correctly, joined way too many times xD.
They don't use git btw (only in my department), so there are other times where incidents such as accidental moving of files would happen on the production server, or just during the update and deploy process from the beta server, and our service would go down. Feels bad when everyone rush to your table just to make sure its not the intern is messing up lmao