# "Server status:   clock unstable"

**URL:** <https://discussions.flightaware.com/t/server-status-clock-unstable/19482>\
**Category:** ADS-B Flight Tracking\
**Created:** [December 30, 2016, 10:07pm UTC](https://discussions.flightaware.com/t/server-status-clock-unstable/19482 "2016-12-30T22:07:30Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [December 30, 2016, 10:53pm UTC](https://discussions.flightaware.com/t/server-status-clock-unstable/19482/4 "2016-12-30T22:53:49Z")

</div>

Not much you can do beyond monitoring the feedback the server gives you. When I looked at a similar VM problem a while back the problem was mostly invisible on the receiver, it would just drop 1% of sample blocks or something like that. You wouldn’t notice it in terms of a reduced message rate really as you’re still seeing 99% of the traffic, but on the mlat server side it shows up as the intervals between messages from the receiver being way off compared to the same messages being received by other receivers.

---

_[View the full topic](https://discussions.flightaware.com/t/server-status-clock-unstable/19482)._