Eclipse ’98 is what a live Internet event looked like when “scale” meant finding enough mirror servers before the crowd arrived.
The site was built for the total solar eclipse of February 26, 1998 in the Caribbean. Its volunteer E-team wanted to publish educational material before and after the event and deliver live eclipse images during totality.
The surviving “Lessons Learned” document is better than a polished retrospective because it records the actual engineering problems.
Seven hundred files and twelve servers
The team says the site contained more than 700 files from multiple authors. Twelve server sites supported Eclipse ’98 on eclipse day, and estimated traffic exceeded one million accesses. One mirror alone reportedly handled more than 220,000 hits.
The architecture sounds wonderfully transitional now: static HTML pages, CGI scripts, FTP image servers, mirror sites, distribution scripts, guestbooks, and a separate “post office.”
The webcast portion struggled under saturation. Servers that were supposed to distribute fresh images were also busy serving ordinary HTML. The team later concluded that dedicated image servers and better traffic prioritization would have helped.
Browser compatibility was another headache.
The pages were primarily built on Windows 95 using Netscape 4.x. Internet Explorer, Macintosh systems, Windows 3.1, screen sizes below 800×600, MIME mappings on older servers, and differences between browsers all created trouble.
The authors put it plainly: the web’s promise of standards and portability was still far from automatic.
The communication stack is just as period-specific. E-mail did most of the work, with ICQ, NetMeeting, and AOL Instant Messenger used when the team needed tighter coordination.
That makes Eclipse ’98 more than an astronomy site. It is a preserved postmortem from the era when a million-hit day could be fought with mirrors, FTP, volunteer labor, and a lot of improvisation.
CacheRat’s 1,967 Ancient Web Domains research list includes sites like this because the web’s history is not only in old page designs. It is also in the infrastructure notes people left behind after something unexpectedly worked—or almost worked.
Eclipse ’98 caught the shadow.
Its postmortem caught the web around it.