Vendor reports: partial outageResolved · vendor status “resolved”Official status API

[Datto Partner Portal] - Datto partner portal is not loading and gives a 504 Gateway Timeout error, and Recovery Launchpad is loading slowly

Reported by Kaseya · Cloud & Infrastructure · source last read just now

Official source (opens in a new tab)
Vendor start
Nov 7, 2026, 03:46 UTC
Vendor's clock
Resolved
Nov 7, 2026, 04:58 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 12 min
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 partial outage: "[Datto Partner Portal] - Datto partner portal is not loading and gives a 504 Gateway Timeout error, and Recovery Launchpad is loading slowly".[E1, E2]
  • The vendor marked it resolved at 2026-11-07 04:58 UTC.[E3, E7]

Affected products and regions

  • Components: Login, Status Components.[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-11-07 04:58 UTC · summary s1, evidence f4b620866e4b98aa

Evidence (7)
  1. E1Kaseya reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "[Datto Partner Portal] - Datto partner portal is not loading and gives a 504 Gateway Timeout error, and Recovery Launchpad is loading slowly". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-11-07 03:46 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Login, Status Components. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-11-07 04:58 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Login, Status Components

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. Nov 7, 2026, 03:46 UTCVendor-reported startVendor time
  2. Nov 7, 2026, 04:58 UTCVendor-reported resolutionVendor time

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