The Internet

Internet \in"ter*net, n. A deeply misunderstood technology upon which we increasingly depend

Julian Oliver & Danja Vasiliev

The Internet is often described as a "cloud", an amorphous entity that is everywhere and nowhere at the same time. This sort of magical thinking does us a disservice as netizens. If we hope to do meaningful work on/about the Internet that also speaks to living in a world mediated by the Internet, it would help if we knew what the Internet really is.

We can approach answering this question from a number of different vector views: its politics, its culture, its history (see links/references at the end of these notes for more) etc. In this lesson we'll be exploring the Internet's infrastructure and technical protocols, in the interest of understanding what it literally is. The Internet is actually a very real, very physical thing. You can touch it, you can smell it, it has a "delicious old odor" as Leonard Kleinrock put it. The Internet exists in time and space, in this workshop we'll illustrate this by following a piece of our data—an Internet packet—on its journey from our computer to a server elsewhere on the Internet. Along the way we'll make various cultural, political and aesthetic observations and reference works by artists, activists and hackers informed by these perspective.

the globe

Interactive 3D map of the Internet

The Internet is the great masterpiece of human civilization. As an artifact it challenges the pyramid, the aqueduct, the highway, the novel, the newspaper, the nation-state, the Magna Carta, Easter Island, Stonehenge, agriculture, the feature film, the automobile, the telephone, the telegraph, the television, the Chanel suit, the airplane, the pencil, the book, the printing press, the radio, the realist painting, the abstract painting, the Pill, the washing machine, the skyscraper, the elevator, and cooked meat. As an idea it rivals monotheism

Virginia Heffernan

local networks

The Internet is a network of computer networks. A computer network is 1 or more computers (laptops, phones, tablets, servers, smart fridges, etc) connected together via physical cables or wireless signals such that they can exchange data. There are a few different ways of creating computer networks but the most common is by using a network router.

Unless you're on a desktop computer connected to an ethernet cable, it's most likely that you're connected to your local network (through a router) over WiFi. Data sent to and from the network's router is transmitted over the air, through the electromagnetic spectrum. These are frequencies of light, invisible to our eye, which can be transmitted and detected by the WiFi antennas in our devices and router.

Electro Magnetic Spectrum

When you connect to a router managing a local network, it assigns you an Internet Protocol address, or IP address. If you are currently connected to a network you can find your local IP address by following these instructions for Window, Mac or Linux.

You can send HTTP requests (aka web requests) using a web "client", like your web browser, by entering a URL beginning with the IP address of another computer on your local network running a web "server".

You can send a request for a specific file by specifying the file's "path" in the URL following the destination computer's IP address.

Assuming the computer you sent this HTTP request is running a server, it will then send that file, in the form of an HTTP response, over the air to the router which will pass it along to your computer which will display it in your browser. If the URL generating your HTTP request contained a path to an HTML file, then your browser will "render" (aka display) the HTML code in that file as a web page (we'll discuss HTML in a bit more depth in another lesson).

Log Jammer by Allison Burtch

Today, nearly everywhere we go, we're surrounded by data floating through the electromagnetic spectrum all around us. The devices we carry in our pockets, whether we're actively using them or not, are in constant communication with the Internet, persistently sending and receiving data through the air, whether at home, at work, riding the train or strolling through the park. This is why artist Allison Burtch created the Log Jammer, a log which contains a custom computer and antenna which Burtch created which "jams" all the wireless communication in the area, to provide "a safe space in the woods, a right to be alone".

In my WiFi Wizardry notes, you can explore other projects like this one by artists exploring the data floating all around us and engaging with the electromagnetic spectrum as an artistic medium.

Our local network, and by extension all of our computers, become a part of the Internet the moment our router connects to a cable that is itself connected to the rest of the Internet, usually provided to us by our Internet Service Provider, or ISP. But not all local networks are connected to the Internet, some remain "offline".

It's easy for many of us to take our connection to the Internet for granted, but only ~50% of the planet have access to the Internet. The gap between those with and without access is often referred to as the digital divide. But this doesn't mean that the other half of the world is devoid of computer networks. In countries like Cuba, where Internet access is limited/restricted due to economic and political reasons, enterprising netizens have taken it upon themselves to build their own local networks.

Inspired by these sorts of DIY networks, artists like Aram Bartholl, Dennis de Bel and Roel Roscam Abbing have created their own "offline" network projects.


Meshenger by Dennis de Bel and Roel Roscam Abbing,

Dead Drops

Dead Drops (a peer-2-peer "offline" network) by Aram Bartholl

a network of networks

As mentioned earlier, the Internet is a network of networks. It happens to be the largest network humanity has ever produced, wrapping itself around the entire planet. Rather than using WiFi or cats to transfer data between routers and computers, these networks are predominantly connected together using cables. When you send an email, share a post on social media, watch a stream or visit a web page, data is being sent back and fourth (nearly at the speed of light) between your computer and another which may be halfway across the planet.

Visit any website in your browser, right-mouse click the page and "View Source." This is the HTML code, the file itself, that just traveled the world to reach your computer, but where did this data come from? Let's map the journey it took across the Internet...

As mentioned earlier, when you sign on to a local WiFi (or ethernet) network the router assigns you a "local" IP address, the router itself has a public IP address, this address is a unique address on the Internet. When your request packets travel over the air from your computer over to your router, the IP address in that data packet changes from your local IP address to your router's public IP address, this way the HTTP response sent back from the server knows to find it's way back to you over the Internet. If you'd like to see what your public IP address is (ie. your router's IP address) do a web search for "what's my IP address"

