Ubivox Status - Incident history https://status.ubivox.com Ubivox Fri, 4 Sep 2026 12:05:56 +0000 Microsoft has issues receiving email Type: Incident Duration: 1 hour and 14 minutes Affected Components: Email Delivery Sep 4, 12:05:56 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: <https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029> We'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'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.) Sep 4, 13:19:45 GMT+0 - Resolved - This incident has been resolved by Microsoft. We're have emptied all queues and delivered all waiting email. Type: Incident

Duration: 1 hour and 14 minutes

Affected Components:

<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: <https://admin.cloud.microsoft/?source=applauncher#/servicehealth/:/alerts/EX1467029> We'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'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're have emptied all queues and delivered all waiting email..</p> ]]> Fri, 4 Sep 2026 12:05:56 +0000 https://status.ubivox.com/incident/cmtmwqwpb0b5l0wo5cwumezdd https://status.ubivox.com/incident/cmtmwqwpb0b5l0wo5cwumezdd Connection Issues Type: Incident Duration: 18 hours and 43 minutes Affected Components: Ubivox Platform, Newsletter Images & Links, API, Email Delivery, Signup Forms, SMTP Service Jul 14, 16:00:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jul 15, 08:14:41 GMT+0 - Resolved - This incident has been resolved. The incident was caused by a technical issue with a service provider. We've closely monitored system performance since the incident and verified stability. We're conducting a detailed investigation to identify the precise cause and prevent recurrence. Jul 14, 13:32:00 GMT+0 - Investigating - We are currently investigating connection issues for Ubivox (app.ubivox.com). Type: Incident

Duration: 18 hours and 43 minutes

Affected Components: , , , , ,

<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've closely monitored system performance since the incident and verified stability. We'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> ]]> Tue, 14 Jul 2026 13:32:00 +0000 https://status.ubivox.com/incident/cmrkt3qr80crs0ro2cj1bt4aw https://status.ubivox.com/incident/cmrkt3qr80crs0ro2cj1bt4aw DNS issue with ubivox.com Type: Incident Affected Components: Ubivox Platform, Newsletter Images & Links, API, Email Delivery, SMTP Service, Signup Forms Oct 16, 18:00:00 GMT+0 - Resolved - 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'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. Type: Incident

Affected Components: , , , , ,

<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'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> ]]> Thu, 16 Oct 2025 18:00:00 +0000 https://status.ubivox.com/incident/cmh0jkud4002jm2i9c39ggbyp https://status.ubivox.com/incident/cmh0jkud4002jm2i9c39ggbyp DNS issue Type: Incident Duration: 43 minutes Affected Components: Signup Forms, SMTP Service, Ubivox Platform, Newsletter Images & Links, API, Email Delivery Sep 3, 09:11:00 GMT+0 - Identified - The issue is caused by a change in DNS handling by a provider we're using. We were not notified of this change. The change has been handled on our end and we'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're very sorry about the issue. Do not hesitate to contact support if you have any questions. Sep 3, 09:54:00 GMT+0 - Resolved - We have made all the changes to DNS and we'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. Type: Incident

Duration: 43 minutes

Affected Components: , , , , ,

<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're using. We were not notified of this change. The change has been handled on our end and we'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'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'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> ]]> Wed, 3 Sep 2025 09:11:00 +0000 https://status.ubivox.com/incident/cmhkl4lxe00w5kse1xev8egth https://status.ubivox.com/incident/cmhkl4lxe00w5kse1xev8egth Image upload issues Type: Incident Duration: 1 hour and 21 minutes Affected Components: Ubivox Platform Feb 24, 11:19:00 GMT+0 - Investigating - We'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'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. Feb 24, 12:40:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 21 minutes

Affected Components:

<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'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'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> ]]> Mon, 24 Feb 2025 11:19:00 +0000 https://status.ubivox.com/incident/cmhklcdvs04yf6lz9rv25tpcw https://status.ubivox.com/incident/cmhklcdvs04yf6lz9rv25tpcw