Ubivox Outage History

Ubivox is up right now

Ubivox had 4 outages in the last 2 years totaling 1h 13m of downtime — averaging 0.2 incidents per month.

There were 4 Ubivox outages since October 16, 2025 totaling 1h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ubivox.com

Minor September 8, 2026

We are experiencing issues with a server service provider.

Detected by Pingoru
Sep 08, 2026, 06:00 AM UTC
Resolved
Sep 08, 2026, 06:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 08, 2026, 06:00 AM UTC

    Type: Incident Duration: 3 hours and 36 minutes Affected Components: Newsletter Images & Links, Email Delivery Sep 8, 07:13:19 GMT+0 - Monitoring - We have implemented a fix and are currently monitoring the result. Sep 8, 06:00:00 GMT+0 - Investigating - We are currently experiencing issues with a server service provider. Users may experience issues uploading images to Ubivox. We have paused our email queues to avoid sending newsletters with errors. We are currently investigating the issue with our service provider. Sep 8, 09:36:08 GMT+0 - Resolved - This incident has been resolved. We switched to a backup solution to address the problems caused in Ubivox by the service issues as quickly as possible. We have since closely monitored the system and found no further issues.

Read the full incident report →

Minor September 4, 2026

Microsoft has issues receiving email

Detected by Pingoru
Sep 04, 2026, 12:05 PM UTC
Resolved
Sep 04, 2026, 01:19 PM UTC
Duration
1h 13m
Affected: Email Delivery
Timeline · 2 updates
  1. monitoring Sep 04, 2026, 12:05 PM UTC

    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: 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.)

  2. resolved Sep 04, 2026, 01:19 PM UTC

    This incident has been resolved by Microsoft. We're have emptied all queues and delivered all waiting email.

Read the full incident report →

Minor July 14, 2026

Connection Issues

Detected by Pingoru
Jul 14, 2026, 01:32 PM UTC
Resolved
Jul 14, 2026, 01:32 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 14, 2026, 01:32 PM UTC

    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).

Read the full incident report →

Minor October 16, 2025

DNS issue with ubivox.com

Detected by Pingoru
Oct 16, 2025, 06:00 PM UTC
Resolved
Oct 16, 2025, 06:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 16, 2025, 06:00 PM UTC

    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.

Read the full incident report →