Your system is set to reduce motion, so the screen is paused. It has a slowly turning globe and moving arcs, and the edges glow red during incidents.
This page is the big screen at the front of a network operations centre: the room where a team watches a global network around the clock. In the middle a night-side Earth turns slowly, its cities lit orange, with data links arcing between twenty-six of them. Around it, instruments report system health, network traffic, server status, request rates, and alerts, while an activity feed scrolls past. Once in every four minutes something goes wrong. The camera swings round to the city in trouble, red traffic converges on it, and the incident card works through detection, investigation, mitigation, and recovery. Click ⛶ FULLSCREEN and it fills the screen.
No. It is an animation, and the bar under it says SIMULATION. The metrics, the twelve server clusters, the incidents, the alerts, and every line of the activity feed are invented and drawn in your browser. The twenty-six city names are real places and the continents come from a real land map, but no real network, company, or outage is shown. The page makes no connections while it runs and monitors nothing.
Real network operations screens are usually less dramatic: rows of graphs, maps of links coloured green, amber, or red, and ticket queues. The section on what a network operations centre does below explains what this screen's numbers would mean in a real one.
There are six kinds of incident, each with its own remedy:
| Incident | Cause shown | Remedy shown |
|---|---|---|
| DDoS attack | Volumetric flood | Scrubbing traffic at edge |
| Intrusion attempt | Lateral movement | Isolating host segment |
| Ransomware beacon | C2 beacon traffic | Blocking C2 domains |
| Brute-force campaign | Credential stuffing | Rate limiting auth API |
| BGP route leak | Route hijack | Withdrawing bad prefixes |
| Database failover | Primary unreachable | Promoting replica |
Incidents in the first half hour (seek with the bar or use ?t=):
| Time | Seconds | What happens |
|---|---|---|
| 00:00:00 | 0 | Start-up: the planet irises open and the panels wipe on |
| 00:00:14 | 14 | DDoS attack on London (SRV-07); mitigation from 0:29, resolved at 0:44 |
| 00:05:00 | 300 | First scan line sweeps down the screen |
| 00:05:04 | 304 | Ransomware beacon traced to Hong Kong |
| 00:08:49 | 529 | Brute-force campaign on Vancouver |
| 00:13:52 | 832 | Intrusion attempt at Anchorage |
| 00:17:11 | 1031 | Database failover at Perth |
| 00:20:50 | 1250 | Ransomware beacon at Perth |
| 00:24:27 | 1467 | Brute-force campaign on Seoul |
| 00:30:13 | 1813 | BGP route leak at Hong Kong |
Over the full ten-hour cycle there are 150 incidents: 31 brute-force campaigns, 26 ransomware beacons, 25 DDoS attacks, 24 intrusion attempts, 23 BGP route leaks, and 21 database failovers. They hit 22 of the 26 cities, most often Hong Kong and Singapore. The gaps between them run from just over two minutes to nearly six, and about 900 routine alerts and 61,200 data links fill the time in between.
?t= and the number of seconds to the address, for example /orbital-command?t=1813 for the first BGP route leak. Minutes and hours also work: ?t=30m13s or ?t=1h30m.The page draws at the full resolution of your screen, up to 4K. On a slow computer it lowers the resolution by itself to keep the motion smooth.
Background screens for films and series set in a technology company, a telecoms operator, an airline, or any control room; office and lobby displays that should look like a network operations centre without exposing real data; stage backdrops for technology talks and product launches; stream backgrounds for coding and gaming streams; and escape rooms or live-action games that need a calm screen that turns tense now and then. It is the calmest of the site's globe screens and the one best suited to being left on for hours. For OBS setup as a browser source, see the streaming toolkit.
A network operations centre, or NOC, is the team (and usually the room) responsible for keeping a network and the services on it running. Internet providers, telecoms companies, cloud and hosting providers, banks, broadcasters, and large companies run them, often around the clock in shifts. The job is mostly watching and responding: monitoring tools collect measurements from routers, links, and servers every few seconds or minutes, raise an alert when something crosses a threshold, and the NOC decides what to do. That might be rerouting traffic around a failed link, calling a carrier about a cut cable, restarting a service, scheduling a maintenance window, or waking up the engineer on call.
A NOC is not the same as a security operations centre, although films often show them as one room and many incidents need both.
| NOC (network operations) | SOC (security operations) | |
|---|---|---|
| Main question | Is everything up and fast enough? | Is anyone attacking us, or already inside? |
| Watches | Uptime, latency, packet loss, bandwidth, errors, capacity | Logins, intrusion alerts, malware detections, unusual traffic |
| Typical incident | A failed link, a full disk, a bad configuration change, a database that will not answer | A phishing compromise, ransomware, data being copied out |
| Measured by | Availability and time to restore service | Time to detect and contain |
This screen is mostly a NOC with some security incidents mixed in. A DDoS attack sits in both worlds: it is an attack, but what users notice is an outage, so network and security teams handle it together. The site's SOC screen shows the security side.
Two of the incident types are pure operations problems. The internet is made of tens of thousands of separately run networks, called autonomous systems, which tell each other which blocks of addresses (prefixes) they can reach using the Border Gateway Protocol, BGP. BGP largely trusts what neighbours announce. A route leak happens when a network passes on routes it should have kept to itself, and traffic for whole regions can suddenly flow the wrong way, slowly or not at all. A hijack is an announcement of someone else's addresses, by mistake or on purpose. The fix is to withdraw the bad announcements, as the screen shows. The prevention is careful filtering of what neighbours may announce, and route origin validation with RPKI, which lets networks reject announcements from an origin not authorised to make them.
Failover is switching to a standby when the main system fails. Databases are often run as a primary that takes the writes and one or more replicas that copy it, a few milliseconds behind (the "replication lag" in the feed). If the primary stops answering, a replica is promoted to take its place. Doing that safely is harder than it sounds: the system must be sure the old primary is really gone, or two machines may both accept writes and the data splits in two.
The whole ten-hour cycle is worked out in advance from a fixed random seed: the start, length, type, city, and server of each of the 150 incidents, the alert schedule, the brief server warnings, and every data link, each one chosen between cities that face the camera at the moment it fires. The planet is a set of dots taken from a one-degree land map, rotated and tilted by a camera that blends smoothly onto each incident's target and back. The metrics are layered slow waves with a little noise, and an incident adds to or subtracts from them as its severity rises and falls. Because every frame is a function of the time alone, the page can jump anywhere in the cycle at once, and the same moment always looks the same.
No. It is an animation. The metrics, the servers, the incidents, the alerts, and every line of the activity feed are invented and drawn in your browser. Only the city names and the shapes of the continents are real. The page connects to nothing and monitors nothing.
A network operations centre (NOC) keeps networks and services running: it watches uptime, latency, capacity, and faults, and fixes outages. A security operations centre (SOC) watches for attacks: intrusions, malware, and suspicious logins. Many organisations have both, and they work closely during an incident such as a DDoS attack, which is both an outage and an attack.
Ten hours. The cycle holds 150 incidents, one in every four-minute stretch, each with its own city, server, and type. After ten hours it starts again from the beginning. The screen is calculated frame by frame rather than played from a recording, so it needs no download and never buffers.
Drag the seek bar, or add ?t= to the address with the number of seconds, for example ?t=1813 for the first BGP route leak. This screen has no next and previous event buttons, but the table on this page lists the incidents in the first half hour, and there is one in every four minutes.
Yes. It is free to use for videos, films, streams, presentations, and events. Click FULLSCREEN, or add the page as an OBS browser source at 1920 × 1080 or 3840 × 2160; the scene is drawn at the full resolution of the source.
No. The screen was designed without hard flashes, since it is meant to be left on for hours. During an incident the edges of the screen warm to red and pulse slowly, about once every three seconds, and warning lights pulse softly. Every five minutes a thin teal line sweeps down the screen over four seconds. If your system is set to reduce motion, the page opens paused. See accessibility and visual effects for more.
Once the page and its fonts have loaded, the simulation makes no further network requests, so it keeps running if the connection drops. The optional VIDEO view streams from YouTube and needs a connection.
The sci-fi tech dashboard is a simpler control panel built from page elements, and the cyber attack map puts attacks on a flat world map. For the security side of the room, open the SOC screen; for a louder globe with a shield and botnets, the Hologram Globe. The satellite tracking screen suits the same mission-control scenes, and what is a DDoS attack? explains the most common incident here.