# MLAT connection issues?

**URL:** https://adsbx.discourse.group/t/mlat-connection-issues/390
**Category:** Technical Support
**Created:** [March 6, 2024, 4:48pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390 "2024-03-06T16:48:28Z")
**Posts on this page:** 18
**Page:** 1

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 4:48pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/1 "2024-03-06T16:48:28Z")

</div>

So i noticed that MLAT isnt connected all of a sudden and i can not see/ pick up planes with MLAT as the source. any ideas?

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 5:07pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/2 "2024-03-06T17:07:45Z")

</div>

UPDATE: restarted and still nothing, its been issue since maybe midnight it would appear or within the past 8 hours… looking at the system log there is a connection issue… heres the log

Mar 06 12:00:11 adsbexchange systemd[1]: Started adsbexchange-mlat.  
Mar 06 12:00:13 adsbexchange adsbexchange-mlat[506]: mlat-client 0.4.2 starting up  
Mar 06 12:00:13 adsbexchange adsbexchange-mlat[506]: Listening for Basestation-format results connection on port 31003  
Mar 06 12:00:13 adsbexchange adsbexchange-mlat[506]: Listening for Beast-format results connection on port 30157  
Mar 06 12:00:13 adsbexchange adsbexchange-mlat[506]: Connection to [feed2.adsbexchange.com:64590](http://feed2.adsbexchange.com:64590) failed: [Errno -3] Temporary failure in name resolution

---

<div class="post-metadata">

### Author: ![dseven](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@dseven](https://adsbx.discourse.group/u/dseven)
#### Post date: [March 6, 2024, 6:18pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/3 "2024-03-06T18:18:21Z")

</div>

The last log line indicates a DNS issue. When you say “restarted”, do you mean a reboot, or just a restart of the adsbexchange-mlat service? If it was on reboot, that error might be temporary, if networking is not fully up yet, but if that’s after a service restart, there’s something else going on. Can you `ping feed2.adsbexchange.com` ?

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 6:29pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/4 "2024-03-06T18:29:05Z")

</div>

so i did a reboot from the adsbexchange local page on my laptop that didnt fix it… i did a restart when i saved something before that didnt fix it… i could try unplugging for a few minutes and try that …

when you say ping, where/ how do i do that? i have ADSBx DIY 1090 Receiver Kit  
style setups.

---

<div class="post-metadata">

### Author: ![dseven](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@dseven](https://adsbx.discourse.group/u/dseven)
#### Post date: [March 6, 2024, 6:32pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/5 "2024-03-06T18:32:23Z")

</div>

If you can ssh into the Pi, you could try the ping from there … otherwise leave it up for at least a few minutes after reboot and see what shows up under “adsbexchange-mlat.service logs”

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 6:36pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/6 "2024-03-06T18:36:41Z")

</div>

since it wont let me post what the log shows cause it has links… ill do best to show what its showing…

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 6:38pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/7 "2024-03-06T18:38:41Z")

</div>

Mar 06 13:07:52 adsbexchange adsbexchange-mlat[506]: Reconnecting in 6.4 seconds  
Mar 06 13:07:59 adsbexchange adsbexchange-mlat[506]: Connected to multilateration server at feed1.adsbexchange(.com):31090, handshaking  
Mar 06 13:08:04 adsbexchange adsbexchange-mlat[506]: Lost connection to feed1.adsbexchange(.com):

I put () around the com

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 6:49pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/8 "2024-03-06T18:49:24Z")

</div>

i did dig around online and someone posted to a mlat connection issue that this usually means it is on the server side? idk… beats me…

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 7:09pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/9 "2024-03-06T19:09:44Z")

</div>

i think i pinged it correctly but not sure but it keeps displaying new readings every second. in the time category its showing time= 100ms  
as average.

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 7:21pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/11 "2024-03-06T19:21:54Z")

</div>

I think its working but still not sure honestly… it says feeder not connected on status page but it now shows its connecting but dissconnecting from server since there are no mlat planes flying nearby rightnow… hmm

