ADSBexchange.com
Custom Image - System Info

(..back to main menu)

Feeder Name
Public IP
 
11_knauf

67.251.72.229

Local IP: 
192.168.1.41

Configured Location: 
Owego
US-NY
United States of America (the)

Zerotier Status: 
zerotier is disabled.

Uptime: 
Current Time: Thu Feb 12 03:43:53 UTC 2026
Uptime: up 2 days, 22 hours, 58 minutes
Since 2026-02-09 04:45:06

Voltage Drops: 
sudo: unable to resolve host piaware: Name or service not known
Status: 0x0
Undervolted:
   Now: NO
   Run: NO
Throttled:
   Now: NO
   Run: NO
Frequency Capped:
   Now: NO
   Run: NO
Softlimit:
   Now: NO
   Run: NO

CPU temp=51.5'C
Redline=80'C

Messages since boot: 
1090mhz: 7,785,626
978mhz: 0
Tracks: 4,252

Installed SDR serials
(vendor code 0bda:*) 
00000001

Position Count By Type: (info)
Last 1 Minute
Last 5 Minutes
Last 15 Minutes
Since Boot
 
{
  "adsb_icao": 164,
  "adsb_icao_nt": 0,
  "adsr_icao": 0,
  "tisb_icao": 0,
  "adsc": 0,
  "mlat": 0,
  "other": 0,
  "mode_s": 0,
  "adsb_other": 0,
  "adsr_other": 0,
  "tisb_trackfile": 0,
  "tisb_other": 0,
  "mode_ac": 0,
  "unknown": 0
}

{
  "adsb_icao": 553,
  "adsb_icao_nt": 0,
  "adsr_icao": 0,
  "tisb_icao": 0,
  "adsc": 0,
  "mlat": 0,
  "other": 0,
  "mode_s": 0,
  "adsb_other": 0,
  "adsr_other": 0,
  "tisb_trackfile": 0,
  "tisb_other": 0,
  "mode_ac": 0,
  "unknown": 0
}

{
  "adsb_icao": 2187,
  "adsb_icao_nt": 0,
  "adsr_icao": 0,
  "tisb_icao": 0,
  "adsc": 0,
  "mlat": 0,
  "other": 0,
  "mode_s": 0,
  "adsb_other": 0,
  "adsr_other": 0,
  "tisb_trackfile": 0,
  "tisb_other": 0,
  "mode_ac": 0,
  "unknown": 0
}

{
  "adsb_icao": 796842,
  "adsb_icao_nt": 0,
  "adsr_icao": 0,
  "tisb_icao": 0,
  "adsc": 0,
  "mlat": 0,
  "other": 0,
  "mode_s": 0,
  "adsb_other": 0,
  "adsr_other": 0,
  "tisb_trackfile": 0,
  "tisb_other": 0,
  "mode_ac": 0,
  "unknown": 0
}

Current WiFi Status: 
wlan0     IEEE 802.11  ESSID:"Release The Epstein Files"  
          Mode:Managed  Frequency:2.457 GHz  Access Point: CC:40:D0:72:83:09   
          Bit Rate=72.2 Mb/s   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=70/70  Signal level=-30 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:22851  Invalid misc:0   Missed beacon:0

Current IP Status: 
eth0: flags=4099  mtu 1500
        ether b8:27:eb:5e:a2:e0  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

