Ubivox Outage History

Ubivox is up right now

Ubivox had 6 outages in the last 2 years totaling 25h 36m of downtime — averaging 0.2 incidents per month.

There were 6 Ubivox outages since February 24, 2025 totaling 25h 36m 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, 09:36 AM UTC
Duration
3h 36m
Timeline · 3 updates
  1. investigating Sep 08, 2026, 06:00 AM UTC

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

  2. monitoring Sep 08, 2026, 07:13 AM UTC

    We have implemented a fix and are currently monitoring the result..

  3. resolved Sep 08, 2026, 09:36 AM UTC

    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 15, 2026, 08:14 AM UTC
Duration
18h 42m
Timeline · 3 updates
  1. investigating Jul 14, 2026, 01:32 PM UTC

    We are currently investigating connection issues for Ubivox (app.ubivox.com). .

  2. monitoring Jul 14, 2026, 04:00 PM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Jul 15, 2026, 08:14 AM UTC

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

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

    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 September 3, 2025

DNS issue

Detected by Pingoru
Sep 03, 2025, 09:11 AM UTC
Resolved
Sep 03, 2025, 09:54 AM UTC
Duration
43m
Timeline · 2 updates
  1. identified Sep 03, 2025, 09:11 AM UTC

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

  2. resolved Sep 03, 2025, 09:54 AM UTC

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

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, 12:40 PM UTC
Duration
1h 21m
Timeline · 2 updates
  1. investigating Feb 24, 2025, 11:19 AM UTC

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

  2. resolved Feb 24, 2025, 12:40 PM UTC

    This incident has been resolved..

Read the full incident report →