Sage incident

Sage Cloud Enablement - Major Outage

Major Resolved View vendor source →

Sage experienced a major incident on July 23, 2026 affecting Embedded Services and Embedded Services and 1 more component, lasting 20h 29m. The incident has been resolved; the full update timeline is below.

Started
Jul 23, 2026, 04:26 PM UTC
Resolved
Jul 24, 2026, 12:55 PM UTC
Duration
20h 29m
Detected by Pingoru
Jul 23, 2026, 04:26 PM UTC

Affected components

Embedded ServicesEmbedded ServicesSage 50Sage 50 Cloud (US)Sage Cloud EnablementSage 50Sage 50 Cloud (FR)Sage 50 Cloud (UK)Sage 200 (ES)Sage Cloud Enablement

Update timeline

  1. investigating Jul 23, 2026, 04:01 PM UTC

    We are investigating a potential issue with the service. An update will be provided within 30 minutes.

  2. identified Jul 23, 2026, 04:26 PM UTC

    We have identified an issue preventing new customers to use their new product listed below and from doing any changes to existing entitlements.. We are working on a fix. The products/services affected are: -Sage 50 Cloud US -Sage 50 Cloud CA -Sage 50 Cloud FR -Sage 50 Cloud UKI -Connected Bridge Service -Organisation Service -Sage HR Suite - (DE) -Sage CoPilot (UKI) -Sage 100 (DE) -Sage HR Suite - (CA) -Sage 50 (DE) -Sage 50 for Accounts (CA) -Sage HR Suite - (US) -Sage 50 - Sage Expense (UKI) -Sage HR Suite - 100 (US) -Sage HR Suite - 300 (US) -Sage 100 Online SPP -Sage Connect (FR) -Sage 50 (ES) -Sage FRP1000 (FR) -Sage 200 (ES) -Sage Connect (US) -Sage Batigest (FR) -Sage 50 Faturação (PT) -Sage 50 Loja (PT) -Sage 50 Salários (PT) -Sage 50 Contabilidade (PT) -Sage 50 Cloud Contabilidade (PT) -Sage 50 Cloud Salários (PT) -Sage 50 Cloud Loja (PT) -Sage 50 Cloud Faturação (PT) -Sage 100 (PT) -Sage 100 Cloud (PT) -Sage for Accountants Pay per use (PT) -Sage for Accountants Cloud Pay per Use (PT) -Sage for Accountants Expert (PT) -Sage for Accountants Cloud Expert (PT)

  3. monitoring Jul 23, 2026, 06:51 PM UTC

    The services are performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the services.

  4. resolved Jul 24, 2026, 12:55 PM UTC

    The issue is resolved and the service continues to perform as expected.