<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.ubivox.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.ubivox.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.ubivox.com/history.atom"/>
  <title>Ubivox Status - Incident history</title>
  <updated>2026-09-04T12:05:56.360+00:00</updated>
  <author>
    <name>Ubivox</name>
  </author>
  
<entry>
  <id>tag:status.ubivox.com,2005:Incident/cmtmwqwpb0b5l0wo5cwumezdd</id>
  <published>2026-09-04T12:05:56.360+00:00</published>
  <updated>2026-09-04T12:05:56.360+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ubivox.com/incident/cmtmwqwpb0b5l0wo5cwumezdd"/>
  <title>Microsoft has issues receiving email</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 14 minutes</p>
    <p><strong>Affected Components:</strong> Email Delivery</p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>12:05:56</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>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>13:19:45</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved by Microsoft. We&#039;re have emptied all queues and delivered all waiting email..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ubivox.com,2005:Incident/cmrkt3qr80crs0ro2cj1bt4aw</id>
  <published>2026-07-14T13:32:00.000+00:00</published>
  <updated>2026-07-14T16:00:57.385+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ubivox.com/incident/cmrkt3qr80crs0ro2cj1bt4aw"/>
  <title>Connection Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 43 minutes</p>
    <p><strong>Affected Components:</strong> Ubivox Platform, Newsletter Images &amp; Links, API, Email Delivery, Signup Forms, SMTP Service</p>
    <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>16:00:57</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>08:14:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. The incident was caused by a technical issue with a service provider. We&#039;ve closely monitored system performance since the incident and verified stability. We&#039;re conducting a detailed investigation to identify the precise cause and prevent recurrence..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>13:32:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating connection issues for Ubivox (app.ubivox.com). .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ubivox.com,2005:Incident/cmh0jkud4002jm2i9c39ggbyp</id>
  <published>2025-10-16T18:00:00.000+00:00</published>
  <updated>2025-10-16T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ubivox.com/incident/cmh0jkud4002jm2i9c39ggbyp"/>
  <title>DNS issue with ubivox.com</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Ubivox Platform, Newsletter Images &amp; Links, API, Email Delivery, SMTP Service, Signup Forms</p>
    <p><small>Oct <var data-var='date'> 16</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Update: The issue was solved around 9:40 CEST on Thursday the 16th but it took up to 48 hours to propagate to all DNS servers across the globel.

---

Update 11:35 CEST: The issue is still apparent for some users. The reason is that the DNS change has to propagate to all DNS servers for the issue to be fully solved. We have made all the necessary changes on our end so for now all we can do is wait for the changes to spread. We&#039;re monitoring the changes and will update this incident as needed.

---

This morning we had an issue with DNS for the domain [ubivox.com](http://ubivox.com). The issue has been solved but for a while the domain would have been inaccessible for some of our clients..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ubivox.com,2005:Incident/cmhkl4lxe00w5kse1xev8egth</id>
  <published>2025-09-03T09:11:00.000+00:00</published>
  <updated>2025-09-03T09:11:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ubivox.com/incident/cmhkl4lxe00w5kse1xev8egth"/>
  <title>DNS issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 43 minutes</p>
    <p><strong>Affected Components:</strong> Signup Forms, SMTP Service, Ubivox Platform, Newsletter Images &amp; Links, API, Email Delivery</p>
    <p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>09:11:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue is caused by a change in DNS handling by a provider we&#039;re using. We were not notified of this change. The change has been handled on our end and we&#039;re updating DNS settings for several domains running the Ubivox platform.

Since this issue is DNS related changes take time to propagate across the internet. We expect it to be solved worldwide within six hours and we will keep an eye on the system over the next 24 hours to make sure nothing else pops up.

We&#039;re very sorry about the issue. Do not hesitate to contact support if you have any questions..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>09:54:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have made all the changes to DNS and we&#039;re seeing most systems running as expected again. However, due to the nature of DNS changes might not show up on your network just yet. It should all be solved within the next few hours without any actions on your end.

Let us know if you experience anything out of the ordinary..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ubivox.com,2005:Incident/cmhklcdvs04yf6lz9rv25tpcw</id>
  <published>2025-02-24T11:19:00.000+00:00</published>
  <updated>2025-02-24T11:19:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ubivox.com/incident/cmhklcdvs04yf6lz9rv25tpcw"/>
  <title>Image upload issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> Ubivox Platform</p>
    <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>11:19:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;re experiencing an issue with image uploads. 

If an image which is more than 2.000 pixels wide or high is uploaded the upload will not succeed. We&#039;re working on a fix with the supplier handling file uploads but for now you can solve the issue by resizing the image before uploading it to Ubivox. 

We will update when the issue is solved..</p>
<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>12:40:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

</feed>