Identified - The issue seems to be caused by the new adminconsole indexer release and we are about to proceed with a rollback. Until it's completed customers may see not see recently created deployments. We will post an update within next 60 minutes.
Dec 12, 10:29 UTC

Identified - We've uncovered an issue with upgrading a small percentage of clusters to the latest 7.5 release.

Clusters which have previously been monitored by a different Cloud deployment, but currently have monitoring disabled or are self monitored, will fail to elect new master nodes when attempting to upgrade to 7.5. Clusters with monitoring currently enabled, or which have never had external monitoring enabled will not be impacted by this issue.

We're working on fixing this workflow, and will update this incident when we have an estimate on a fix becoming available. In the meantime, customers can upgrade affected clusters by re-enabling external monitoring before attempting the upgrade.

As part of this issue, customers are unable to disable external monitoring on 7.5 clusters via the Cloud console. External monitoring can be disabled in 7.5 clusters by:

* Disabling monitoring in the Cloud Console
* Sending the following request in the API Console

PUT _cluster/settings
{
    "persistent": {
        "xpack.monitoring.collection.enabled": false,
        "xpack.monitoring.exporters.found-user-defined": {
            "type": "http",
            "enabled": false
        }
    }
}

We will update this incident within the next 12 hours with further details on when this issue will be fixed.

If you encounter any other issues, or need further help upgrading your clusters to 7.5 please contact us via support@elastic.co
Dec 5, 04:55 UTC

Identified - We suspect the issue has been introduced with a new code base deployed recently and the currently working on a rollback. We will provide an update within 1 hour.
Dec 11, 13:47 UTC