Sysadmins got a day. Network admins got blamed.
When the call freezes, the scanners drop, or the card reader times out at the register, the first sentence in the room is always the same: “the network is down.”
It usually isn’t. But somebody has to prove that in the next four minutes, from memory, while people watch. That person has never had a day of their own.
SysAdmin Day will tell you it covers network admins. It does — the way “the IT guy” covers them. Being included is not the same as being named.
Now they have one. October 8.
10/8, because that’s where we live.
Each cell is one /8 — the entire IPv4 space in 256 blocks.
Lit: 10.0.0.0/8. Block ten. Ours.
10.0.0.0/8 is the largest private range RFC 1918 ever handed out: 16,777,216 addresses that live on nearly every corporate network, lab, VPN tunnel and wiring closet on earth. It is never routed across the public internet, and it is always, quietly, there.
Network administrators spend whole careers inside that block. So the date is the block.
Ten, slash eight. October 8.
Normative details
- Date
- October 8, fixed. Not the second Tuesday of anything.
- Duration
- The full 24 hours, in your own local time zone.
- Scope
- Global. A
/8is the same/8in every office you plug into. - Changes
- None. The date does not move. Please do not write in asking.
The work that made your connection boring.
A good network is invisible. That invisibility is the deliverable — which is exactly why it is so easy to forget there is a person behind it. This day covers everyone who did any of the following, and never got asked about it.
- /24Designed the addressing — subnets that won’t collide with the company you acquire next year, or with whatever your vendor insists on tunneling in.
- RJ45Pulled and terminated the cable, labeled both ends, and drew the diagram that is somehow still accurate three years later.
- 5GHzTuned the wireless — channel plan, power levels, and the roaming that lets you walk to the conference room mid-sentence.
- ACLWrote the firewall rules and, far harder, deleted the ones that stopped being necessary in 2019.
- BGPPeers with your ISP so that when a circuit dies at 3 a.m., the other one carries the load and no ticket is ever filed.
- SFP+Reads the logs nobody asked for and finds the failing optic in the dark, before it takes the site with it.
- 2AMTakes the page, drives in, fixes it, and is back on the morning call like nothing happened.
Low effort. High signal.
There is no gift list on this page. We don’t need a lot of gifts. We need coffee.
Start with coffee.
Not a gift card that arrives next week — an actual coffee, handed to an actual person, on October 8, made the way they take it. This is the whole holiday compressed into one gesture, and it has never once failed.
- 01Be specific. “Thanks” is fine. “The warehouse wifi hasn’t dropped once since you redid it” is the one they will still remember in a year.
- 02Say it where their manager can hear it. Public credit outperforms anything you can buy.
- 03Feed them. Lunch, donuts, tacos, a pizza delivered to whoever is on call. Food shows up; intentions don’t.
- 04Defend an hour of their calendar. One uninterrupted hour is a genuine luxury in this job.
- 05Don’t open a ticket today. If it can wait until the 9th, let it wait until the 9th.
- 06Approve the thing. There is a piece of failing hardware they have been asking to replace for a year. Today is a very good day to finally sign off on it.
A holiday is just a protocol everyone agreed to run.
This one is new, which means right now it exists only if people actually use it. Post what your team did with #NetAdminDay, or skip the internet entirely and walk to the network closet with a coffee. Either is a complete implementation.
SysAdmin Day is the last Friday of July — go celebrate that one too. Thanks, sysadmins. We’ve got it from here.