Hey, I'm Umutcan.

I work on networks, infrastructure, packet processing and DDoS mitigation. Basically, I spend a suspicious amount of time convincing packets to go where they are supposed to go, and convincing garbage traffic to go bother someone else.

What I Do:

Network Engineer — routing, policy, peering, traffic engineering and asking “who the hell announced this?”
Infrastructure — Linux, monitoring, automation and services that love failing at the worst possible time.
DDoS Mitigation — filtering nonsense, keeping real traffic alive and occasionally negotiating with DPDK like it owes me money.
Debugging — graphs are nice, logs are suspicious, counters usually snitch first.

Things I Like:

JUNOS syntax. It looks weird until it starts making too much sense.
BGP, because apparently the internet needed a trust-based system with commitment issues.
Linux systems that were “temporary” three years ago and are now critical infrastructure.
Clean configs, boring forwarding paths and traffic that does not act like it was raised by wolves.
Breaking things in lab before production finds a more expensive way to teach the same lesson.

Useless Facts:

I used to develop Resurrection Remix ROMs and turn Android phones into hand warmers. Now I use an iPhone and live inside the Apple ecosystem. Character development, or betrayal. Still investigating.
If something breaks, it is probably DNS, MTU, the vendor, or me. Spoiler: it's always DNS.
“Just restart it” is not engineering. It is, however, annoyingly effective sometimes.
Some of my best work started with “this should be simple” and ended several hours later with a personal grudge.

Want to talk about networks, DDoS, infrastructure, old Android ROM trauma, or why a “temporary workaround” is never temporary? [email protected]