As Voyager 2 crosses into the mysterious boundary of interstellar space, it has encountered something scientists are calling ...

NASA's Voyager 2 spacecraft completed a historic flyby of Uranus, becoming the first,and so far, only probe to closely study ...

Scientists looked at decades' worth of data, combining reports and readings from various spacecraft and new computer modeling ...

Voyager 1 was launched in 1977, and after 49 years of travelling, it will reach a milestone in space that was once thought ...

By Kevin Gill Voyager 2 , an unmanned space probe launched by NASA on August 20, 1977, is equipped with 10 scientific instruments. However, after 47 years of operation, some of the scientific ...

Uranus emits 12% more heat than it gets from the Sun, contradicting Voyager 2 data. The discovery points to lingering formation heat and strengthens calls for a new NASA flagship mission to the ...

NASA's distant Voyager 2 probe has sent a "heartbeat" signal to Earth after mission control mistakenly cut contact, the U.S. space agency said Tuesday. Launched in 1977 to explore the outer planets ...

Voyager 2 is currently in the constellation of Pavo, more than 12.3 billion miles away from Earth, while Voyager 1 is in the constellation of Ophiucus 1 almost 15 billion miles from Earth.

NASA scientists are breathing a sigh of relief as data from the Voyager 2 spacecraft is again being received. The long-range one-way probe launched in 1977 and is far beyond our solar system, some ...

Floating through the edge of the solar system, the Voyager 2 space probe heard a “shout” from its creators from almost 20 billion km away. The ground team at NASA finally managed to ...

NASA has turned off one of Voyager 2's science instruments as power conservation becomes crucial for the interstellar exploring spacecraft located 12.8 billion miles from home.

After weeks of silence and worry, NASA has finally heard Voyager 2 come back to life. Communication with the unmanned probe was lost on July 21 when controllers accidentally sent a wrong command ...