<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>HeyMint Status - Incident history</title>
    <link>https://uptime.heymint.xyz</link>
    <description>HeyMint</description>
    <pubDate>Sat, 11 May 2024 16:33:51 +0000</pubDate>
    
<item>
  <title>Degraded database performance</title>
  <description>
    Type: Incident
    Duration: 3 hours and 3 minutes

    Affected Components: Contract Compiler, Mint Button, Launchpad Dashboard, Art Generator, HeyMint, Mint Page
    May 11, 16:33:51 GMT+0 - Investigating - We are currently investigating this incident. May 11, 19:37:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:33:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:37:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 11 May 2024 16:33:51 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/clw2bssws135815b8lq6vte3qtn</link>
  <guid>https://uptime.heymint.xyz/incident/clw2bssws135815b8lq6vte3qtn</guid>
</item>

<item>
  <title>Twitter API is experiencing an issue</title>
  <description>
    Type: Incident
    Duration: 21 hours and 12 minutes

    Affected Components: HeyMint
    Dec 14, 00:22:00 GMT+0 - Investigating - 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. Dec 14, 04:58:13 GMT+0 - Monitoring - 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.  Dec 14, 21:33:33 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:22:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:58:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:33:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 14 Dec 2023 00:22:00 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/clq4ggphs20797c3oizavkdq8g</link>
  <guid>https://uptime.heymint.xyz/incident/clq4ggphs20797c3oizavkdq8g</guid>
</item>

<item>
  <title>Upgrading HeyMint auth</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 29 minutes

    Affected Components: HeyMint
    Aug 23, 20:45:46 GMT+0 - Identified - 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! Aug 23, 22:28:30 GMT+0 - Completed - Explore page functionality is restored &amp; Heymint is fully migrated to the new auth system! Aug 23, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 23, 20:00:00 GMT+0 - Identified - We are upgrading HeyMint to a new authentication system. During this process, HeyMint will temporarily be unavailable. Aug 23, 21:18:34 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:45:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:28:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Explore page functionality is restored &amp; Heymint is fully migrated to the new auth system!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are upgrading HeyMint to a new authentication system. During this process, HeyMint will temporarily be unavailable..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:18:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 23 Aug 2023 20:00:00 +0000</pubDate>
  <link>https://uptime.heymint.xyz/maintenance/cllmsdv0u44690b7ojr8vv4vu4</link>
  <guid>https://uptime.heymint.xyz/maintenance/cllmsdv0u44690b7ojr8vv4vu4</guid>
</item>

<item>
  <title>Twitter API is experiencing an issue</title>
  <description>
    Type: Incident
    Duration: 2 days, 13 hours and 48 minutes

    Affected Components: HeyMint
    Jun 27, 06:02:34 GMT+0 - Investigating - 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. Jun 28, 19:22:58 GMT+0 - Monitoring - 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. Jun 29, 19:50:06 GMT+0 - Resolved - Our workaround is operating as expected and full functionality of HeyMint should be restored. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 13 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:02:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:22:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:50:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Our workaround is operating as expected and full functionality of HeyMint should be restored..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 27 Jun 2023 06:02:34 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/cljdvs7y466734azogyjd6k7wb</link>
  <guid>https://uptime.heymint.xyz/incident/cljdvs7y466734azogyjd6k7wb</guid>
</item>

<item>
  <title>Twitter integration not working for allowlists</title>
  <description>
    Type: Incident
    Duration: 18 hours and 51 minutes

    Affected Components: HeyMint
    Jun 14, 21:30:40 GMT+0 - Investigating - We are currently investigating this incident. Jun 15, 16:21:52 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:30:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:21:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 14 Jun 2023 21:30:40 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/cliw87qbb39243amn1xlzwmvmz</link>
  <guid>https://uptime.heymint.xyz/incident/cliw87qbb39243amn1xlzwmvmz</guid>
</item>

<item>
  <title>Database Connectivity Issues</title>
  <description>
    Type: Incident
    Duration: 42 minutes

    Affected Components: Launchpad Dashboard, HeyMint, Mint Page
    Jun 3, 01:35:36 GMT+0 - Identified - 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. Jun 3, 01:51:08 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 3, 02:17:51 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:35:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:51:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:17:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 3 Jun 2023 01:35:36 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/clifboh1o64081b4n8lsu9kjvf</link>
  <guid>https://uptime.heymint.xyz/incident/clifboh1o64081b4n8lsu9kjvf</guid>
</item>

<item>
  <title>Database connectivity issues</title>
  <description>
    Type: Incident
    Duration: 3 hours and 44 minutes

    Affected Components: HeyMint, Contract Compiler, Mint Button, Launchpad Dashboard, Art Generator, Mint Page
    May 13, 21:30:00 GMT+0 - Investigating - 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. May 13, 23:27:49 GMT+0 - Investigating - 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. May 13, 23:35:41 GMT+0 - Monitoring - All affected services have been restarted and appear to be working normally. We are monitoring to ensure no further interruptions to service. May 14, 01:13:41 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:27:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:35:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  All affected services have been restarted and appear to be working normally. We are monitoring to ensure no further interruptions to service..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:13:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 13 May 2023 21:30:00 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/clhmlvag51081767zmzsvx06zgx</link>
  <guid>https://uptime.heymint.xyz/incident/clhmlvag51081767zmzsvx06zgx</guid>
