Xeround - The (Potentially) Unusable Database?

Xeround is "an elastic, always-on database-as-a-service for your MySQL applications" (from the site).
Which sounds great, 'cept from the Q&A when they say

Despite the protective mechanisms that we’ve put into our technology (previously-mentioned quorum-based algorithms included), it is potentially possible for a more-than-trivial-but-less-than-total network split to bring the system to an unintelligible state. To safeguard against database schizophrenia because of split-brain (both to conserve consistency as well as avoid later conflict resolutions), Xeround’s database suspends itself when it experiences a network partitioning event that it can’t overcome by itself. In such cases, an external arbitrator (e.g., our service operators) instructs the system to continue operating by decided which of its parts is deemed active.

Which I'd translate to "If there is a network split, the DB will shut down till the sys-admins fix stuff"
Which is absolutely fine - if thats what you are looking for.
Me, I'd say they've got the specs slightly wonky - if you're really providing a database-as-a-service, (cloud-based, yada, yada), you probably really want to focus on this not happening.  I mean, what d'you think is most likely to cheese a customer off?

As  @al3xandru puts it

Instead of focusing strictly on the CAP characteristics of a distributed database, one should focus on what is the required behavior for their system and look for the database solution that offers them the guarantees they need.

Hat tip @al3xandru