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

Sage FRP 1000 (FR) - Partial Outage

Reported by Sage · HR, Finance & Ops · source last read just now

Official source (opens in a new tab)
Vendor start
Oct 27, 2026, 15:14 UTC
Vendor's clock
Resolved
Oct 27, 2026, 15:33 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
19 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

  • Sage reports partial outage: "Sage FRP 1000 (FR) - Partial Outage".[E1, E2]
  • The vendor marked it resolved at 2026-10-27 15:33 UTC.[E3, E7]

Affected products and regions

  • Components: Sage FRP 1000 (FR).[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-27 15:33 UTC · summary s1, evidence c86e0eff114e08d4

Evidence (7)
  1. E1Sage reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Sage FRP 1000 (FR) - Partial Outage". (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-27 15:14 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Sage FRP 1000 (FR). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-10-27 15:33 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Sage FRP 1000 (FR)

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

Sage 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 27, 2026, 15:14 UTCVendor-reported startVendor time
  2. Oct 27, 2026, 15:33 UTCVendor-reported resolutionVendor time

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