Is Voyado down?

Last checked 3m ago
Current status
Voyado is up

No incidents right now.

Official status page: https://status.voyado.com · Polled every 5 minutes · 13 components tracked

Voyado is operational right now. Last checked 3m ago; the most recent incident resolved 4d ago.

Real-time Voyado status, recent outages, and incident history — pulled directly from Voyado's official status page at https://status.voyado.com every 5 minutes. Pingoru tracks 13 Voyado services and has captured 33 incidents in the last 90 days (98.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Voyado reports a new incident — free for 3 monitors, no credit card.

Users who monitor Voyado also follow these CRM services: HubSpot Intercom Jira Service Desk ActiveCampaign Teamwork Alchemer Formstack Help Scout Intapp Bullhorn View all 6,000+ providers
Voyado uptime 98.44% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Active incident 1

  1. Ongoing ● 5d 7h
    Started Oct 12, 2026, 09:00 AM UTC
    APIWeb ApplicationMessagingAutomationsFTP3rd Party IntegrationsOther
    Timeline · 1 update
    • scheduled · Oct 12, 2026, 09:00 AM UTC

      Every Sunday at 03:00 CET/CEST we reserve the right to perform scheduled maintenance on our databases. During this time we make sure that the databases are fine tuned and all your data is protected. Normally this won’t affect availability, but some unresponsiveness or degraded performance may be experienced for short periods during the maintenance.

    Latest: Every Sunday at 03:00 CET/CEST we reserve the right to perform scheduled maintenance on our databases. During this time we make sure that the databases are fine tuned and all your …

Recent outages & incidents

