Opti9 Outage History

Opti9 partial outage · 2 active incidents · 1 long-running issue View live status →

Pingoru has recorded 51 incidents for Opti9: 51 in the last 12 months and 18 in the last 90 days.

Source: status.opti9tech.com

51incidents recorded
51last 12 months
18last 90 days
3 daystypical duration

Incidents, newest first

Minor April 7, 2026 Veeam Cloud Connect - Intermittent Failures - Calgary/YYC 4d 6h Veeam Cloud Connect Backup - hostedbizz-west2, Veeam Cloud Connect Replication - hostedbizz-west2

Started Apr 07, 2026, 12:44 PM UTC· resolved Apr 11, 2026, 07:12 PM UTC

  1. identified Apr 07, 2026, 12:44 PM UTC

    We are currently experiencing intermittent backup and replication job failures with Veeam Backup and Replication jobs. Our team is investigating the issue and are working toward resolution as soon as possible.

  2. monitoring Apr 08, 2026, 12:54 AM UTC

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

  3. resolved Apr 11, 2026, 07:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 1, 2026 Veeam Service Provider Console - Management Agent Connectivity - LAX/Los Angeles 6d 15h Veeam Service Provider Console - veeam-lax-acw

Started Apr 01, 2026, 09:14 PM UTC· resolved Apr 08, 2026, 01:10 PM UTC

  1. identified Apr 01, 2026, 09:14 PM UTC

    We are currently experiencing an issue impacting Veeam Management Agent connectivity to Veeam Service Provider Console. We are working with our vendor toward a resolution and will provide an update as soon as possible. If your Veeam components are not reporting correctly to Veeam Service Provider console, a workaround is to remove and reinstall the Service Provider Console Agent. (detail here: https://helpcenter.veeam.com/docs/vac/provider_admin/obtain_agent_setup_file.html?ver=9.1)

  2. resolved Apr 08, 2026, 01:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 16, 2026 Veeam Cloud Connect - Job Failures (YOW00/Ottawa) 3d 21h Veeam Cloud Connect - hostedbizz

Started Mar 16, 2026, 08:48 PM UTC· resolved Mar 20, 2026, 06:29 PM UTC

  1. investigating Mar 16, 2026, 08:48 PM UTC

    We are currently experiencing job failures with Veeam Backup and Replication jobs targeting this region. Our team is investigating the issue and are working toward resolution as soon as possible.

  2. resolved Mar 20, 2026, 06:29 PM UTC

    This issue has been resolved and all Veeam Backup and Replication jobs in this region are now succeeding.

Read the full incident report →

Minor March 5, 2026 Veeam Service Provider Console - Management Agent Connection Issues (GSC3/New York) 1d 8h Veeam Service Provider Console - gsc3-acw

Started Mar 05, 2026, 06:29 PM UTC· resolved Mar 07, 2026, 02:31 AM UTC

  1. investigating Mar 05, 2026, 06:29 PM UTC

    We are currently experiencing connectivity issues between Veeam Management Agents and Veeam Service Provider Console (VSPC) in this region. Our team is investigating the issue and are working toward resolution as soon as possible.

  2. resolved Mar 07, 2026, 02:31 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 4, 2026 Veeam Cloud Connect - Job Failures 1d 2h Veeam Cloud Connect Backup - pub1-gsc3-cgb, Veeam Cloud Connect Backup - pub2-gsc3-cgb

Started Mar 04, 2026, 04:16 PM UTC· resolved Mar 05, 2026, 06:28 PM UTC

  1. identified Mar 04, 2026, 04:16 PM UTC

    We are currently experiencing job failures with Veeam Backup and Replication jobs targeting this region. Our team is investigating the issue and are working toward resolution as soon as possible.

  2. resolved Mar 05, 2026, 06:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 20, 2026 Veeam Cloud Connect - Job Failures (LON/London) 7h 9m Veeam Cloud Connect Backup - pub1-lon-cgb, Veeam Cloud Connect Backup - pub2-lon-cgb, Veeam Cloud Connect Replication - pub1-lon-cgr

Started Feb 20, 2026, 02:40 PM UTC· resolved Feb 20, 2026, 09:50 PM UTC

  1. identified Feb 20, 2026, 02:40 PM UTC

    We are currently experiencing job failures with Veeam Backup and Replication jobs targeting this region. Our team is investigating the issue and are working toward resolution as soon as possible.

  2. monitoring Feb 20, 2026, 07:47 PM UTC

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

  3. resolved Feb 20, 2026, 09:50 PM UTC

    The service issue in the London region has been resolved. You may need to manually retry any failed backup or replication jobs that were impacted by this incident

Read the full incident report →

Major February 13, 2026 Veeam Backup for Microsoft 365 Job Failures - YOW/Ottawa 33d 1h Veeam Backup for Microsoft 365 - office365

Started Feb 13, 2026, 06:12 PM UTC· resolved Mar 18, 2026, 07:52 PM UTC

  1. identified Feb 13, 2026, 06:12 PM UTC

    A subset of jobs are not running as expected, we are working alongside the vendor to resolve the issue.

  2. monitoring Feb 18, 2026, 10:29 PM UTC

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

  3. resolved Mar 18, 2026, 07:52 PM UTC

    This issue has been resolved and all Veeam Backup for Microsoft 365 Job's are now succeeding. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor January 20, 2026 Veeam Cloud Connect Backup - Intermittent Failures - New York/GSC 3d 8h Veeam Cloud Connect Backup - pub1-gsc3-cgb, Veeam Cloud Connect Backup - pub2-gsc3-cgb, Veeam Backup for Dedicated Private Cloud - GSC, Veeam Backup for Cloud Director - GSC

Started Jan 20, 2026, 01:53 PM UTC· resolved Jan 23, 2026, 10:03 PM UTC

  1. investigating Jan 20, 2026, 01:53 PM UTC

    We are currently experiencing intermittent backup and replication job failures with Veeam Backup and Replication jobs. Our team is investigating the issue and are working toward resolution as soon as possible.

  2. monitoring Jan 20, 2026, 10:30 PM UTC

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

  3. resolved Jan 23, 2026, 10:03 PM UTC

    A time synchronization issue caused time drift between the Veeam Cloud Connect server and several repository servers. The source of the time synchronization issue has been identified and corrected.

Read the full incident report →

Minor January 19, 2026 Intermittent Veeam Backup for Microsoft 365 Job Failures - Canada 4h 28m Veeam Backup for Microsoft 365 - portal-m-yvr, Veeam Backup for Microsoft 365 - office365, Veeam Backup for Microsoft 365 - yow01-m, Veeam Backup for Microsoft 365 - yow02-m and 1 more

Started Jan 19, 2026, 04:33 PM UTC· resolved Jan 19, 2026, 09:01 PM UTC

  1. investigating Jan 19, 2026, 04:33 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 19, 2026, 09:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 8, 2026 Veeam Service Provider Console (Calgary/YYC) - Emergency Maintenance 1d 2h Veeam Service Provider Console - console-yyc

Started Jan 08, 2026, 07:26 PM UTC· resolved Jan 09, 2026, 09:44 PM UTC

  1. identified Jan 08, 2026, 07:26 PM UTC

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

  2. identified Jan 09, 2026, 03:58 PM UTC

    We are experiencing issues with management agent connectivity to Veeam Service Provider Console, as a result of our maintenance window. We are currently engaged with Veeam to diagnose and determine next steps. At this time, management agent connectivity to VSPC is intermittently working. We will provide another update before 1PM Eastern Time.

  3. identified Jan 09, 2026, 06:49 PM UTC

    We are currently seeing improvements with management agent connectivity to Veeam Service Provider Console. We are still engaged with Veeam to ensure we bring this intermittent issue to a full resolution. We will provide another update before 5PM Eastern Time today.

  4. resolved Jan 09, 2026, 09:44 PM UTC

    We have confirmed that the intermittent issues we were experiencing with management agent connectivity to Veeam Service Provider Console have now been resolved. If you continue to observe issues with your management agent connectivity to Veam Service Provider Console, please reach out to our technical support team.

Read the full incident report →

Minor December 29, 2025 Intermittent Backup and Replication Job Issues - Calgary 1h 43m Veeam Cloud Connect Backup - hostedbizz-west2, Veeam Cloud Connect Replication - hostedbizz-west2, Veeam Cloud Connect Backup - yyc01-b, Veeam Cloud Connect Replication - yyc01-b and 2 more

Started Dec 29, 2025, 03:08 PM UTC· resolved Dec 29, 2025, 04:51 PM UTC

  1. investigating Dec 29, 2025, 03:08 PM UTC

    We are currently experiencing intermittent backup and replication job issues that may fail and restore and failover operations may not be available. You may see error messages that you are unable to connect to the service provider.

  2. resolved Dec 29, 2025, 04:51 PM UTC

    We have resolved the intermittent issues impacting backup and replication jobs in our Calgary region. If you continue to observe failures or issues with your backup/replication jobs, please reach out to our technical support team.

  3. postmortem Jan 05, 2026, 03:40 PM UTC

    ## Incident Summary On Saturday, December 27th at approximately 1:00AM Eastern time, a VMware ESXi host running several servers supporting Veeam Cloud Connect crashed. These servers were subsequently HA \(high availability\) restarted on another host in the cluster. Several Veeam Cloud Connect Gateways lost WAN connectivity as a result of the restart. This issue was not immediately apparent, due to the LAN connectivity for these gateways being functional. The incident was fully resolved on Monday, December 29th at 10:15AM Eastern Time after repairing the WAN connectivity to the offline gateways and restarting the Veeam Cloud Connect service. ## Impact of Incident All jobs that were running at the time of the incident failed, due to the Veeam Cloud Connect server being impacted. After the restart, a subset of client jobs experienced failures due to being assigned an offline Veeam Cloud Connect gateway. ## Follow Up Actions Opti9 are reviewing the incident carefully, and making adjustments to monitoring and processes as required to prevent future incidents. At this time, we have made the following adjustments: · Expanded our health check procedures to include manual checks and verification of the Veeam Cloud Connect gateways · Added additional monitoring items, specific to the Veeam Cloud Connect gateway component to ensure they are functional at all times

Read the full incident report →

Minor December 18, 2025 Intermittent DNS issues with vmcloud.ca and vmbackup.ca 3h 51m Veeam Cloud Connect - hostedbizz, Veeam Cloud Connect Backup - hostedbizz-west2, Veeam Cloud Connect Backup - yvr01-b, Veeam Cloud Connect - yow01-b and 24 more

Started Dec 18, 2025, 05:10 PM UTC· resolved Dec 18, 2025, 09:02 PM UTC

  1. identified Dec 18, 2025, 05:10 PM UTC

    An issue with our 3rd party DNS provider may cause intermittent name resolution failures for services using vmcloud.ca and vmbackup.ca DNS suffixes.

  2. resolved Dec 18, 2025, 09:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 13, 2025 GSC (Garden City, NY) Network Issues Impacting Multiple Services 1h 55m Cloud Director - GSC, Veeam Service Provider Console - gsc2-acw, Compute - GSC, Veeam Service Provider Console - gsc3-acw and 14 more

Started Dec 13, 2025, 09:23 PM UTC· resolved Dec 13, 2025, 11:18 PM UTC

  1. investigating Dec 13, 2025, 09:23 PM UTC

    Our teams are currently investigating a network issue in the Garden City, NY data center impacting multiple services.

  2. monitoring Dec 13, 2025, 11:12 PM UTC

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

  3. resolved Dec 13, 2025, 11:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 10, 2025 Veeam Service Provider Console (YYC) Intermittently Unavailable 5d 23h Veeam Service Provider Console - console-yyc

Started Dec 10, 2025, 06:31 PM UTC· resolved Dec 16, 2025, 06:22 PM UTC

  1. investigating Dec 10, 2025, 06:31 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 16, 2025, 06:22 PM UTC

    This incident has been resolved.

Read the full incident report →