Eagle Eye Installations Offline

17 AUG 3304

Admiral Aden Tanner has confirmed reports that Aegis’s Eagle Eye installations are offline. The development is the result of Thargoid-sensor related interference at Dantec Enterprise, home of Aegis Core, which has neutralised Aegis’s ability to transmit data to the orbital installations.




Aegis has launched an operation to monitor Thargoid activity in the Pleiades Nebula. Admiral Aden Tanner, chief military liaison at Aegis, made this statement:

Our new Eagle Eye initiative will closely monitor systems where Thargoid surface sites are known to exist. We have established orbital surveillance installations at six locations in the Pleiades, which will measure energy-level fluctuations and track ship movements. Each installation is attended by a comms beacon that will collect the data before transmitting it to us for analysis.

Installation Locations

  • HIP 17692 A 3 – Eagle Eye One
  • HR 1185 A 5- Eagle Eye Two
  • HIP 17892 1 a – Eagle Eye Three
  • HIP 17225 A 5 – Eagle Eye Four
  • Pleiades Sector KC-V c2-4 – Eagle Eye Five
  • Pleiades Sector IR-W d1-55 2 – Eagle Eye Six


The messages from the unregister comms beacons appear to change on a weekly basis. The Eagle Eye installations give out messages that contain planet locations with Thargoid Structures in nearby systems. These structures contain Thargoid Links that in turn point to various locations which can be:

  • Previously Attacked starports
  • Unattacked starports
  • Thargoid Structures
  • Thargoid Barnacles
  • Crashed Thargoid ships
  • INRA bases and INRA related locations
  • Settlements attacked by Thargoids


When targets are starports that have not previously been attacked there is a one week interval where Non Human Signal Sources appear in that system (and surrounding systems). The starport can be saved if CMDRs kill enough Thargoids, but if the (hidden) kill count is not reached then the starport will be attacked and damaged the following week. It has been confirmed that success is based upon kill numbers, and only kills in the target system will be counted. This means that kills derived from missions on Aegis ships (which typically give out missions in nearby systems) do not count.

Aegis megaships Vanguard and Acropolis follow the attacks, and often stop in nearby systems each week. They are given a new flight plan before the Eagle Eye messages change, which seems to indicate that Aegis knows internally whether the attack has succeeded before this is reflected via Eagle Eye.

Decoding the messages

Eagle Eye Installations

The installations have an Unregistered Communications Beacon (UCB). These transmit once per hour (Eagle Eye One transmits on the hour, Eagle Eye Two transmits at ten past, Eagle Eye Three at twenty past etc). Transmissions normally change early Thursday. The transmissions use the key INVADERS (early weeks used THARGOIDS) and phonetic letters (decoder). They point to several systems with known Thargoid Structures (you can look up the exact locations in our datasheet, sometimes there are typos in the system names).

Finding the targets

The Thargoid Structures can be visited to find that some of the messages from the sites have changed (see Thargoid Linkfor methodology). You will need to activate the machine in the Thargoid Structure, which requires a Thargoid Probe and a Thargoid Sensor. Pick up as many Thargoid Links as you can, as they are easy to accidentally destroy. When the Thargoid machine is activated you will get usually two or three messages in your inbox that can be used to find targets. You can then fly into space to play and decode the messages (as described on the Thargoid Link page linked above).

Confirming the Targets

The Thargoid Links give the target systems, but no information about where the target is within that system. Look up the system in the various Canonn datasets to check whether it is a known system, often if there is something unusual in a system the link will be pointing to that. If the system is populated then it is may be a system the Thargoids plan to attack. Attack locations are confirmed by dropping the Thargoid Link in space in the target and playing the appropriate message – the link will swivel around and point a beam on light at the target. This can be repeated at different locations in a system to pin down the target.

In the cases of systems targeted for attack it was found that there are further Unregistered Communications Beacons in the vicinity of one of the starport in the system (play the message from the Thargoid Base after deploying the Thargoid Link as usual – follow the direction the link points. Easiest way is to enter supercruise and drop out around 900km from the starport – the transmitter should be nearby if this is the correct starport). The beacon is labeled as Transmitter and can sometimes be seen on starport approach. The beacons can be 1Mm away, and difficult to reach, they move quite fast, around 300m/s. The message from the beacons is “anomalous signal detected in system” in the phonetic alphabet. This is sometimes garbled (text messages run together, or fail to repeat). These beacons remain after a starport is attacked.

Sometimes it is not possible to confirm a target – the Thargoid Link simply points ahead and doesn’t point in a consistent direction. It is believed that these targets are incorrect, and it may be worth searching nearby systems – though this has never been successful. Unconfirmed targets are noted in the weekly reports. If you suspect a link is not pointing correctly then dropping two or more to see them point in different locations. It is also worth relogging as sometimes they will then point correctly.