Every computer connected to the Internet has an IP addresses, including the computers running the servers which host the files, and other data, we experience on our devices, like the HTML file we just looked at when we viewed the source of a website.


We rarely type IP address of these other computers into our browser address bars, this is because a server could optionally register a "domain name" on the Internet's Domain Name System (DNS). This is like a giant phone book (or books) for the Internet that match names to numbers. Here you can find a list of all the The Root Servers for the DNS, and here you'll find an interactive map of where they're all located.

You can look up any domain name's IP address by using the nslookup command in your terminal.

If you're using a Mac or Linux computer, open your Terminal application (or the Command Prompt on Windows) and run nslookup replacing "" with your website.

Once you know your destination IP address, you can use that to find the server's physical location.

Do a web search for "IP address to location" or "IP to geo" and you'll come across various different services that can translate an IP address into GPS coordinates. I prefer to use because it not only gives me the GPS coordinates, but also tells me the name of the organization who owns that IP address (a helpful piece of information when creating your travelogue). Use an online mapping service to navigate to those GPS coordinates and try to find where exactly the site is hosted. The GPS coordinates aren't always precise, it'll get you to the general area, but you'll likely need to search the map for "data centers" in the area to try and find the building where your identified organization (hosting the website) is a tenant at. Large data centers often (though not always) have many different companies renting space in the data center for their servers. This means the building your looking for might not have the same name as the organization for which the IP address belongs.

Citizen Ex

Citizen Ex by James Bridle

Directions ot Last Visitor by Charles Broskoski

The sever hosting the web page you requested may be in a part of the world you hadn't expected, having traveled the distance to your computer faster than any boat, train or plane could have. The speed of travel can often make the Internet feel smaller than it is, everywhere and nowhere. Artists like James Bridle and Charles Broskoski (linked above) have created projects that help bring this to light, and raise questions about the Internet which are only possible when we see it for what it actually is.

On a sunny morning at 7:45:03, one Internet packet is born. 60 bytes weight, with just one simple mission in life – to get to the place called Even though this does not sound like an exciting mission in life, things that happen in the next 1 second are pretty exciting. His journey starts with a fast 7ms jump, 5 meters away to the box called home router. Over the attic, where he passes through the switch where all the cables from the building meet, he jumps down to the street and into the underground cable that brings him to the main city router in Novi Sad. With a speed of 30.600.000 km/h he runs for 10 ms to Belgrade, to the SBB TelePark building.

Next we'll chart the journey from our IP address to the IP address of the computer hosting the website we requested.

On a Mac or Linux computer, open your Terminal again (or the Command Prompt on Windows) and run traceroute -I (or tracert on Windows), replacing "" with your destination's IP address.


