The first morning back after a holiday break is supposed to feel like the building stretching its limbs.
Lights warming up.HVAC groaning awake.Coffee drifting through stale air.A sense of “we survived another year; let’s try not to burn anything down.”
Instead, I unlocked the VCIM office at 7:02 a.m. and walked into the kind of silence normally reserved for suspense movies and abandoned warehouses.
The wrong kind of quiet.The “something fundamental is broken but hasn’t started screaming yet” quiet.
I sat down, hit the power button on my workstation, and waited for the usual startup sequence.
Fan.Fan.Click.Monitor.Desktop loading.
Then:
NO NETWORK CONNECTION
A little red X over the network icon stared back at me.
I stared at it.
It stared louder.
“No,” I told it. “Absolutely not.”
I opened a command prompt and pinged the firewall.
Request timed out.
I pinged the core switch.
Request timed out.
I pinged the domain controller.
Request timed out.
My phone buzzed.
7:04 a.m. — DISPATCH:“Morning, Howard. Not to rush you, but CAD won’t load. Neither will email. Or the map. Or the ticket system. Or… anything?”
I typed:
“Working on it.”
Another buzz:
7:04 a.m. — ADMINISTRATOR:“Is our internet down? We can’t log into the agenda software.”
Another:
7:05 a.m. — SHERIFF McCREADY:“Everything says ‘cannot connect to server.’ If that’s planned, fine. If not, fix it.”
I hit send on my first reply and grabbed my tool kit.
The hallway lights flicked on as I passed, startled to see a human. The HVAC kicked in somewhere overhead, gently exhaling lukewarm encouragement.
The building was waking up.
The network was not.
The server room should have felt like opening a freezer full of angry bees. Instead, the air was room temperature.
That was not good.
The firewall was up.The core switch was up.Both flashing contentedly, completely unaware of the ongoing disaster.
Everything behind them was dead.
The tale has been taken without authorization; if you see it on Amazon, report the incident.
No VM hosts.No storage array heartbeat.No phone system.No access switches.No WiFi controller.Nothing.
I turned to the UPS.
It was powered on, humming, cheerful.
Its display read:
LOAD: 0%OUTPUT: OFF
I closed my eyes.
Someone had pressed the Output Off button.
Over the break.
Despite the label on the front of the rack that said:
DO NOT TOUCH — ASK HOWARD
Beneath it, in handwriting I recognized as belonging to someone in Facilities, was a helpful addition:
(EXCEPT THIS BUTTON)
The arrow pointed directly at the “Off” key.
Of course it did.
I pressed Output On, and the UPS made the quiet, satisfying click of systems returning to the land of the living.
Power surged into the racks.
Access switches lit up.Distribution switches blinked.Servers rumbled.Storage arrays spun.Phones beeped awake like startled birds.
My tablet chimed as ping responses filled the screen.
“Welcome back,” I told the equipment.
It ignored me, because it has taste.
I stepped into the hallway and immediately received three more texts.
7:10 a.m. — FRONT DESK:“WiFi says ‘no gateway.’ Is that bad?”
Me:“Tell them to refresh their browser.”
7:11 a.m. — DISPATCH:“CAD’s back! You’re a magician.”
7:11 a.m. — ADMINISTRATOR:“Agenda system works again. New year miracle.”
Miracle is a strong word.
“Preventable” is better.
I walked back to my desk just as Jake arrived with the frantic energy of someone trying very hard to look like he wasn’t late.
“Happy new—whoa. Why do you look like that?”
“The network was down,” I said.
“Oh no,” he whispered, as if learning a friend had been hospitalized. “How bad?”
“UPS output off,” I said. “Everything behind it was dark.”
“Oh no,” he whispered again, louder.
“Dispatch is back up,” I said. “Email is up. Phones are up. Crisis technically averted.”
He dropped his backpack and sat. “We survived the break! That’s great! So now we have a nice normal Monday.”
My email finished loading and dumped a backlog of messages onto the screen like a dam bursting.
Jake glanced at it. “That seems like… a lot.”
“There are no happy holiday emails,” I said. “Only warnings wearing festive fonts.”
He pulled up his own inbox and relaxed when it didn’t explode.
“So that’s it?” he asked. “Network’s up? Everything’s fine?”
The universe, hearing him, decided to intervene.My phone rang.
Not the normal ringtone.
The other one.
The red line.
I answered it.
“VCIM.”
“Howard,” said the Administrator, sounding like a man who had already given up on the day. “Happy new year.”
“That depends on your definition,” I said.
“Is our network up?” he asked.
“Yes,” I said. “Fully restored.”
“Okay,” he said. “Then the problem is… email.”
I exhaled through my nose. “What kind of email?”
“The kind where Legal forwarded it to me with the subject line ‘Please address immediately.’”
Jake winced.
Administrator continued, voice tight:“There’s a statement from BiOnyx. About the BT4s. And a follow-up. And… language in it I do not like.”
I already felt the headache forming. “I understand.”
“I need you and Jake in the conference room in fifteen minutes,” he said. “Legal and Risk will be there.”
“Understood.”
“And Howard?”
“Yes?”
“Please tell me the network will stay up.”
“For the moment,” I said truthfully.
He hung up.
I set the phone down carefully.
Jake watched me like I’d just read my own autopsy.
“Scale of one to ten,” he said. “How bad?”
“Somewhere between ‘forgot the WiFi password’ and ‘the county attorney has printed screenshots.’”
Jake made a small wounded noise. “BiOnyx?”
“BiOnyx,” I confirmed.
He pointed toward the yard cameras. “But the Hoppers are fine! They’ve been still for two weeks! Rusty hasn’t moved!”
“I know,” I said. “And I suspect that will be part of the problem.”
I stood.
“Come on,” I said. “We’re expected.”
He grabbed his notebook. “Do you think they’re going to ask if we can run without the Hoppers again?”
“Oh,” I said, “I guarantee it.”
He groaned. “Happy new year.”
I opened the conference room door.
“Try not to say that in there,” I told him.
We walked in.
And the meeting did not look festive.
Not even a little.