BTC-E still exist?

[collaghost]

which one of the files are you suppose to edit?

Forget about trying to access by IP. Seems that now ddos goes to both IP and DNS addresses. I'm able to access btc-e once in a while though.

[coinotron]

They and Coinotron have been under attack for over 12 hours I would say.

Doesn't seem fair that coinotron is caught up in this, even if they do have a pool. Having a pool doesn't really count as anything.

True, but they don't care
It is sad that protection against ddos costs more than ordering an attack.

[mufa23]

Still down for me. What about you guys?

[crazy_rabbit]

Yeah, still down. It's really going on long now.

[Nicksasa]

Hasn't been down for me today ... up atm for me.

[creativex]

Been down for about an hour...still down.

[creativex]

One tab open, host file modified, incognito used.

...cannot connect. If I cannot reliably access my account because they're in love with some new self promoted alt coin, then hello vircurex and bye-bye dummies.

Hmm...those VCX shares are looking a lot more attractive suddenly.

[sublime5447]

Been working for me all morning. Working right now.

[creativex]

Been down for about an hour...still down.

Use your friend's internet connection or vpn or tor and try to connect afterwards. Connectivity issues are somehow related to anti-ddos protection, most likely they have your ip address blacklisted. Either wait 24 hours before they get it removed from stop-list or change your IP somehow. And do not open too much tabs when you trade, seems like this may trigger anti-ddos to block you again.

You're absolutely correct. Had a friend log into my account from their connection and move my funds to my wallets. BTC-e can go fvck themselves until they become an exchange again and stop peddling their own homebrew altcoins.

Thanks for your help.

EDIT: Deleted posts...swell.

[RoadTrain]

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

Code:

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.

[creativex]

I realize this. The hostfile mod got me access to my own funds yesterday and was necessary.

Today they've changed their IP and remarking out the host file entry allows access.

Accounts emptied...done with them. 

[SAC]

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

Code:

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_records

Edit: That is if the expired of two days if I read this right don't override.

Code:

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

[mufa23]

Just got to, and can load, the homepage. But if I try to login, I get this in Chrome

Code:

Error 118 (net::ERR_CONNECTION_TIMED_OUT): The operation timed out.

[SRoulette]

we logged in today without issue.

[maxcarjuzaa]

now we need to remove the hosts btc-e entry to access the site.

[armana]

still down in here

note : my local time is 10.40 17 -february-2013 (+7) indonesia time

[btc-e.com]

Exchange works 

[crazy_rabbit]

Loading slow for me, and the chatbox never loads. Loading for anyone else? The pain is going on quite awhile for BTC-e....

I don't get why coinotron is involved as well.

[dishwara]

Working for me, India.

[12gaFacelift]

Loading slow for me, and the chatbox never loads. Loading for anyone else? The pain is going on quite awhile for BTC-e....

I don't get why coinotron is involved as well.

since there is not much help to make new pool then maybe there is someone who dont like competitor.