The traceroute application will start to list the IP addresses of each "hop" (or router) your packet takes on it's journey. Once you have your list of hops, look up each IP address like you did before to find the GPS coordinates of each and find them on the map.

It's important to note that the traceroute application isn't perfect. It doesn't actually trace a direct route so much as send "pings" (a tiny packet to a router that echos back) to and from each router along the path. Because your packet doesn't necessarily take the same exact journey each time (every new Web request finds the quickest path across the Internet to it's destination at that moment) the list of IP address returned by the traceroute in a way reflects a combination of alternative routes the packet may have taken. So, what you'll need to do is run the traceroute a few times (maybe 4 or 5) keeping track of the list of IP addresses and their corresponding GPS coordinates. Compare the different results, disregard any anomolies (IP addresses that only ever showed up once) and make your best guess as to what a likely journey may have been.

Between each "hop", each stop at along the packet's journey, the data travels across cables, initially probably the cables of your local Internet service provider (or ISP), like Comcast for example...


As mentioned earlier, not everyone on the planet has access to the Internet for a variety of reasons. In this country, the reason is often financial. Unlike other utilities and services the public depends on, access to the Internet in the United States is almost entirely handled by private corporations. The profit motive driving the expansion of these networks often disincentivizes those companies from connecting parts of the country which are more rural or poor. This has the effect of negatively impacting already marginalized communities, because "having a slow connection can mean increased health risks, a limited education or having less money", as explained in the video below.

Fortunately, there are efforts like the Equitable Internet Initiative in Detroit which take a community focused approach to closing the digital divide through community owned and operated ISPs.

Unless the website you've requested is on a computer connected to the same ISP you're connected to, your request packet will likely need to hop from your ISP's network onto another network.

Many of the subsequent IP addresses along the way are likely going to be Internet exchange points or "colocation centers", or "carrier hotels".

These are all names for different types of large data centers where different networks (like your ISP) meet and connect with each other to exchange Internet traffic. Use those terms (in addition to "data center") to try and find the buildings (near the GPS coordinates) where the hops might have taken place.

At this point in our data packet's journey it has likely traveled through a handful of networks owned and operated by different individuals and organizations. It started on your local network, operated by whoever owns the WiFi router you're connected to, before being passed along to your ISP, which might be your university, or maybe a non-profit (like the Equitable Internet Initiative) but is most likely a private company running sub-par equipment and providing the minimal viable service like Comcast, Verizon or AT&T. If there's ever a hop between two different continents, then it's likely your packet fount it's way to a shoreline, like this one in Canada...

coastline landing cable

"This modest indentation on the Canadian coastline is a major Internet landmark, a sort of Ellis Island of the Web: It’s where a submarine cable owned by Hibernia Atlantic comes ashore."--Andrew Blum

Like the previous hops in our data packet's journey, these landing point stations are also owned and operated by yet another set of organizations. It's at these "landing points" that our data packet leaves the "dry" network and hops onto a "wet" network. These are transoceanic networks made of fiber-optic cables many miles long, resting on the ocean floor. A significantly large portion of our Internet data travels through the ocean.


This undersea cable called Alba-1 is on its way to Cuba from Venezuela

These subsea cables are incredibly expensive to create and install, it can takes months and cost millions of dollars. There are many different private and state owned companies producing this pivotal part of the Internet, like Tata Communications which created one of the first subsea networks that circumnavigates the world, a fiber-optic belt wrapped around the entire planet. Because these cables are so expensive to produce, they're often joint ventures between a handful of companies. The video below documents the creation of the Monet cable system, a collectively owned by Algar Telecom, Angola Cables, Antel Uruguay and Google.

Use this map of submarine cables to try and identify which undersea Internet cable your packet crossed.

After traveling across the ocean at nearly the speed of light through fiber-optic cables, our packet of data makes landfall on another shoreline, here's a photo of me (^__^) when i stumbled upon an Internet landing cable on the shore of St. Thomas in the Caribbean...

St. Thomas landing cable

Artists like Ingrid Burrington and Trevor Paglen have researched these cables, their history and their politics to better understand, and help others see this network we so heavily depend on...

Networks of New York

Networks of New York: An Internet Infrastructure Field Guide (2015) by Ingrid Burrington