Ubivox Outage History

Ubivox is up right now

Ubivox had 3 outages in the last 2 years — averaging 0.1 incidents per month.

There were 3 Ubivox outages since February 24, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ubivox.com

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 →

Minor February 24, 2025

Image upload issues

Detected by Pingoru
Feb 24, 2025, 11:19 AM UTC
Resolved
Feb 24, 2025, 11:19 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 24, 2025, 11:19 AM UTC

    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.

Read the full incident report →