</item>

<item>
  <title>Mint page not working if wallet isn&#039;t connected</title>
  <description>
    Type: Incident
    Duration: 41 minutes

    Affected Components: Mint Page
    Mar 31, 19:59:45 GMT+0 - Identified - *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. Mar 31, 20:40:48 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:59:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  *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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:40:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 31 Mar 2023 19:59:45 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/clfwyxw0n65532c7oc34njtsu5</link>
  <guid>https://uptime.heymint.xyz/incident/clfwyxw0n65532c7oc34njtsu5</guid>
</item>

<item>
  <title>Elevated error rate</title>
  <description>
    Type: Incident
    Duration: 6 hours and 40 minutes

    Affected Components: HeyMint
    Mar 7, 16:20:00 GMT+0 - Investigating - We are currently investigating an elevated error rate on HeyMint, especially when logging in. Mar 7, 16:51:53 GMT+0 - Identified - We have identified the issue and are working on a fix now. Mar 7, 18:39:57 GMT+0 - Identified - 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. Mar 7, 19:38:41 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 7, 23:00:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an elevated error rate on HeyMint, especially when logging in..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:51:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the issue and are working on a fix now..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:39:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:38:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 7 Mar 2023 16:20:00 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/cleygitjk216447hjojqmyhpx05</link>
  <guid>https://uptime.heymint.xyz/incident/cleygitjk216447hjojqmyhpx05</guid>
</item>

<item>
  <title>Elevated error rate when entering raffles</title>
  <description>
    Type: Incident
    Duration: 35 minutes

    Affected Components: HeyMint
    Feb 28, 17:23:28 GMT+0 - Resolved - This incident has been resolved. Feb 28, 16:48:04 GMT+0 - Investigating - 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! Feb 28, 17:06:38 GMT+0 - Monitoring - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 35 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:23:28&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:48:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:06:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 28 Feb 2023 16:48:04 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/cleohfzbs186005o1n6qp2e73la</link>
  <guid>https://uptime.heymint.xyz/incident/cleohfzbs186005o1n6qp2e73la</guid>
</item>

<item>
  <title>Infrastructure Upgrades</title>
  <description>
    Type: Maintenance
    Duration: 37 minutes

    Affected Components: HeyMint, Launchpad Dashboard
    Jan 12, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 12, 05:00:00 GMT+0 - Identified - 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. Jan 12, 05:37:05 GMT+0 - Completed - Maintenance has been completed successfully.

Thank you so much for your patience! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 37 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:37:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has been completed successfully.

Thank you so much for your patience!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 12 Jan 2023 05:00:00 +0000</pubDate>
  <link>https://uptime.heymint.xyz/maintenance/clcsgrlgd3812hwn18yaulwd0</link>
  <guid>https://uptime.heymint.xyz/maintenance/clcsgrlgd3812hwn18yaulwd0</guid>
</item>

<item>
  <title>Elevated error rate across HeyMint</title>
  <description>
    Type: Incident
    Duration: 1 hour and 59 minutes

    Affected Components: HeyMint
    Jan 11, 19:19:17 GMT+0 - Investigating - 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! Jan 11, 19:25:10 GMT+0 - Identified - We have identified the root cause of the issue, and are continuing to work on a fix for this incident. Jan 11, 20:17:39 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Jan 11, 21:18:07 GMT+0 - Resolved - The issue is resolved at this time, if you run into any issues going forward, please reach out and let us know! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:19:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:25:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the root cause of the issue, and are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:17:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:18:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue is resolved at this time, if you run into any issues going forward, please reach out and let us know!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 11 Jan 2023 19:19:17 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/clcs1pjmh8721hkol9zjqnhgb</link>
  <guid>https://uptime.heymint.xyz/incident/clcs1pjmh8721hkol9zjqnhgb</guid>
</item>

<item>
  <title>HeyMint DDoS Attack</title>
  <description>
    Type: Incident
    Duration: 3 hours and 34 minutes

    Affected Components: HeyMint
    Dec 3, 21:10:00 GMT+0 - Identified - 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! Dec 3, 22:26:09 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 4, 00:00:46 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Dec 4, 00:44:29 GMT+0 - Resolved - 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! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:26:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:00:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:44:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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!.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 3 Dec 2022 21:10:00 +0000</pubDate>
  <link>https://uptime.heymint.xyz/incident/clb8hneff249685vo935vl32dl</link>
  <guid>https://uptime.heymint.xyz/incident/clb8hneff249685vo935vl32dl</guid>
</item>

  </channel>
  </rss>