lo: flags=73  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 6689155  bytes 632585859 (603.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6689155  bytes 632585859 (603.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163  mtu 1500
        inet 192.168.1.41  netmask 255.255.255.0  broadcast 192.168.1.255
        ether b8:27:eb:0b:f7:b5  txqueuelen 1000  (Ethernet)
        RX packets 2079691  bytes 287827321 (274.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2220388  bytes 406678950 (387.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

IP Route: 
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.41 metric 303 
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.41 metric 303

readsb.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:43:55 UTC. --
Feb 09 04:45:10 piaware systemd[1]: Started readsb ADS-B receiver.
Feb 09 04:45:11 piaware readsb[497]: Mon Feb  9 04:45:10 2026 UTC  readsb starting up.
Feb 09 04:45:11 piaware readsb[497]: readsb version: wiedehopf git: d809bd8 (committed: Wed Sep 7 13:47:41 2022 0200)
Feb 09 04:45:11 piaware readsb[497]: Using lat:   42.0924, lon:  -76.2604
Feb 09 04:45:11 piaware readsb[497]: 30002: Raw TCP output port
Feb 09 04:45:11 piaware readsb[497]: 30005: Beast TCP output port
Feb 09 04:45:11 piaware readsb[497]: 30154: Position json output port
Feb 09 04:45:11 piaware readsb[497]: 30152: API output port
Feb 09 04:45:11 piaware readsb[497]: 30003: SBS TCP output ALL port
Feb 09 04:45:11 piaware readsb[497]: 30001: Raw TCP input port
Feb 09 04:45:11 piaware readsb[497]: 30004: Beast TCP input port
Feb 09 04:45:11 piaware readsb[497]: 30104: Beast TCP input port
Feb 09 04:45:11 piaware readsb[497]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
Feb 09 04:45:11 piaware readsb[497]: Found Rafael Micro R820T tuner
Feb 09 04:45:11 piaware readsb[497]: rtlsdr: enabling tuner AGC
Feb 09 04:45:11 piaware readsb[497]: Allocating 16 zero-copy buffers

dump978-fa.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:44:05 UTC. --
-- No entries --

autogain1090.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:44:05 UTC. --
Feb 10 02:33:22 piaware systemd[1]: Started autogain for readsb or dump1090-fa.
Feb 10 02:33:22 piaware autogain1090[32590]: Gain already at maximum! (0.038% messages >-3dB)
Feb 10 02:33:22 piaware systemd[1]: autogain1090.service: Succeeded.
Feb 11 02:31:44 piaware systemd[1]: Started autogain for readsb or dump1090-fa.
Feb 11 02:31:45 piaware autogain1090[23149]: Gain already at maximum! (0.020% messages >-3dB)
Feb 11 02:31:45 piaware systemd[1]: autogain1090.service: Succeeded.
Feb 12 02:46:38 piaware systemd[1]: Started autogain for readsb or dump1090-fa.
Feb 12 02:46:39 piaware autogain1090[21239]: Gain already at maximum! (0.031% messages >-3dB)
Feb 12 02:46:39 piaware systemd[1]: autogain1090.service: Succeeded.

tar1090.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:44:05 UTC. --
Feb 09 04:45:11 piaware systemd[1]: Started tar1090 - compress dump1090 json data.

tar1090-978.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:44:06 UTC. --
-- No entries --

adsbexchange-feed.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:44:06 UTC. --
Feb 09 04:45:10 piaware systemd[1]: Started adsbexchange-feed.
Feb 09 04:45:10 piaware adsbexchange-feed[504]: Mon Feb  9 04:45:10 2026 UTC  readsb starting up.
Feb 09 04:45:11 piaware adsbexchange-feed[504]: readsb version: wiedehopf git: d809bd8 (committed: Wed Sep 7 13:47:41 2022 0200)
Feb 09 04:45:11 piaware adsbexchange-feed[504]: Using lat:   42.0924, lon:  -76.2604
Feb 09 04:45:11 piaware adsbexchange-feed[504]: Beast TCP input: Connection established: 127.0.0.1 port 30005
Feb 09 04:45:11 piaware adsbexchange-feed[504]: BeastReduce TCP output: Name resolution for feed1.adsbexchange.com failed: Temporary failure in name resolution
Feb 09 04:45:11 piaware adsbexchange-feed[504]: BeastReduce TCP output: Name resolution for feed2.adsbexchange.com failed: Temporary failure in name resolution
Feb 09 04:45:12 piaware adsbexchange-feed[504]: BeastReduce TCP output: Name resolution for feed1.adsbexchange.com failed: Temporary failure in name resolution
Feb 09 04:45:14 piaware adsbexchange-feed[504]: BeastReduce TCP output: Name resolution for feed2.adsbexchange.com failed: Temporary failure in name resolution
Feb 09 04:45:19 piaware adsbexchange-feed[504]: BeastReduce TCP output: Name resolution for feed1.adsbexchange.com failed: Temporary failure in name resolution
Feb 09 04:45:27 piaware adsbexchange-feed[504]: BeastReduce TCP output: Connection established: feed2.adsbexchange.com (54.244.22.71) port 64004
Feb 09 13:02:33 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 13:18:03 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 14:14:45 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 14:29:52 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 14:56:01 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 15:11:08 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 15:26:27 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 15:42:17 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 16:00:53 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 16:16:43 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 16:32:55 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 16:48:04 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 17:03:22 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 17:18:55 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 17:34:17 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 17:49:17 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 18:04:21 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 18:19:21 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 18:34:34 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 18:56:35 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 19:11:47 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 19:27:53 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 19:46:07 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 20:01:10 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 20:19:11 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 20:42:28 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 20:58:52 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 21:13:53 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 21:30:44 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 21:53:35 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 09 22:19:33 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 13:22:55 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 14:17:38 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 15:01:52 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 15:19:33 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 15:56:05 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 16:15:04 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 16:30:32 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 16:51:16 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 17:06:23 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 17:23:15 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 17:42:06 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 17:58:20 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 18:41:41 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 18:57:14 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 19:13:39 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 19:30:00 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 19:45:10 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 20:00:39 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 20:15:51 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 20:33:13 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 20:48:18 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 21:16:44 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 10 21:51:29 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 04:08:09 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 14:06:02 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 14:37:32 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 14:52:52 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 15:24:33 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 16:02:18 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 16:17:30 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 16:32:42 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 16:54:16 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 17:10:55 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 17:26:18 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 17:41:23 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 17:56:34 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 18:19:19 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 18:44:45 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 19:01:13 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 19:16:18 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 19:31:27 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 19:47:05 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 20:02:22 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 20:17:25 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 20:36:53 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 20:51:58 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 21:28:17 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 21:56:49 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.
Feb 11 22:15:27 piaware adsbexchange-feed[504]: BeastReduce TCP output: High latency, reducing data usage temporarily.

adsbexchange-mlat.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:44:06 UTC. --
Feb 11 22:47:58 piaware adsbexchange-mlat[499]: Receiver: connected    54.5 msg/s received       15.0 msg/s processed (28%)
Feb 11 22:47:58 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 11 22:47:58 piaware adsbexchange-mlat[499]: Results:  1.9 positions/minute
Feb 11 22:47:58 piaware adsbexchange-mlat[499]: Aircraft: 1 of 4 Mode S, 8 of 10 ADS-B used
Feb 11 22:47:59 piaware adsbexchange-mlat[499]: peer_count:  36 outlier_percent: 0.2 bad_sync_timeout:   0
Feb 11 23:02:59 piaware adsbexchange-mlat[499]: Receiver: connected    60.7 msg/s received       17.4 msg/s processed (29%)
Feb 11 23:02:59 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.2 kB/s to server
Feb 11 23:02:59 piaware adsbexchange-mlat[499]: Results:  2.4 positions/minute
Feb 11 23:02:59 piaware adsbexchange-mlat[499]: Aircraft: 1 of 11 Mode S, 10 of 12 ADS-B used
Feb 11 23:03:16 piaware adsbexchange-mlat[499]: peer_count:  35 outlier_percent: 0.7 bad_sync_timeout:   0
Feb 11 23:17:59 piaware adsbexchange-mlat[499]: Receiver: connected    85.5 msg/s received       24.5 msg/s processed (29%)
Feb 11 23:17:59 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.2 kB/s to server
Feb 11 23:17:59 piaware adsbexchange-mlat[499]: Results:  3.1 positions/minute
Feb 11 23:17:59 piaware adsbexchange-mlat[499]: Aircraft: 1 of 5 Mode S, 4 of 5 ADS-B used
Feb 11 23:18:07 piaware adsbexchange-mlat[499]: peer_count:  31 outlier_percent: 0.8 bad_sync_timeout:   0
Feb 11 23:32:59 piaware adsbexchange-mlat[499]: Receiver: connected    59.7 msg/s received       16.2 msg/s processed (27%)
Feb 11 23:32:59 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.2 kB/s to server
Feb 11 23:32:59 piaware adsbexchange-mlat[499]: Results:  1.5 positions/minute
Feb 11 23:32:59 piaware adsbexchange-mlat[499]: Aircraft: 2 of 5 Mode S, 9 of 10 ADS-B used
Feb 11 23:33:03 piaware adsbexchange-mlat[499]: peer_count:  37 outlier_percent: 0.0 bad_sync_timeout:   0
Feb 11 23:48:00 piaware adsbexchange-mlat[499]: Receiver: connected    51.9 msg/s received       14.3 msg/s processed (28%)
Feb 11 23:48:00 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 11 23:48:00 piaware adsbexchange-mlat[499]: Results:  2.0 positions/minute
Feb 11 23:48:00 piaware adsbexchange-mlat[499]: Aircraft: 0 of 9 Mode S, 8 of 9 ADS-B used
Feb 11 23:48:11 piaware adsbexchange-mlat[499]: peer_count:  33 outlier_percent: 1.1 bad_sync_timeout:   0
Feb 12 00:03:00 piaware adsbexchange-mlat[499]: Receiver: connected    32.6 msg/s received       10.1 msg/s processed (31%)
Feb 12 00:03:00 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 00:03:00 piaware adsbexchange-mlat[499]: Results:  2.1 positions/minute
Feb 12 00:03:00 piaware adsbexchange-mlat[499]: Aircraft: 0 of 1 Mode S, 7 of 8 ADS-B used
Feb 12 00:03:01 piaware adsbexchange-mlat[499]: peer_count:  36 outlier_percent: 0.2 bad_sync_timeout:   0
Feb 12 00:18:00 piaware adsbexchange-mlat[499]: Receiver: connected    29.7 msg/s received        8.7 msg/s processed (29%)
Feb 12 00:18:00 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 00:18:00 piaware adsbexchange-mlat[499]: Results:  1.3 positions/minute
Feb 12 00:18:00 piaware adsbexchange-mlat[499]: Aircraft: 1 of 4 Mode S, 4 of 5 ADS-B used
Feb 12 00:18:13 piaware adsbexchange-mlat[499]: peer_count:  25 outlier_percent: 0.1 bad_sync_timeout:   0
Feb 12 00:33:01 piaware adsbexchange-mlat[499]: Receiver: connected    49.8 msg/s received       15.0 msg/s processed (30%)
Feb 12 00:33:01 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 00:33:01 piaware adsbexchange-mlat[499]: Results:  2.5 positions/minute
Feb 12 00:33:01 piaware adsbexchange-mlat[499]: Aircraft: 3 of 8 Mode S, 3 of 5 ADS-B used
Feb 12 00:33:12 piaware adsbexchange-mlat[499]: peer_count:  35 outlier_percent: 0.9 bad_sync_timeout:   0
Feb 12 00:48:01 piaware adsbexchange-mlat[499]: Receiver: connected    44.1 msg/s received       12.8 msg/s processed (29%)
Feb 12 00:48:01 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 00:48:01 piaware adsbexchange-mlat[499]: Results:  1.5 positions/minute
Feb 12 00:48:01 piaware adsbexchange-mlat[499]: Aircraft: 0 of 8 Mode S, 5 of 8 ADS-B used
Feb 12 00:48:02 piaware adsbexchange-mlat[499]: peer_count:  36 outlier_percent: 0.6 bad_sync_timeout:   0
Feb 12 01:03:02 piaware adsbexchange-mlat[499]: Receiver: connected    69.2 msg/s received       18.7 msg/s processed (27%)
Feb 12 01:03:02 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.2 kB/s to server
Feb 12 01:03:02 piaware adsbexchange-mlat[499]: Results:  2.1 positions/minute
Feb 12 01:03:02 piaware adsbexchange-mlat[499]: Aircraft: 1 of 10 Mode S, 10 of 11 ADS-B used
Feb 12 01:03:11 piaware adsbexchange-mlat[499]: peer_count:  37 outlier_percent: 0.2 bad_sync_timeout:   0
Feb 12 01:18:02 piaware adsbexchange-mlat[499]: Receiver: connected    55.2 msg/s received       14.6 msg/s processed (26%)
Feb 12 01:18:02 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 01:18:02 piaware adsbexchange-mlat[499]: Results:  3.1 positions/minute
Feb 12 01:18:02 piaware adsbexchange-mlat[499]: Aircraft: 2 of 10 Mode S, 4 of 5 ADS-B used
Feb 12 01:18:04 piaware adsbexchange-mlat[499]: peer_count:  29 outlier_percent: 0.3 bad_sync_timeout:   0
Feb 12 01:33:02 piaware adsbexchange-mlat[499]: Receiver: connected    49.0 msg/s received       15.2 msg/s processed (31%)
Feb 12 01:33:02 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 01:33:02 piaware adsbexchange-mlat[499]: Results:  2.4 positions/minute
Feb 12 01:33:02 piaware adsbexchange-mlat[499]: Aircraft: 0 of 4 Mode S, 10 of 12 ADS-B used
Feb 12 01:33:12 piaware adsbexchange-mlat[499]: peer_count:  36 outlier_percent: 0.7 bad_sync_timeout:   0
Feb 12 01:48:02 piaware adsbexchange-mlat[499]: Receiver: connected    43.0 msg/s received       12.8 msg/s processed (30%)
Feb 12 01:48:02 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 01:48:02 piaware adsbexchange-mlat[499]: Results:  1.3 positions/minute
Feb 12 01:48:02 piaware adsbexchange-mlat[499]: Aircraft: 1 of 5 Mode S, 4 of 6 ADS-B used
Feb 12 01:48:06 piaware adsbexchange-mlat[499]: peer_count:  35 outlier_percent: 2.6 bad_sync_timeout:   0
Feb 12 02:03:02 piaware adsbexchange-mlat[499]: Receiver: connected    36.3 msg/s received       12.1 msg/s processed (33%)
Feb 12 02:03:02 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 02:03:02 piaware adsbexchange-mlat[499]: Results:  2.4 positions/minute
Feb 12 02:03:02 piaware adsbexchange-mlat[499]: Aircraft: 1 of 4 Mode S, 7 of 9 ADS-B used
Feb 12 02:03:16 piaware adsbexchange-mlat[499]: peer_count:  35 outlier_percent: 0.3 bad_sync_timeout:   0
Feb 12 02:18:02 piaware adsbexchange-mlat[499]: Receiver: connected    46.0 msg/s received       11.8 msg/s processed (26%)
Feb 12 02:18:02 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 02:18:02 piaware adsbexchange-mlat[499]: Results:  2.9 positions/minute
Feb 12 02:18:02 piaware adsbexchange-mlat[499]: Aircraft: 2 of 7 Mode S, 2 of 4 ADS-B used
Feb 12 02:18:09 piaware adsbexchange-mlat[499]: peer_count:  26 outlier_percent: 0.4 bad_sync_timeout:   0
Feb 12 02:33:03 piaware adsbexchange-mlat[499]: Receiver: connected    44.8 msg/s received       12.6 msg/s processed (28%)
Feb 12 02:33:03 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 02:33:03 piaware adsbexchange-mlat[499]: Results:  2.3 positions/minute
Feb 12 02:33:03 piaware adsbexchange-mlat[499]: Aircraft: 0 of 1 Mode S, 4 of 5 ADS-B used
Feb 12 02:33:09 piaware adsbexchange-mlat[499]: peer_count:  35 outlier_percent: 0.1 bad_sync_timeout:   0
Feb 12 02:48:03 piaware adsbexchange-mlat[499]: Receiver: connected    37.0 msg/s received       10.2 msg/s processed (28%)
Feb 12 02:48:03 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 02:48:03 piaware adsbexchange-mlat[499]: Results:  1.7 positions/minute
Feb 12 02:48:03 piaware adsbexchange-mlat[499]: Aircraft: 2 of 5 Mode S, 1 of 1 ADS-B used
Feb 12 02:48:14 piaware adsbexchange-mlat[499]: peer_count:   1 outlier_percent: 0.1 bad_sync_timeout:   0
Feb 12 03:03:03 piaware adsbexchange-mlat[499]: Receiver: connected    21.5 msg/s received        7.2 msg/s processed (34%)
Feb 12 03:03:03 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 03:03:03 piaware adsbexchange-mlat[499]: Results:  1.0 positions/minute
Feb 12 03:03:03 piaware adsbexchange-mlat[499]: Aircraft: 1 of 4 Mode S, 5 of 5 ADS-B used
Feb 12 03:03:26 piaware adsbexchange-mlat[499]: peer_count:  31 outlier_percent: 0.3 bad_sync_timeout:   0
Feb 12 03:18:03 piaware adsbexchange-mlat[499]: Receiver: connected    40.5 msg/s received       10.4 msg/s processed (26%)
Feb 12 03:18:03 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 03:18:03 piaware adsbexchange-mlat[499]: Results:  2.4 positions/minute
Feb 12 03:18:03 piaware adsbexchange-mlat[499]: Aircraft: 0 of 1 Mode S, 6 of 7 ADS-B used
Feb 12 03:18:17 piaware adsbexchange-mlat[499]: peer_count:  35 outlier_percent: 0.9 bad_sync_timeout:   0
Feb 12 03:33:03 piaware adsbexchange-mlat[499]: Receiver: connected    42.6 msg/s received       12.2 msg/s processed (29%)
Feb 12 03:33:03 piaware adsbexchange-mlat[499]: Server:   ready         0.0 kB/s from server      0.1 kB/s to server
Feb 12 03:33:03 piaware adsbexchange-mlat[499]: Results:  1.7 positions/minute
Feb 12 03:33:03 piaware adsbexchange-mlat[499]: Aircraft: 0 of 2 Mode S, 5 of 6 ADS-B used
Feb 12 03:33:05 piaware adsbexchange-mlat[499]: peer_count:  27 outlier_percent: 0.6 bad_sync_timeout:   0

adsbexchange-stats.service logs: 
-- Journal begins at Mon 2026-02-09 04:45:01 UTC, ends at Thu 2026-02-12 03:44:06 UTC. --
Feb 09 04:45:09 piaware systemd[1]: Started ADSBexchange Stats.
Feb 09 04:45:09 piaware adsbexchange-stats[378]: Note: 'USE_OLD_PATH' is set.
Feb 09 04:45:09 piaware adsbexchange-stats[378]: No valid data source directory found, do you have the adsbexchange feed scripts installed?  Tried each of: [/run/readsb /run/adsbexchange-feed]
Feb 09 04:45:30 piaware adsbexchange-stats[378]: Using UUID [xxxx-xxx-xxx-d93717a49e19] for stats uploads
Feb 09 04:45:30 piaware adsbexchange-stats[378]: Using JSON directory [/run/readsb] for source data
Feb 09 04:45:30 piaware adsbexchange-stats[378]: Using script's DNS cache (600 seconds)
Feb 10 00:27:30 piaware adsbexchange-stats[9181]: curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to adsbexchange.com:443
Feb 10 00:27:30 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (35): []; Sleeping a little extra.
Feb 10 00:28:15 piaware adsbexchange-stats[9488]: curl: (28) Operation timed out after 10003 milliseconds with 0 out of 0 bytes received
Feb 10 00:28:15 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
Feb 10 04:15:04 piaware adsbexchange-stats[12998]: curl: (28) Connection timed out after 10004 milliseconds
Feb 10 04:15:04 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
Feb 10 22:08:29 piaware adsbexchange-stats[3496]: curl: (28) Operation timed out after 10004 milliseconds with 0 bytes received
Feb 10 22:08:29 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
Feb 10 22:14:00 piaware adsbexchange-stats[5990]: curl: (28) Operation timed out after 10001 milliseconds with 0 bytes received
Feb 10 22:14:00 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
Feb 11 04:09:44 piaware adsbexchange-stats[1906]: curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to adsbexchange.com:443
Feb 11 04:09:44 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (35): []; Sleeping a little extra.
Feb 11 06:37:09 piaware adsbexchange-stats[2579]: curl: (28) Connection timed out after 10004 milliseconds
Feb 11 06:37:09 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
Feb 11 06:46:23 piaware adsbexchange-stats[6646]: curl: (28) Connection timed out after 10004 milliseconds
Feb 11 06:46:23 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
Feb 11 13:09:47 piaware adsbexchange-stats[14755]: curl: (28) Connection timed out after 10003 milliseconds
Feb 11 13:09:47 piaware adsbexchange-stats[378]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.

/boot/adsbx-env 
# Default no serial single SDR mode
# use # to comment out for 1090 mode
RECEIVER_OPTIONS="--device-type rtlsdr --ppm 0"

# 1090 serialed SDR
# Remove # for 1090 serial mode
#RECEIVER_OPTIONS="--device 1090 --device-type rtlsdr --ppm 0"

DECODER_OPTIONS="--max-range 450"
NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1200 --net-ro-interval 0.1 \
        --net-ri-port 30001 --net-ro-port 30002 --net-sbs-port 30003 \
        --net-bi-port 30004,30104 --net-bo-port 30005"
JSON_OPTIONS="--json-location-accuracy 2"

# uncomment (remove #) the following line to make the actual range outline persist reboots
#JSON_OPTIONS="--json-location-accuracy 2 --range-outline-hours 8760 --write-state-only-on-exit --write-state=/var/globe_history"

INPUT="127.0.0.1:30005"
RESULTS="--results beast,connect,localhost:30104 --results basestation,listen,31003 --results beast,listen,30157"
MLATSERVER="feed.adsbexchange.com:31090"
INPUT_TYPE="dump1090"
#INPUT_TYPE="dump1090 --privacy"
SERVERPORT="30005"

/boot/adsbx-978env 
RECEIVER_978_OPTIONS="--net-only"
DECODER_978_OPTIONS="--max-range 460"
NET_978_OPTIONS="--net --net-heartbeat 60 --net-ro-interval 0.5 --net-ro-port 0 --net-sbs-port 0 --net-bi-port 0 --net-bo-port 0 --net-connector localhost,30004,beast_out"
JSON_978_OPTIONS="--json-location-accuracy 2"

ENABLED=yes
#RECEIVER_OPTIONS="--sdr-gain 36.4 --sdr driver=rtlsdr,serial=978 --format CS8"
RECEIVER_OPTIONS="--sdr-gain 42.1 --sdr driver=rtlsdr --format CS8"
DECODER_OPTIONS=""
NET_OPTIONS="--raw-port 30978 --json-port 30979"

Log for last update