The Ghost in the Routing Table

I spent three hours yesterday watching a black-and-white anime girl dance across a command prompt, and I don't think I've ever felt more connected to the raw physics of the internet. We usually treat the web like a finished product—a slick, frictionless surface of glass and pixels—but the "Bad Apple but It's Traceroute" project peels that skin back. It uses the Internet Control Message Protocol (ICMP), the diagnostic heartbeat of the web, to draw images. If you aren't a networking nerd, think of it this way: instead of painting on a canvas, the artist is timing the echoes of tennis balls thrown against a series of walls to create a melody.

It works by manipulating the Time to Live (TTL) values of packets. Normally, when you run a traceroute, your computer sends out a probe that dies at the first router, then the second, then the third, reporting back the IP address of each hop. In this project, the creator set up a series of virtual hops so that the IP addresses returned aren't just random strings of numbers—they are carefully curated strings that, when viewed in a terminal, form the ASCII art frames of a 2009 Japanese music video. It’s a performance that exists only in the transit. It is art made of lag.

Why We Are Obsessed With Technical Limits

There is something deeply human about finding a rigid, boring system and forcing it to be beautiful. The "Bad Apple" video has become the "Hello World" of creative engineering; people have ported it to everything from graphing calculators to the internal sensors of a Tesla. But the traceroute version feels different because it isn't inhabiting a device. It’s inhabiting the distance between devices. It’s using the 1981 IPv4 specification as an aesthetic choice, which makes me wonder: why are we suddenly so nostalgic for the internal organs of the web?

Maybe it’s because the modern internet feels too curated. Everything we see now is mediated by algorithms and high-resolution wrappers that hide the "how" of the thing. When you see a video rendered through traceroute, you’re looking at the raw plumbing. You’re seeing the latency, the packet loss, and the hop-by-hop logic that usually stays buried under layers of UI. It’s like discovering that the pipes in your house can play the flute if you turn the taps on in a specific order.

a vintage server rack with blinking green lights in a dark room
Photo by panumas nikhomkhai on Pexels

The Architecture of the Periphery

I’m fascinated by this idea of the "Computational Periphery." For decades, we’ve focused on the edges of the network—the smartphones, the laptops, the VR headsets. That’s where the "content" lives. But this project suggests that the transit itself—the fiber optic cables under the Atlantic, the grey boxes in data centers, the protocols that negotiate how data moves—can be a medium. It treats the infrastructure not as a utility, but as a stage. It turns the boring, functional reality of a 64-byte packet into a brushstroke.

What happens when we stop looking at the screen and start looking at the wires? This kind of "Low-Level Aestheticism" reminds me of early radio enthusiasts who would tune into the static between stations just to hear the texture of the atmosphere. There’s a specific kind of wonder in realizing that the 13th hop in a network path isn't just a gateway in a suburb of Virginia; it’s a coordinate in a map of a digital dance. It’s ephemeral. If the server goes down, the art disappears. You can’t download a traceroute; you can only experience it while it's happening.

  • It challenges the idea of data as a static object.
  • It forces us to acknowledge the physical geography of the web.
  • It turns a diagnostic tool into a narrative device.

What This Actually Means

We are entering an era where the "invisible" parts of our lives are becoming the most interesting places for subversion. As our software becomes more locked down and our hardware becomes harder to repair, the only place left to play is in the protocols. If you can’t change the app, you change the way the data reaches the app. This traceroute performance is a reminder that the internet is still just a collection of machines talking to each other, and those conversations don't have to be strictly business.

It makes me wonder what else is hiding in plain sight. If we can make music videos out of routing tables, what can we do with power grids? What can we do with the metadata of our GPS coordinates? There is a whole world of "ambient data" that we treat as exhaust, but to a certain kind of mind, that exhaust is the fuel for something entirely new. We’re moving past the age of the "user interface" and into the age of the "infrastructure interface."

Ultimately, "Bad Apple but It's Traceroute" is a love letter to the complexity of our world. It’s a way of saying: "I see the system, and I can make it sing." In a world that feels increasingly automated and out of our control, that's a pretty comforting thought. We aren't just passive consumers of the network; we are the ghosts that can haunt it into being something beautiful.

Quick Answers

Is this actually a video file?
No, it’s a sequence of IP addresses being reported back to your computer in real-time. The "video" is reconstructed frame-by-frame by your terminal as it queries a specific server.

Does this slow down the internet?
Technically, it creates a tiny bit of traffic, but it’s essentially a drop of water in the ocean compared to a single Netflix stream. It’s a very lightweight use of ICMP packets.

Why do people keep using the "Bad Apple" song for this?
It has become a benchmark for technical stunts because its high-contrast, black-and-white animation is perfect for testing the limits of low-resolution displays or, in this case, ASCII text.