My UPS blew up this weekend. Arc, flash, pop, burning smell — the works. What followed was two days of waiting and one very satisfying teardown of something I had no hope of repairing.
This weekend, my UPS blew up.
And I do mean blew up. Arc. Flash. POP. Burning smell that hung in the air longer than I'd like to admit.
Also shared on LinkedIn.
The first thought is always the same: did I lose everything?
I didn't. Not my computer, not anything around it. No damage to the wall. The UPS had simply decided it was done — dramatically, and with a light show — but everything connected to it was fine. Once I confirmed that, the panic drained out and something else took its place.
Curiosity.
I'm not an electrical engineer. I have no formal training in anything electrical. I don't speak the language natively. But I've spent enough time in engineering spaces to know that "I don't know how this works" is a starting point, not a stopping point.
So we waited. Two full days, fully unplugged, batteries removed, no residual charge. Then my fiancé and I took the thing apart.
Almost everything was intact. The internals of a UPS are more organized than you'd expect — it's not chaos in there, it's a system. Which made the failure point easy to spot.
One small section, between the transistor and the capacitors, looked like a battlefield. A component had failed, arced back and forth between capacitors, and the resulting short turned the whole unit into an expensive, smoking paperweight. Power surge as the likely catalyst. Age and cumulative wear as the underlying cause — four years old, which shouldn't be ancient, but apparently was enough.
Both Gemini and ChatGPT agreed on the diagnosis when I described what I was looking at. It was a useful reminder that AI is genuinely good at translating "here's what I observed" into "here's what probably happened" — especially outside your own domain.
The UPS is done. There was no saving it, and disassembling it into pieces I can't reassemble made that official.
But that was never really the point.
The point was understanding what happened. Not fixing it. Not salvaging parts. Not proving anything. Just — what went wrong, where, and why.
That's the engineer brain at work, and it's worth paying attention to when it shows up. The instinct to understand a failure — even a failure that doesn't affect you, that you can't reverse, that produces no actionable output — is the same instinct that makes someone good at debugging systems, tracing root causes, and building things that don't fail the same way twice.
You don't always get to fix the thing. But you almost always get to learn from it.
A few things I didn't know before I picked up a screwdriver:
How a UPS actually works — not in theory, but in terms of what's physically inside one and what each section is doing. What a capacitor failure looks like after the fact. That electricity is, in fact, a little terrifying up close. And that curiosity is a skill worth exercising even when there's no practical output on the other side of it.
The UPS is in a bag. The knowledge is not.