Mar 06 14:01:01 adsbexchange adsbexchange-mlat[506]: Connected to multilateration server at [feed2.adsbexchange.com:64590](http://feed2.adsbexchange.com:64590), handshaking  
Mar 06 14:01:26 adsbexchange adsbexchange-mlat[506]: Receiver: disconnected 0.0 msg/s received 0.0 msg/s processed (0%)  
Mar 06 14:01:26 adsbexchange adsbexchange-mlat[506]: Server: handshaking 0.0 kB/s from server 0.0 kB/s to server  
Mar 06 14:01:26 adsbexchange adsbexchange-mlat[506]: Results: 0.0 positions/minute  
Mar 06 14:01:26 adsbexchange adsbexchange-mlat[506]: Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used  
Mar 06 14:02:02 adsbexchange adsbexchange-mlat[506]: Disconnecting from [feed2.adsbexchange.com:64590](http://feed2.adsbexchange.com:64590): No data (not even keepalives) received for 60 seconds  
Mar 06 14:02:02 adsbexchange adsbexchange-mlat[506]: Connected to multilateration server at [feed1.adsbexchange.com:31090](http://feed1.adsbexchange.com:31090), handshaking  
Mar 06 14:03:02 adsbexchange adsbexchange-mlat[506]: Disconnecting from [feed1.adsbexchange.com:31090](http://feed1.adsbexchange.com:31090): No data (not even keepalives) received for 60 seconds  
Mar 06 14:03:03 adsbexchange adsbexchange-mlat[506]: Connected to multilateration server at [feed2.adsbexchange.com:64590](http://feed2.adsbexchange.com:64590), handshaking

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 7:51pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/12 "2024-03-06T19:51:20Z")

</div>

last thing i just noticed there was issues on the ads side to,

Mar 06 12:00:11 adsbexchange adsbexchange-feed[505]: BeastReduce TCP output: Name resolution for [feed1.adsbexchange.com](http://feed1.adsbexchange.com) failed: Temporary failure in name resolution  
Mar 06 12:00:11 adsbexchange adsbexchange-feed[505]: BeastReduce TCP output: Name resolution for [feed2.adsbexchange.com](http://feed2.adsbexchange.com) failed: Temporary failure in name resolution  
Mar 06 12:00:13 adsbexchange adsbexchange-feed[505]: BeastReduce TCP output: Name resolution for [feed1.adsbexchange.com](http://feed1.adsbexchange.com) failed: Temporary failure in name resolution  
Mar 06 12:00:15 adsbexchange adsbexchange-feed[505]: BeastReduce TCP output: Name resolution for [feed2.adsbexchange.com](http://feed2.adsbexchange.com) failed: Temporary failure in name resolution  
Mar 06 12:00:19 adsbexchange adsbexchange-feed[505]: BeastReduce TCP output: Connection established: [feed1.adsbexchange.com](http://feed1.adsbexchange.com) (54.244.22.71) port 30004

---

<div class="post-metadata">

### Author: ![dseven](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@dseven](https://adsbx.discourse.group/u/dseven)
#### Post date: [March 6, 2024, 7:54pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/13 "2024-03-06T19:54:11Z")

</div>

temporary DNS issues during boot are OK - it can be just that networking isn’t fully up yet… buf if that’s happening some time after boot, it could incidate a problem.

The continuous disconnects from MLAT are concerning. There was an issue that affected MLAT yesterday, but I think it’s supposed to be resolved now. I’ll try to get confirmation of that.

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 6, 2024, 8:33pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/14 "2024-03-06T20:33:04Z")

</div>

very well could be server issues…

---

<div class="post-metadata">

### Author: ![dseven](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@dseven](https://adsbx.discourse.group/u/dseven)
#### Post date: [March 6, 2024, 10:07pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/15 "2024-03-06T22:07:27Z")

</div>

It sounds like the MLAT issue is still being worked on. Mine is working today (it was not working yesterday), but it sounds like others are still having issues. Hopefully it’ll get resolved soon.

---

<div class="post-metadata">

### Author: ![dseven](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@dseven](https://adsbx.discourse.group/u/dseven)
#### Post date: [March 7, 2024, 8:37am UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/16 "2024-03-07T08:37:01Z")

</div>

The MLAT issue should be resolved now. Is it looking better for you?

---

<div class="post-metadata">

### Author: ![weatherman](https://avatars.discourse-cdn.com/v4/letter/w/f05b48/32.png) [@weatherman](https://adsbx.discourse.group/u/weatherman)
#### Post date: [March 7, 2024, 4:57pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/17 "2024-03-07T16:57:09Z")

</div>

well i did record mlat planes last night… also looking at the mlat sever map the regions have changed dramatically… the entire east coast up to Cananda was called northeast region… now its called central east. so they fixed something at least

i will say though that on the mlat server map it shows my location incorrectly all sudden though.

---

<div class="post-metadata">

### Author: ![dseven](https://avatars.discourse-cdn.com/v4/letter/d/d07c76/32.png) [@dseven](https://adsbx.discourse.group/u/dseven)
#### Post date: [March 10, 2024, 9:31am UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/18 "2024-03-10T09:31:21Z")

</div>

Locations on the MLAT map are intentionally obfuscated for privacy. It should be fairly close (within a few miles) but not exact.

---

<div class="post-metadata">

### Author: ![GFrayleigh](https://yyz1.discourse-cdn.com/flex027/user_avatar/adsbx.discourse.group/gfrayleigh/32/45_2.png) [@GFrayleigh](https://adsbx.discourse.group/u/GFrayleigh)
#### Post date: [April 13, 2024, 2:42pm UTC](https://adsbx.discourse.group/t/mlat-connection-issues/390/19 "2024-04-13T14:42:38Z")

</div>

hi guys ive just noticed the same mlat issue stating no feed for the last 48hrs feed is ok as is stats just mlat any ideas please
