<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:uptime.heymint.xyz,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz"/>
  <link rel="self" type="application/atom+xml" href="https://uptime.heymint.xyz/history.atom"/>
  <title>HeyMint Status - Incident history</title>
  <updated>2024-05-11T16:33:51.635+00:00</updated>
  <author>
    <name>HeyMint</name>
  </author>
  
<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/clw2bssws135815b8lq6vte3qtn</id>
  <published>2024-05-11T16:33:51.635+00:00</published>
  <updated>2024-05-11T16:33:51.635+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/clw2bssws135815b8lq6vte3qtn"/>
  <title>Degraded database performance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> Contract Compiler, Mint Button, Launchpad Dashboard, Art Generator, HeyMint, Mint Page</p>
    <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>16:33:51</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>19:37:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/clq4ggphs20797c3oizavkdq8g</id>
  <published>2023-12-14T00:22:00.000+00:00</published>
  <updated>2023-12-14T00:22:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/clq4ggphs20797c3oizavkdq8g"/>
  <title>Twitter API is experiencing an issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>00:22:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;re currently experiencing some Twitter API errors that are preventing people from joining allowlists 😞 Our engineering team has been working non-stop to find a solution. We sincerely apologize for any inconvenience..</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>04:58:13</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We&#039;ve implemented a fix and entries are going through. Systems are currently being monitored and slowly being brought up to scale, so things might take a little longer than usual.

You might still see these two kinds of error messages:

**Security header check failed**: It happens when we make a change. Please refresh the page and try again. 

**Sorry, you tried to enter too recently. Please try again in a few minutes**: We are currently rate limiting to lower the number of requests to Twitter. Please try again in a few minutes. .</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>21:33:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Maintenance/cllmsdv0u44690b7ojr8vv4vu4</id>
  <published>2023-08-23T20:00:00.000+00:00</published>
  <updated>2023-08-23T20:45:46.032+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/maintenance/cllmsdv0u44690b7ojr8vv4vu4"/>
  <title>Upgrading HeyMint auth</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>20:45:46</var> GMT+0</small><br /><strong>Identified</strong> -
  At this time we&#039;re dealing with some unanticipated roadblocks, and are working on completing the maintenance &amp; getting HeyMint back up and running as soon as possible!.</p>
<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>22:28:30</var> GMT+0</small><br /><strong>Completed</strong> -
  Explore page functionality is restored &amp; Heymint is fully migrated to the new auth system!.</p>
<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are upgrading HeyMint to a new authentication system. During this process, HeyMint will temporarily be unavailable..</p>
<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>21:18:34</var> GMT+0</small><br /><strong>Identified</strong> -
  The new auth system is live, and heymint.xyz is now accessible to the public again!

