Vendor reports: operationalResolved · vendor status “resolved”Official status API

Datto BCDR (Business Continuity and Disaster Recovery) - Node: use1-dtc-server-118 is inaccessible - Preventing access to Backups/ Screenshots/ Restores.

Reported by Kaseya · Cloud & Infrastructure · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Oct 24, 2026, 19:07 UTC
Vendor's clock
Resolved
Oct 26, 2026, 21:24 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 d 2 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Kaseya reports operational: "Datto BCDR (Business Continuity and Disaster Recovery) - Node: use1-dtc-server-118 is inaccessible - Preventing access to Backups/ Screenshots/ Restores.".[E1, E2]
  • The vendor marked it resolved at 2026-10-26 21:24 UTC.[E3, E7]

Affected products and regions

  • Components: Off-Site Recovery.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-10-26 21:24 UTC · summary s1, evidence 659c40d0a602e6e5

Evidence (7)
  1. E1Kaseya reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Datto BCDR (Business Continuity and Disaster Recovery) - Node: use1-dtc-server-118 is inaccessible - Preventing access to Backups/ Screenshots/ Restores.". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-24 19:07 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Off-Site Recovery. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-10-26 21:24 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Off-Site Recovery

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Kaseya is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Oct 24, 2026, 19:07 UTCVendor-reported startVendor time
  2. Oct 26, 2026, 21:24 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.