# Toad connection time when instance is down **URL:** \ **Category:** Toad for Oracle & DevOps Toolkit\ **Created:** [May 20, 2019, 7:01am UTC](https://forums.toadworld.com/t/toad-connection-time-when-instance-is-down/46556 "2019-05-20T07:01:20Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![raul.kaubi](https://avatars.discourse-cdn.com/v4/letter/r/d26b3c/32.png) [@raul.kaubi](https://forums.toadworld.com/u/raul.kaubi)\ **Post date:** [May 20, 2019, 10:06am UTC](https://forums.toadworld.com/t/toad-connection-time-when-instance-is-down/46556/3 "2019-05-20T10:06:03Z")
Yes, I am describing the case, where specific database instance is down. Server itself is up and running. I also tried tnsnames.ora Set this as follows: > ORCL = > (DESCRIPTION = > (ADDRESS = (PROTOCOL = TCP)(HOST = [oradb.domain.com](http://oradb.domain.com))(PORT = 1521)) > (CONNECT\_DATA = > (SERVER = DEDICATED) > (SERVICE\_NAME = orcl) > ) > ) Then tried connecting, and the behaviour is the same, it took nearly a minute. While just testing the connection, it took me ~2 seconds. FYI: Toad is installed in terminal server, where there is no access to public internet (access is only to company intranet). By the way, this topic is quite similar to my problem, since this same thing happens when database instance is up and running, but I have put wrong username/password: > [@Why does TOAD 12.10.0.30 take so long to report ORA-01017 invalid username/password?](https://forums.toadworld.com/t/why-does-toad-12-10-0-30-take-so-long-to-report-ora-01017-invalid-username-password/41070/2): > > We don’t add any delay. If there is an error, we post it immediately. My guess in your situation is that the “Connect” command isn’t spooled until it is kicked back from Oracle with the error. Are SQL\*Plus and Toad using the same Oracle client? Regards Raul --- _[View the full topic](https://forums.toadworld.com/t/toad-connection-time-when-instance-is-down/46556)._