<?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>Heyloyalty Status - Incident history</title>
    <link>https://status.heyloyalty.com</link>
    <description>Heyloyalty</description>
    <pubDate>Tue, 8 Sep 2026 06:00:00 +0000</pubDate>
    
<item>
  <title>Issues with sending</title>
  <description>
    Type: Incident
    Duration: 3 hours and 2 minutes

    Affected Components: Images &amp; Links, Email Delivery
    Sep 8, 09:01:37 GMT+0 - Resolved - This incident has been resolved. Sep 8, 07:23:57 GMT+0 - Monitoring - We have implemented a fix and are currently monitoring the result.   
  
Campaigns and automations will now resume sending.

You will also be able to upload and edit images again. Sep 8, 06:00:00 GMT+0 - Identified - We are currently experiencing periodic issues with our image hosting provider. As a result, we have temporarily paused all campaign and automation sends.

If you try to upload or edit images, you may experience issues where images are not uploaded or your changes are not saved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>09:01:37</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>07:23:57</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have implemented a fix and are currently monitoring the result.   
  
Campaigns and automations will now resume sending.

You will also be able to upload and edit images again..</p>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are currently experiencing periodic issues with our image hosting provider. As a result, we have temporarily paused all campaign and automation sends.

If you try to upload or edit images, you may experience issues where images are not uploaded or your changes are not saved..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 8 Sep 2026 06:00:00 +0000</pubDate>
  <link>https://status.heyloyalty.com/incident/cmtsaj28y052v1mmrl6mhxgu6</link>
  <guid>https://status.heyloyalty.com/incident/cmtsaj28y052v1mmrl6mhxgu6</guid>
</item>

<item>
  <title>Microsoft has issues receiving email</title>
  <description>
    Type: Incident
    Duration: 51 minutes

    Affected Components: Email Delivery
    Sep 4, 13:19:11 GMT+0 - Resolved - This incident has been resolved by Microsoft. We&#039;re working on emptying the queues and we expect all email to be delivered soon. Sep 4, 12:28:23 GMT+0 - Monitoring - Microsoft currently has issues receiving email. This means that many emails sent to Office365 recipients will result in a soft bounce with this message:

52.101.68.10 failed after I sent the message./Remote host said: 451 4.7.500 Server busy. Please try again later from \[REDACTED\]. (S77714) \[[**DB1PEPF000509E3.eurprd03.prod.outlook.com**](http://DB1PEPF000509E3.eurprd03.prod.outlook.com) 2026-09-04T08:16:36.825Z 08DF04AEA47F75BA\]/

If you have access to the Office365 admin page they have created an issue to follow here:  
&lt;https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029&gt;

We&#039;re monitoring the issue but for now there is nothing we can do to force emails through. Emails sent during Microsoft downtime will be tried again for the following 48 hours until delivery is possible.

(We&#039;re mainly creating this issue to have a place to point clients to for updates. There is nothing we can do inhouse to solve the issue.) 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 51 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>13:19:11</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved by Microsoft. We&#039;re working on emptying the queues and we expect all email to be delivered soon..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>12:28:23</var> GMT+0</small><br><strong>Monitoring</strong> -
  Microsoft currently has issues receiving email. This means that many emails sent to Office365 recipients will result in a soft bounce with this message:

52.101.68.10 failed after I sent the message./Remote host said: 451 4.7.500 Server busy. Please try again later from \[REDACTED\]. (S77714) \[[**DB1PEPF000509E3.eurprd03.prod.outlook.com**](http://DB1PEPF000509E3.eurprd03.prod.outlook.com) 2026-09-04T08:16:36.825Z 08DF04AEA47F75BA\]/

If you have access to the Office365 admin page they have created an issue to follow here:  
&lt;https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029&gt;

We&#039;re monitoring the issue but for now there is nothing we can do to force emails through. Emails sent during Microsoft downtime will be tried again for the following 48 hours until delivery is possible.

(We&#039;re mainly creating this issue to have a place to point clients to for updates. There is nothing we can do inhouse to solve the issue.).</p>
]]>
  </content:encoded>
  <pubDate>Fri, 4 Sep 2026 12:28:23 +0000</pubDate>
  <link>https://status.heyloyalty.com/incident/cmtmxjrza0b6j0wqjrm9q51r4</link>
  <guid>https://status.heyloyalty.com/incident/cmtmxjrza0b6j0wqjrm9q51r4</guid>
</item>

<item>
  <title>Issues with sending</title>
  <description>
    Type: Incident
    Duration: 4 hours and 44 minutes

    Affected Components: Email Delivery
    Aug 10, 14:57:10 GMT+0 - Resolved - Due to an issue with a hosting provider a main mailserver went offline. The issue has been solved and all services are online again. We will be monitoring the services closely for the rest of the day if issues arise again.

Get in touch with our support if you have any questions regarding the downtime. We sincerely apologise for the inconvenience caused. Aug 10, 10:13:00 GMT+0 - Investigating - We&#039;re experiencing issues sending e-mails and other messages from our system. We&#039;re currently investigating the cause. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>14:57:10</var> GMT+0</small><br><strong>Resolved</strong> -
  Due to an issue with a hosting provider a main mailserver went offline. The issue has been solved and all services are online again. We will be monitoring the services closely for the rest of the day if issues arise again.

Get in touch with our support if you have any questions regarding the downtime. We sincerely apologise for the inconvenience caused..</p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>10:13:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re experiencing issues sending e-mails and other messages from our system. We&#039;re currently investigating the cause..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 10 Aug 2026 10:13:00 +0000</pubDate>
  <link>https://status.heyloyalty.com/incident/cmsn5tbx30lwp0rrpmtq0jpkq</link>
  <guid>https://status.heyloyalty.com/incident/cmsn5tbx30lwp0rrpmtq0jpkq</guid>
</item>

<item>
  <title>System down</title>
  <description>
    Type: Incident
    Duration: 57 minutes

    Affected Components: API, Onsite Campaigns, App, Images &amp; Links, Email Delivery
    Dec 11, 12:51:09 GMT+0 - Resolved - This incident has been resolved, and systems are operational again Dec 11, 12:06:51 GMT+0 - Monitoring - Our service provider has implemented a fix and are currently monitoring the result. Dec 11, 11:54:12 GMT+0 - Investigating - One of our service providers is experiencing some issues, which has resulted in the system being down. They are currently investigating, and will provide running updates 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 57 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>12:51:09</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved, and systems are operational again.</p>
<p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>12:06:51</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our service provider has implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>11:54:12</var> GMT+0</small><br><strong>Investigating</strong> -
  One of our service providers is experiencing some issues, which has resulted in the system being down. They are currently investigating, and will provide running updates.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 11 Dec 2025 11:54:12 +0000</pubDate>
  <link>https://status.heyloyalty.com/incident/cmj1drdku001qry6a8myob58i</link>
  <guid>https://status.heyloyalty.com/incident/cmj1drdku001qry6a8myob58i</guid>
</item>

  </channel>
  </rss>