Sage incident

Sage 50 Cloud (FR) - Partial Outage

Minor Resolved View vendor source →

Sage experienced a minor incident on June 12, 2026 affecting Sage 50 Cloud (FR), lasting 13d 6h. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2026, 09:32 AM UTC
Resolved
Jun 25, 2026, 03:54 PM UTC
Duration
13d 6h
Detected by Pingoru
Jun 12, 2026, 09:32 AM UTC

Affected components

Sage 50 Cloud (FR)

Update timeline

  1. investigating Jun 12, 2026, 09:13 AM UTC

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

  2. investigating Jun 12, 2026, 09:32 AM UTC

    We identified issue preventing a subset of Sage 50 Cloud (FR) customers in France from accessing the service. We are currently investigating

  3. investigating Jun 12, 2026, 11:00 AM UTC

    We are continuing to investigate the cause of the issue. Thank you for your patience as we work to resolve this issue.

  4. investigating Jun 12, 2026, 04:34 PM UTC

    We are continuing to investigate. Thank you for your understanding as we work to resolve this issue.

  5. investigating Jun 15, 2026, 04:02 PM UTC

    We are actively investigating the cause of the issue and appreciate your patience as we work to resolve it.

  6. investigating Jun 16, 2026, 02:59 PM UTC

    Nous continuons à enquêter sur la cause du problème. Si vous y êtes confronté, veuillez suivre les instructions figurant dans ce lien. ------------------------------------------------------- We continue to investigate the cause of the issue. If you are experiencing it, please follow the instructions in this link.

  7. monitoring Jun 19, 2026, 04:02 PM UTC

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

  8. identified Jun 22, 2026, 04:01 PM UTC

    Nous avons reçu des signalements indiquant que les clients continuent de rencontrer la même erreur. Nous continuons à enquêter sur la cause du problème. Si vous y êtes confronté, veuillez suivre les instructions figurant dans ce lien. Nous vous remercions de votre compréhension pendant que nous œuvrons à la résolution de ce problème. ------------------------------------------------------- We have received reports that customers are continuing to experience the same error. We continue to investigate the cause of the issue. If you are experiencing it, please follow the instructions in this link. Thank you for your understanding as we work to resolve this issue.

  9. identified Jun 23, 2026, 04:02 PM UTC

    Nous travaillons activement à la mise en place d’un correctif et poursuivons l’analyse de la cause du problème. Si vous y êtes confronté, veuillez suivre les instructions figurant dans ce lien. Merci de votre compréhension pendant que nous nous efforçons de résoudre ce problème. ------------------------------------------------------------------------------------- We are actively working on a fix and continue to investigate the cause of the issue. If you are experiencing it, please follow the instructions in this link.

  10. monitoring Jun 25, 2026, 10:50 AM UTC

    Le service fonctionne comme prévu. Éviter toute récurrence est notre priorité, et nous surveillons le service de près. ----------------------------------------------------------------------------- The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.

  11. resolved Jun 25, 2026, 03:54 PM UTC

    L’incident est résolu et le service continue de fonctionner comme prévu. ------------------------------------------------------------- The issue is resolved and the service continues to perform as expected.