Emunie.com still down. Why?

[player01]

I looked several times for an explanation for the website being down for more than 48 hours.

I heard something akin to ... "oh well, it just went down and our hosting is working on it"

Well, that's not really believable is it?

WHY did you not take the precaution of multiple websites?

Obviously it is an attack, the question is does the eMunie team recognize this?
Can we know the nature or origination of this attack?

Please explain.

[Kenshin]

I looked several times for an explanation for the website being down for more than 48 hours.

I heard something akin to ... "oh well, it just went down and our hosting is working on it"

Well, that's not really believable is it?

WHY did you not take the precaution of multiple websites?

Obviously it is an attack, the question is does the eMunie team recognize this?
Can we know the nature or origination of this attack?

Please explain.

This is on their site.

We’ll be back soon!

Sorry for the inconvenience but we’re performing some maintenance at the moment, we should be back online shortly! Thank you.

— eMunie team

IRC: FreeNode #eMunieCrypto

You can always go on their IRC and see what is really happening. 

[MsCollec]

the forum is back online http://forum.emunie.com/ My guess is that Dan is too preoccupied by the Open beta release to focus on getting the website running but neither the website or forum is connected to eMunie client functionality in any way. eMunie client is secured and running just a tiny setback with the website.
Cheers

[extee]

I bet they get DDOSSed.
anyway the foum is now reachable again
http://forum.emunie.com/

[r0ach]

2 Possibilities:

1)  The saw Corgi coin launch and gave up because they can't compete

2)  They had to go shop for briefcases to stuff the IPO money in before they flee to Costa Rica

[MsCollec]

2 Possibilities:

1)  The saw Corgi coin launch and gave up because they can't compete

2)  They had to go shop for briefcases to stuff the IPO money in before they flee to Costa Rica

wrong, try again later