# Simple Ad Hoc commands results in many UNREACHABLE hosts

**URL:** <https://forum.ansible.com/t/simple-ad-hoc-commands-results-in-many-unreachable-hosts/29241>\
**Category:** Ansible Project\
**Created:** [December 11, 2018, 7:52pm UTC](https://forum.ansible.com/t/simple-ad-hoc-commands-results-in-many-unreachable-hosts/29241 "2018-12-11T19:52:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sloan](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@Sloan](https://forum.ansible.com/u/Sloan)\
**Post date:** [December 11, 2018, 7:52pm UTC](https://forum.ansible.com/t/simple-ad-hoc-commands-results-in-many-unreachable-hosts/29241/1 "2018-12-11T19:52:50Z")

</div>

I have about 200 servers in my hosts file. I can ssh to those servers without entering a password. ssh and no errors or trouble. When i attempt to run a simple Ad Hoc uptime command more that 50% of the servers show up as UNREACHABLE. Are there any setting I can use to improve this? Salt uses --async to improve response rates. Does ansible have any command line flags that are similar?

[privilege\_escalation]  
become=True  
become\_method=sudo  
become\_user=root  
gathering = explicit  
[inventory]

[ssh\_connection]  
pipelining = True

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [December 12, 2018, 3:05pm UTC](https://forum.ansible.com/t/simple-ad-hoc-commands-results-in-many-unreachable-hosts/29241/2 "2018-12-12T15:05:59Z")

</div>

There is an async, but that should not help with unreachable, it would  
help to know WHY they are unreachable, normally running with -vvv  
gives you helpful information on what is happening at the connection  
level.