An issue with the network adapter occurred on the pi (details below) causing these observations not to be uploaded, however their IQ data is a available on S3 to download if required. For example http://satnogs-iq.s3.amazonaws.com/1609520.raw
The issue appears that the ethernet controller just stopped working. Rebooting provided access via WiFi however ethernet was still wasn’t working even though it was showing as up. Setting the interface to down and back to up fixed the issue, which is very weird.
root@70:~# ifconfig eth0
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:49:81:8c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@70:~# ifconfig eth0 down
root@70:~# ifconfig eth0
eth0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:49:81:8c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@70:~# ifconfig eth0 up
root@70:~# ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::9945:7f48:b597:3081 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:49:81:8c txqueuelen 1000 (Ethernet)
RX packets 34 bytes 4738 (4.6 KiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 6 bytes 1067 (1.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0