# Hosts availability discrepancies

**URL:** <https://community.dynatrace.com/t/hosts-availability-discrepancies/21388>\
**Category:** Dynatrace Managed\
**Tags:** dynatrace-managed, hosts-classic\
**Created:** [July 24, 2019, 12:31pm UTC](https://community.dynatrace.com/t/hosts-availability-discrepancies/21388 "2019-07-24T12:31:10Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Christopher\_Cha](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/christopher_cha/32/26178_2.png) [@Christopher\_Cha](https://community.dynatrace.com/u/Christopher_Cha)\
**Post date:** [July 25, 2019, 2:03pm UTC](https://community.dynatrace.com/t/hosts-availability-discrepancies/21388/14 "2019-07-25T14:03:15Z")

</div>

I just want to add on to what Sebastian has mentioned. Usually if it’s a static host, then upon uninstallation of the agent, there would still be some static remnants left behind; these are used when we reinstall the agent, and the agent will recognize that this was previously monitored so data continuity will be maintained. It’s a totally different story if it’s cloud deployment where hosts can be destroyed and “respawn” as completely new host.

---

_[View the full topic](https://community.dynatrace.com/t/hosts-availability-discrepancies/21388)._