Past 90 days
  1. Resolved 1d 13h
    Started Oct 12, 2026, 09:00 AM UTC · Resolved Oct 13, 2026, 10:02 PM UTC
    APIWeb ApplicationMessagingAutomationsFTP3rd Party IntegrationsOther
    Timeline · 2 updates
    • scheduled · Oct 12, 2026, 09:00 AM UTC

      Every Tuesday at 21:00 CET/CEST we reserve the right to perform scheduled maintenance on Voyado Engage. Normally this won't affect availability at all, but on some rare occasions unresponsiveness or degraded performance may be experienced during the upgrade. We do apologize in advance for any impact on your work and/or availability, but hope that the things we release to production will make it all worth it in the end.

    • in progress · Oct 13, 2026, 07:00 PM UTC

      Scheduled maintenance is currently in progress. We will provide updates as necessary.

    Latest: Scheduled maintenance is currently in progress. We will provide updates as necessary.

  2. Resolved 1h 47m
    Started Oct 07, 2026, 12:39 PM UTC · Resolved Oct 07, 2026, 02:26 PM UTC
    Web Application
    Timeline · 5 updates
    • identified · Oct 07, 2026, 12:39 PM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Oct 07, 2026, 12:57 PM UTC

      A fix has been implemented, and deployment is in progress.

    • monitoring · Oct 07, 2026, 01:33 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Oct 07, 2026, 02:26 PM UTC

      This incident has been resolved.

    • postmortem · Oct 09, 2026, 12:18 PM UTC

      **Date:** October 7, 2026 **Duration:** 14:13–15:32 CEST \(approximately 1 hour and 20 minutes\) **Affected service:** Engage Web Application ### Summary On October 7, 2026, between approximately 14:13 and 15:32 CEST, the Voyado Engage web application was unavailable to customers. During this period, users were unable to log in or access the web application. Our team identified the cause and restored service at 15:32 CEST. Following a period of monitoring, the incident was confirmed as resolved. ### Customer impact The incident affected access to the Engage web application for nearly all production environments. Users attempting to access the application experienced continuous loading, preventing them from logging in or using the interface. The partner portal remained accessible, and no data was lost during the incident. ### Root cause The incident was caused by a software update that introduced an issue with how the web application handles security tokens used during user sessions. ### Mitigation Once the issue was identified, our development team initiated a new deployment that removed the problematic change. In parallel, we restored a previously working version of the affected application components to accelerate recovery. This allowed functionality to return progressively while the updated deployment was completed. Full access was confirmed restored at approximately 15:32 CEST. ### Next steps To reduce the risk of similar incidents and improve our ability to recover quickly, we are focusing on the following improvements: * **Faster recovery:** Improve our deployment processes to enable quicker rollbacks to previously working application versions. * **Improved monitoring:** Introduce automated checks for login and application loading to help detect issues before customers are affected. * **Enhanced testing:** Strengthen testing procedures to better cover differences between production and testing environments. We sincerely apologize for the disruption this caused and appreciate your patience while we worked to restore the service.

    Latest: **Date:** October 7, 2026 **Duration:** 14:13–15:32 CEST \(approximately 1 hour and 20 minutes\) **Affected service:** Engage Web Application ### Summary On October 7, 2026, betwee…

  3. Resolved 1d
    Started Oct 05, 2026, 01:16 PM UTC · Resolved Oct 06, 2026, 02:09 PM UTC
    AutomationsOther
    Timeline · 7 updates
    • investigating · Oct 05, 2026, 01:16 PM UTC

      There is currently a buildup of messages queued up on one of our processes, this is causing delays to automations triggered by interactions as well as webhooks related to contact events. It is being investigated.

    • identified · Oct 05, 2026, 02:15 PM UTC

      We have identified a likely cause and taken steps to address it. We are now monitoring the results and will continue working on the issue until we can confirm it has been resolved.

    • monitoring · Oct 05, 2026, 03:18 PM UTC

      We are seeing continued progress, with delays gradually decreasing. Delays remain, but we expect the service to recover during the evening. We will continue to monitor the service closely as it recovers.

    • monitoring · Oct 06, 2026, 09:08 AM UTC

      Some delays remain. We currently expect the service to return to normal around 13:00 CEST and will continue to monitor it closely.

    • monitoring · Oct 06, 2026, 12:47 PM UTC

      Unfortunately, some delays remain, but they continue to decrease. We currently expect the service to return to normal in about 30 minutes.

    • resolved · Oct 06, 2026, 02:09 PM UTC

      This incident has been resolved. We have not observed any further delays since around 15:15 CEST.

    • postmortem · Oct 13, 2026, 07:52 AM UTC

      ## Summary Between 5 October and 6 October 2026, processing of some events in Voyado Engage was delayed. The cause was an internal update to one of our background processes, which unexpectedly triggered a large amount of extra processing. The issue was limited to this process and has been corrected. ## Customer Impact Automations triggered by contact interactions ran later than normal. Webhooks for contact, consent and preferences changes were delayed as well. ## Root Cause and Mitigation A safeguard in the update did not work as intended, so existing data was processed again as if it were new. This happened on two occasions, 5 and 6 October. Our engineering teams stopped the process, cleared the extra processing and confirmed that everything was back to normal. ## Next Steps We are adding stronger safeguards and checks for this type of update, as well as earlier alerts so we can react faster if something similar happens. We apologize for the disruption and appreciate your patience.

    Latest: ## Summary Between 5 October and 6 October 2026, processing of some events in Voyado Engage was delayed. The cause was an internal update to one of our background processes, which …

  4. Resolved 5d 18h
    Started Oct 05, 2026, 09:00 AM UTC · Resolved Oct 11, 2026, 03:08 AM UTC
    APIWeb ApplicationMessagingAutomationsFTP3rd Party IntegrationsOther
    Timeline · 2 updates
    • scheduled · Oct 05, 2026, 09:00 AM UTC

      Every Sunday at 03:00 CET/CEST we reserve the right to perform scheduled maintenance on our databases. During this time we make sure that the databases are fine tuned and all your data is protected. Normally this won’t affect availability, but some unresponsiveness or degraded performance may be experienced for short periods during the maintenance.

    • in progress · Oct 11, 2026, 01:00 AM UTC

      Scheduled maintenance is currently in progress. We will provide updates as necessary.

    Latest: Scheduled maintenance is currently in progress. We will provide updates as necessary.

  5. Resolved 1d 13h
    Started Oct 05, 2026, 09:00 AM UTC · Resolved Oct 06, 2026, 10:06 PM UTC
    APIWeb ApplicationMessagingAutomationsFTP3rd Party IntegrationsOther
    Timeline · 2 updates
    • scheduled · Oct 05, 2026, 09:00 AM UTC

      Every Tuesday at 21:00 CET/CEST we reserve the right to perform scheduled maintenance on Voyado Engage. Normally this won't affect availability at all, but on some rare occasions unresponsiveness or degraded performance may be experienced during the upgrade. We do apologize in advance for any impact on your work and/or availability, but hope that the things we release to production will make it all worth it in the end.

    • in progress · Oct 06, 2026, 07:00 PM UTC

      Scheduled maintenance is currently in progress. We will provide updates as necessary.

    Latest: Scheduled maintenance is currently in progress. We will provide updates as necessary.

See the full Voyado outage history

28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Voyado outage history →

Or sign up free to get alerts when Voyado breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 33 incidents View full outage history →