One tab open, host file modified, incognito used.
To be honest one should always avoid modifying hosts file and use it only as last resort. It's DNS' responsibility to update IP addresses. You can try to use
ipconfig /flushdns
to clear you local dns cache. If it won't help just wait for dns records to update. It can take up to 24 hours if I recall correctly.
It depends on the TTL setting used in their setup but that would be the standard time to use, apparently they could not be bothered using the disaster recovery method...
https://en.wikipedia.org/wiki/Time_to_live#DNS_recordsEdit: That is if the expired of two days if I read this right don't override.
dig +nocmd btc-e.com +trace
. 7271 IN NS j.root-servers.net.
. 7271 IN NS c.root-servers.net.
. 7271 IN NS a.root-servers.net.
. 7271 IN NS e.root-servers.net.
. 7271 IN NS l.root-servers.net.
. 7271 IN NS f.root-servers.net.
. 7271 IN NS g.root-servers.net.
. 7271 IN NS d.root-servers.net.
. 7271 IN NS h.root-servers.net.
. 7271 IN NS k.root-servers.net.
. 7271 IN NS m.root-servers.net.
. 7271 IN NS i.root-servers.net.
. 7271 IN NS b.root-servers.net.
;; Received 228 bytes from 192.168.0.1#53(192.168.0.1) in 1034 ms
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
;; Received 487 bytes from 199.7.91.13#53(199.7.91.13) in 1030 ms
btc-e.com. 172800 IN NS brad.ns.cloudflare.com.
btc-e.com. 172800 IN NS gail.ns.cloudflare.com.
;; Received 167 bytes from 192.42.93.30#53(192.42.93.30) in 239 ms
btc-e.com. 30 IN A 190.93.249.44
btc-e.com. 30 IN A 190.93.248.44
;; Received 59 bytes from 173.245.59.105#53(173.245.59.105) in 94 ms