tag:status.hazelcast.cloud,2005:/historyHazelcast Cloud Status - Incident History2024-03-28T18:40:29ZHazelcast Cloudtag:status.hazelcast.cloud,2005:Incident/166970762023-03-30T11:49:39Z2023-03-30T11:49:39Z[Statuspage] -<p><small>Mar <var data-var='date'>30</var>, <var data-var='time'>11:49</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>30</var>, <var data-var='time'>11:37</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.hazelcast.cloud,2005:Incident/92446942022-02-05T17:02:56Z2022-02-05T17:02:56Zhazelcast.cloud DNS records are not resolving on global servers<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>17:02</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>17:02</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>14:22</var> UTC</small><br><strong>Investigating</strong> - hazelcast.cloud DNS records are not resolving on global servers. Hazelcast Cloud production services are not accessible now. Existing clusters are not affected by this outage. We are continuously working the fix and will update here as soon as possible.</p>tag:status.hazelcast.cloud,2005:Incident/88303312021-12-13T10:00:30Z2021-12-13T10:00:30ZCloud API upgrade on Mon 13 Dec<p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>10:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>08:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>13</var>, <var data-var='time'>06:26</var> UTC</small><br><strong>Scheduled</strong> - Scheduled Maintenance: Cloud API upgrade on Mon 13 Dec 08:00/09:00 UTC. Duration: 60 minutes. Purpose: Regularly scheduled services updates. Impacts: dashboard, metrics. This won't affect Hazelcast clusters</p>tag:status.hazelcast.cloud,2005:Incident/47953502020-08-06T13:33:26Z2020-08-06T13:33:26ZTLS Enabled Cluster Creation Problem<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>13:33</var> UTC</small><br><strong>Resolved</strong> - There was a stucked process in certificate generation system, it prevented certificate creation operation. Now the system works fine and meanwhile we will try to stabilize that part to detect this and take automated action.</p><p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>13:16</var> UTC</small><br><strong>Investigating</strong> - We are having problem during TLS enabled cluster creation. Still investigating root cause, will inform once we found.</p>tag:status.hazelcast.cloud,2005:Incident/48179282020-08-06T07:00:00Z2020-08-21T22:53:02ZCluster Status Problem<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>Resolved</strong> - When you stop your cluster, it stays in Stopping state even after your cluster is shutdown.</p>tag:status.hazelcast.cloud,2005:Incident/43478282020-06-12T15:37:36Z2020-06-12T15:37:36ZAWS IAM and Organization API Increased Error Rate<p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>15:37</var> UTC</small><br><strong>Resolved</strong> - IAM & Organization API on AWS is resolved, there was no affected clusters on our side.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>09:31</var> UTC</small><br><strong>Monitoring</strong> - AWS is having increased error rate on their IAM and Organization APIs. This will not affect our customers and existing clusters. However, we are actively monitoring it and will inform here if there is any change.</p>tag:status.hazelcast.cloud,2005:Incident/42165702020-05-28T17:48:27Z2020-05-28T18:11:54ZContainer Registry Problem<p><small>May <var data-var='date'>28</var>, <var data-var='time'>17:48</var> UTC</small><br><strong>Resolved</strong> - Quay.io is getting back up online again, we will update when everything is online</p><p><small>May <var data-var='date'>28</var>, <var data-var='time'>13:37</var> UTC</small><br><strong>Monitoring</strong> - There is an outage on container registry system on quay.io, it may affect new Enterprise cluster creation, but there will be no problem for running clusters. Actively monitoring the system and will inform here once we saw everything is ok</p>tag:status.hazelcast.cloud,2005:Incident/38904582020-04-15T20:34:14Z2020-04-15T20:41:03ZCloudflare Outage<p><small>Apr <var data-var='date'>15</var>, <var data-var='time'>20:34</var> UTC</small><br><strong>Resolved</strong> - Everything is operational now</p><p><small>Apr <var data-var='date'>15</var>, <var data-var='time'>20:22</var> UTC</small><br><strong>Update</strong> - CloudFlare seems operational, but we are verifying this on Hazelcast Cloud, will report here once we are done</p><p><small>Apr <var data-var='date'>15</var>, <var data-var='time'>19:49</var> UTC</small><br><strong>Monitoring</strong> - Due to outage on CloudFlare, we have inconsistency on Enterprise Cluster creations. Existing Enterprise clusters are not affected by this outage. We are continuously monitoring the fix and will update here as soon as possible.</p>