We are seeing some issues with the explore pages, which we are currently investigating..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/cljdvs7y466734azogyjd6k7wb</id>
  <published>2023-06-27T06:02:34.959+00:00</published>
  <updated>2023-06-27T06:02:34.959+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/cljdvs7y466734azogyjd6k7wb"/>
  <title>Twitter API is experiencing an issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 13 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>06:02:34</var> GMT+0</small><br /><strong>Investigating</strong> -
  The Twitter API is currently returning a 403 (Forbidden) error for follows, tweet likes, and retweets, which appears to be affecting various services (https://github.com/twitterdev/Twitter-API-v2-sample-code/issues/58). This issue is causing certain Twitter features to be unavailable, including the ability to check follows, tweet likes, and retweets..</p>
<p><small>Jun <var data-var='date'> 28</var>, <var data-var='time'>19:22:58</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Due to seemingly undocumented changes to the Twitter API, we have had to change how we verify the Twitter account follow requirement. We have implemented an alternative approach and will be monitoring to ensure there are no further issues. HeyMint should now be fully functional..</p>
<p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>19:50:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our workaround is operating as expected and full functionality of HeyMint should be restored..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/cliw87qbb39243amn1xlzwmvmz</id>
  <published>2023-06-14T21:30:40.795+00:00</published>
  <updated>2023-06-14T21:30:40.795+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/cliw87qbb39243amn1xlzwmvmz"/>
  <title>Twitter integration not working for allowlists</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Jun <var data-var='date'> 14</var>, <var data-var='time'>21:30:40</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jun <var data-var='date'> 15</var>, <var data-var='time'>16:21:52</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/clifboh1o64081b4n8lsu9kjvf</id>
  <published>2023-06-03T01:35:36.342+00:00</published>
  <updated>2023-06-03T01:35:36.342+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/clifboh1o64081b4n8lsu9kjvf"/>
  <title>Database Connectivity Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> Launchpad Dashboard, HeyMint, Mint Page</p>
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>01:35:36</var> GMT+0</small><br /><strong>Identified</strong> -
  We are investigating issues with our database load balancer which are resulting in some sign-in errors, and elevated error rates for other features which require database connectivity..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>01:51:08</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>02:17:51</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/clhmlvag51081767zmzsvx06zgx</id>
  <published>2023-05-13T21:30:00.000+00:00</published>
  <updated>2023-05-13T21:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/clhmlvag51081767zmzsvx06zgx"/>
  <title>Database connectivity issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint, Contract Compiler, Mint Button, Launchpad Dashboard, Art Generator, Mint Page</p>
    <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>21:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  It appears that the server hosting our database load balancer has crashed. We are investigating further and will post an update when we know more..</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>23:27:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our database load-balancer is now up and running again, however our deployments are still having issues connecting to the database. We are still investigating why..</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>23:35:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  All affected services have been restarted and appear to be working normally. We are monitoring to ensure no further interruptions to service..</p>
<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>01:13:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/clfwyxw0n65532c7oc34njtsu5</id>
  <published>2023-03-31T19:59:45.646+00:00</published>
  <updated>2023-03-31T19:59:45.646+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/clfwyxw0n65532c7oc34njtsu5"/>
  <title>Mint page not working if wallet isn&#039;t connected</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> Mint Page</p>
    <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>19:59:45</var> GMT+0</small><br /><strong>Identified</strong> -
  *Please connect your wallet using &quot;Connect you wallet&quot; in the top right.* This will resolve the issue for you.

We&#039;ve identified an issue where mint pages will continually load if a wallet isn&#039;t connected. We&#039;re working on a fix to the issue now..</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>20:40:48</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/cleygitjk216447hjojqmyhpx05</id>
  <published>2023-03-07T16:20:00.214+00:00</published>
  <updated>2023-03-07T16:20:00.214+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/cleygitjk216447hjojqmyhpx05"/>
  <title>Elevated error rate</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>16:20:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an elevated error rate on HeyMint, especially when logging in..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>16:51:53</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the issue and are working on a fix now..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>18:39:57</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;ve introduced a fix to the issue which has started to stabilize the service, but we are continuing to work on a more solid fix..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>19:38:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/cleohfzbs186005o1n6qp2e73la</id>
  <published>2023-02-28T16:48:04.783+00:00</published>
  <updated>2023-02-28T17:23:28.369+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/cleohfzbs186005o1n6qp2e73la"/>
  <title>Elevated error rate when entering raffles</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 35 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>17:23:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>16:48:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an elevated error rate when trying to enter raffles on HeyMint.

If you receive an error code 500 message, please try to enter again later!.</p>
<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>17:06:38</var> GMT+0</small><br /><strong>Monitoring</strong> -
  This appears to be an issue with the provider of our captchas, Cloudflare (see their report here: https://www.cloudflarestatus.com/incidents/2rfr4k8b7gcs )

They have implemented a fix and are monitoring the result. We are seeing error rates go down on HeyMint..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Maintenance/clcsgrlgd3812hwn18yaulwd0</id>
  <published>2023-01-12T05:00:00.000+00:00</published>
  <updated>2023-01-12T05:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/maintenance/clcsgrlgd3812hwn18yaulwd0"/>
  <title>Infrastructure Upgrades</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 37 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint, Launchpad Dashboard</p>
    <p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>05:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for scheduled maintenance to upgrade our infrastructure during this time.

The site may be unavailable or degraded for some (or all) of this maintenance window, but we&#039;ll complete the maintenance as quickly as possible!

Thanks so much for your patience &amp; understanding..</p>
<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>05:37:05</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has been completed successfully.

Thank you so much for your patience!.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/clcs1pjmh8721hkol9zjqnhgb</id>
  <published>2023-01-11T19:19:17.225+00:00</published>
  <updated>2023-01-11T19:19:17.225+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/clcs1pjmh8721hkol9zjqnhgb"/>
  <title>Elevated error rate across HeyMint</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 59 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>19:19:17</var> GMT+0</small><br /><strong>Investigating</strong> -
  HeyMint is currently experiencing an unprecedented amount of traffic (and an elevated error rate) that may cause the site to be intermittently unreliable for some users.

We&#039;re currently working hard to resolve the issue - so sorry for the inconvenience!.</p>
<p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>19:25:10</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the root cause of the issue, and are continuing to work on a fix for this incident..</p>
<p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>20:17:39</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and currently monitoring the result..</p>
<p><small>Jan <var data-var='date'> 11</var>, <var data-var='time'>21:18:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  The issue is resolved at this time, if you run into any issues going forward, please reach out and let us know!.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:uptime.heymint.xyz,2005:Incident/clb8hneff249685vo935vl32dl</id>
  <published>2022-12-03T21:10:00.000+00:00</published>
  <updated>2022-12-03T21:10:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://uptime.heymint.xyz/incident/clb8hneff249685vo935vl32dl"/>
  <title>HeyMint DDoS Attack</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> HeyMint</p>
    <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>21:10:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified a DDoS attack against HeyMint and are currently working on a fix.

Apologies for the inconvenience, we are working hard to get everything back up and running!.</p>
<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>22:26:09</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>00:00:46</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>00:44:29</var> GMT+0</small><br /><strong>Resolved</strong> -
  Thanks for your patience everyone - HeyMint is back to being fully operational.

Just to clarify, the DDoS attack didn&#039;t compromise security in any regard - it merely spammed our servers with a ton of bot traffic and momentarily made the site unusable.

So sorry again all!.</p>

        ]]>
  </content>
</entry>

</feed>