- Detected by Pingoru
- Jun 01, 2026, 08:16 AM UTC
- Resolved
- Jun 01, 2026, 03:35 PM UTC
- Duration
- 7h 19m
Affected: Sage 50 Cloud (FR)
Timeline · 4 updates
-
investigating Jun 01, 2026, 08:16 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
identified Jun 01, 2026, 08:43 AM UTC
We have identified an issue in France where customer sites being migrated are failing. Existing sites and users are not impacted. We are currently investigating.
-
identified Jun 01, 2026, 10:52 AM UTC
We are continuing to investigate the cause of the issue. We appreciate your patience as we work to resolve this issue.
-
resolved Jun 01, 2026, 03:35 PM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 12:02 PM UTC
- Resolved
- Jun 01, 2026, 03:02 PM UTC
- Duration
- 3d 2h
Affected: Sage Business Cloud Digital Network
Timeline · 4 updates
-
investigating May 29, 2026, 12:02 PM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
investigating May 29, 2026, 12:19 PM UTC
We have identified a potential issue that could impact customers in Europe and North America, resulting in degraded performance for the directory service. We are currently investigating.
-
monitoring May 29, 2026, 04:04 PM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
resolved Jun 01, 2026, 03:02 PM UTC
The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 12:56 PM UTC
- Resolved
- May 28, 2026, 02:39 PM UTC
- Duration
- 1h 43m
Affected: Sage 200 Standard (UKI)
Timeline · 3 updates
-
investigating May 28, 2026, 12:56 PM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
investigating May 28, 2026, 01:08 PM UTC
We identified an issue where a small subset of customers in the UK are unable to access their companies in the application. We are currently investigating.
-
resolved May 28, 2026, 02:39 PM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 09:54 AM UTC
- Resolved
- May 28, 2026, 09:51 AM UTC
- Duration
- 23h 57m
Affected: Sage 50
Timeline · 2 updates
-
investigating May 27, 2026, 09:54 AM UTC
Nous avons identifié un incident affectant les clients Sage 50 en France, où les transactions bancaires ne sont pas reçues dans leurs fichiers Sage 50. Les clients sont susceptibles de voir le message d’erreur suivant " Aucune transaction bancaire depuis votre dernière connexion". Nous sommes actuellement en cours d’investigation. ------------------------------------------------------------------------------------ We have identified an issue affecting Sage 50 customers in France, where bank transactions are not being received in their Sage 50 files. Customers are presented with “no bank transactions since your last login” error message. We are currently investigating.
-
resolved May 28, 2026, 09:51 AM UTC
Le problème est résolu et le service fonctionne comme prévu. ---------------------------------------------- The issue is resolved and the service is performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 10:13 AM UTC
- Resolved
- May 19, 2026, 11:50 AM UTC
- Duration
- 1d 1h
Affected: AutoEntryAutoEntryAutoEntryAutoEntryAutoEntrySage Ai Document ExtractionSage Ai Document ExtractionSage Business Cloud Accounting ZASage Ai Document ExtractionSage Business Cloud Accounting (NA)Sage IntacctSage IntacctSage IntacctSage Ai Document ExtractionSage Business Cloud Accounting (UKI)Sage Intacct
Timeline · 6 updates
-
investigating May 18, 2026, 10:13 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
identified May 18, 2026, 12:46 PM UTC
We have identified an issue preventing customers in Europe from using the Document Extraction service. The products/services affected is: - AutoEntry We are currently investigating.
-
identified May 18, 2026, 04:20 PM UTC
We are continuing to investigate the cause of the issue and are working on a fix. The products/services affected are: AutoEntry Sage Intacct
-
identified May 18, 2026, 06:17 PM UTC
We appreciate your patience and we will let you know as soon as this issue is resolved.
-
monitoring May 18, 2026, 06:59 PM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
resolved May 19, 2026, 11:50 AM UTC
The issue is resolved and the services continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 08:49 AM UTC
- Resolved
- May 27, 2026, 02:56 PM UTC
- Duration
- 9d 6h
Affected: Sage Business Cloud Accounting ZA
Timeline · 17 updates
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 08:17 AM UTC
- Resolved
- May 22, 2026, 05:09 PM UTC
- Duration
- 4d 8h
Affected: Banking ServiceSage 50Sage Business Cloud Accounting ZASage Intacct
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 10:10 AM UTC
- Resolved
- May 16, 2026, 03:28 PM UTC
- Duration
- 1d 5h
Affected: Sage Active
Timeline · 3 updates
-
investigating May 15, 2026, 10:10 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
identified May 15, 2026, 10:22 AM UTC
We identified that customers in France, Spain, Germany are unable to access the Sage Active iOS mobile application. Only the iOS application is affected and Sage Active is performing as expected. We are currently investigating.
-
resolved May 16, 2026, 03:28 PM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 10:07 AM UTC
- Resolved
- May 18, 2026, 01:56 PM UTC
- Duration
- 3d 3h
Affected: Sage PeopleSage PeopleSage PeopleSage PeopleSage People
Timeline · 3 updates
-
investigating May 15, 2026, 10:07 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
identified May 15, 2026, 10:23 AM UTC
We have identified that a subset customers in the UK are unable to transfer Payflow files to vendor SFTP endpoints. All other product functionality is working as expected. We are currently investigating.
-
resolved May 18, 2026, 01:56 PM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 04:38 PM UTC
- Resolved
- Jun 10, 2026, 03:38 PM UTC
- Duration
- 26d 23h
Affected: AutoEntryAutoEntryAutoEntryAutoEntryAutoEntry
Timeline · 7 updates
-
investigating May 14, 2026, 04:38 PM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
monitoring May 14, 2026, 04:54 PM UTC
Earlier today we identified a global issue preventing Desktop Sync App customers from using the service integrations. Customers were being presented with the error message: "The operation has timed out”. All other product functionalities were performing as expected. The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
monitoring May 22, 2026, 01:46 PM UTC
We continue to work on a permanent fix for this issue, and will continue to closely monitor the service performance.
-
investigating Jun 09, 2026, 03:05 PM UTC
We have identified that Sage 50 Canada customers are unable to access AutoEntry. We are currently investigating.
-
identified Jun 09, 2026, 03:26 PM UTC
We have identified the cause of the Sage 50 Canada customers not being able to access AutoEntry are we are working on a fix. We apologise for any inconvenience this might cause.
-
monitoring Jun 10, 2026, 06:36 AM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
resolved Jun 10, 2026, 03:38 PM UTC
The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 02:30 PM UTC
- Resolved
- May 14, 2026, 02:30 PM UTC
- Duration
- —
Affected: BrightpearlBrightpearlBrightpearlBrightpearlBrightpearl
Timeline · 1 update
-
resolved May 15, 2026, 06:08 AM UTC
We identified that between yesterday and this morning a subset of customers globally received duplicate purchase orders. All other product functionality was working as expected. The issue is now resolved and the duplicates have been deleted. We apologise for any inconvenience this might caused.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 08:03 PM UTC
- Resolved
- May 26, 2026, 10:39 AM UTC
- Duration
- 13d 14h
Affected: E-Invoicing
Timeline · 12 updates
Read the full incident report →
- Detected by Pingoru
- May 10, 2026, 09:39 AM UTC
- Resolved
- May 10, 2026, 11:13 AM UTC
- Duration
- 1h 33m
Affected: Sage Global KnowledgeBaseSage Global KnowledgeBase
Timeline · 3 updates
-
investigating May 10, 2026, 09:39 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
identified May 10, 2026, 09:57 AM UTC
We have identified an issue preventing customers globally from accessing the service. We are currently investigating.
-
resolved May 10, 2026, 11:13 AM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 09:53 AM UTC
- Resolved
- May 08, 2026, 10:34 AM UTC
- Duration
- 41m
Affected: Sage 300 People Managed ServicesRemote Data Access (RDA) NASage 50Remote Data Access (RDA) UKISage 50
Timeline · 4 updates
-
investigating May 08, 2026, 09:53 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
investigating May 08, 2026, 10:08 AM UTC
none
-
investigating May 08, 2026, 10:13 AM UTC
We have identified an issue preventing customers in the UK and NA from onboarding new customers via connected bridge service. So far, 19 customers reported the issue. This issue was reported 09:03 UTC on May 8th. The products/services affected are: - Sage 50 UKI - Sage 50 CA - Sage 50 US - Remote Data Access (RDA) UKI - Remote Data Access (RDA) NA - Sage VIP Payroll (ZA) - Sage HR - Sage 300 People Managed Services (ZA) We have identified the cause of the issue and are currently implementing a fix.
-
resolved May 08, 2026, 10:34 AM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 07, 2026, 09:33 AM UTC
- Resolved
- May 07, 2026, 11:11 AM UTC
- Duration
- 1h 38m
Affected: Payments Acceptance ServicePayments Acceptance Service
Timeline · 3 updates
-
investigating May 07, 2026, 09:33 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
investigating May 07, 2026, 10:06 AM UTC
We have identified an issue preventing customers in Europe and North America from accessing the service. We are currently investigating.
-
resolved May 07, 2026, 11:11 AM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 09:14 PM UTC
- Resolved
- May 06, 2026, 09:24 PM UTC
- Duration
- 9m
Affected: Sage Business Cloud Accounting (NA)
Timeline · 2 updates
-
investigating May 06, 2026, 09:14 PM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
resolved May 06, 2026, 09:24 PM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 02:26 PM UTC
- Resolved
- May 11, 2026, 01:38 PM UTC
- Duration
- 4d 23h
Affected: Sage Online (FR)
Timeline · 5 updates
-
investigating May 06, 2026, 02:26 PM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
monitoring May 06, 2026, 02:54 PM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
identified May 07, 2026, 09:35 AM UTC
Nous avons identifié qu’un sous-ensemble de clients rencontre encore des problèmes lors de l’utilisation de Sage Flux Bancaires. Nous sommes actuellement en cours d’investigation. --------------------- We have identified that a subset of customers are still experiencing issues while using Sage Flux Bancaires. We are currently investigating.
-
monitoring May 07, 2026, 02:29 PM UTC
Le service fonctionne comme prévu. Notre priorité est d’éviter que la situation ne se reproduise et nous surveillons de près le service. ------------ The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
resolved May 11, 2026, 01:38 PM UTC
Le problème est résolu et le service continue de fonctionner comme prévu. -------------------------------------------- The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 10:42 AM UTC
- Resolved
- May 06, 2026, 08:43 PM UTC
- Duration
- 10h
Affected: Sage Business Cloud Accounting (UKI)
Timeline · 4 updates
-
investigating May 06, 2026, 10:42 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
investigating May 06, 2026, 10:59 AM UTC
We have identified an issue preventing customers in the UK from accessing the iOS mobile version of SBC Accounting. Customers are presented with an EC02 error or asked to create an account when attempting to log into the IOS mobile app. We are currently investigating.
-
identified May 06, 2026, 12:34 PM UTC
We have identified the cause of the issue and we are working on a fix. We appreciate your patience as we work to resolve this issue.
-
resolved May 06, 2026, 08:43 PM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 10:22 AM UTC
- Resolved
- May 06, 2026, 01:42 PM UTC
- Duration
- 3h 20m
Affected: Sage Online (FR)Sage Token Service
Timeline · 3 updates
-
investigating May 06, 2026, 09:55 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
monitoring May 06, 2026, 10:22 AM UTC
We identified that French customers using the desktop products listed below were getting an STS validation token error messages when trying to enable services. All other product functionality was working as expected. The products/services impacted by this were: -Sage 50 Accounts FR -Sage 100 Accounts FR -Sage SMDE FR -Sage Batigest -Sage Batigest Connect -Sage FRP 1000 -Sage 100 Payroll FR -Sage 100 Comptabilite -Sage Generation Experts -Sage Flux Bancaires The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service
-
resolved May 06, 2026, 01:42 PM UTC
Le problème est résolu et le service continue de fonctionner comme prévu. --------------------- The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 10:02 PM UTC
- Resolved
- May 06, 2026, 08:47 AM UTC
- Duration
- 10h 45m
Affected: ISV MarketplaceISV MarketplaceISV Marketplace
Timeline · 3 updates
-
investigating May 05, 2026, 10:02 PM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
monitoring May 05, 2026, 10:41 PM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
resolved May 06, 2026, 08:47 AM UTC
The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 04:01 PM UTC
- Resolved
- May 07, 2026, 12:29 PM UTC
- Duration
- 1d 20h
Affected: Sage 200 Standard (UKI)
Timeline · 7 updates
-
investigating May 05, 2026, 04:01 PM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
identified May 05, 2026, 04:38 PM UTC
We have identified an issue where UKI customers are experiencing latency when using the product. We are currently working on a fix.
-
identified May 05, 2026, 04:40 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring May 05, 2026, 08:27 PM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
monitoring May 06, 2026, 12:14 PM UTC
We have scheduled a maintenance for the product to apply further improvements on Wednesday 6th May for 30 minutes, between 21:00 BST and 21:30 BST. We apologise for any inconvenience this might cause.
-
monitoring May 06, 2026, 08:44 PM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
resolved May 07, 2026, 12:29 PM UTC
The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 07:33 AM UTC
- Resolved
- May 04, 2026, 02:56 PM UTC
- Duration
- 7h 22m
Affected: Sage DPW Cloud
Timeline · 4 updates
-
investigating May 04, 2026, 07:33 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
investigating May 04, 2026, 07:43 AM UTC
We identified an issue where a small subset of customers in Austria are experiencing a prolonged loading time when navigating the service. Some are getting error messages and timeouts. We are currently investigating.
-
monitoring May 04, 2026, 09:32 AM UTC
The service is performing as expected. Avoiding a reoccurrence is our priority as we closely monitor the service.
-
resolved May 04, 2026, 02:56 PM UTC
The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 08:32 AM UTC
- Resolved
- May 19, 2026, 12:08 PM UTC
- Duration
- 20d 3h
Affected: Sage 50Sage 50Sage 50 Accounts
Timeline · 4 updates
-
investigating May 05, 2026, 08:42 AM UTC
We have identified that customers in the UK, Ireland and ZA are getting an error message when trying to use the email functionality on the following products: -Sage 50 Accounts UK -Sage 50 Payroll UK -Sage 50 Payroll Ireland -Sage 50c ZA -Sage Pastel Payroll We are currently investigating.
-
investigating May 05, 2026, 08:42 AM UTC
We are continuing to investigate the cause of the issue. As a workaround, when using the following listed below, customers can save the e-mail as draft and then send the saved draft. -Sage 50 Accounts UK -Sage 50 Payroll UK -Sage 50 Payroll Ireland We apologise for any inconvenience this may cause.
-
identified May 08, 2026, 09:51 AM UTC
If you are experiencing this issues while using one of the UK products please check the instructions in the following link. If you are experiencing the issue while using on of the South African products please reach out to your local customer services or business partners that will provide you with a workaround.
-
resolved May 19, 2026, 12:08 PM UTC
The incident is being resolved. If you continue to experience this issues while using one of the UK products please check the instructions in the following link. If you you continue to experience the issue while using on of the South African products please reach out to your local customer services or business partners that will provide you with a workaround.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 08:32 AM UTC
- Resolved
- May 05, 2026, 08:37 AM UTC
- Duration
- 6d
Affected: Sage 50Sage 50 AccountsSage 50 Payroll
Timeline · 3 updates
-
investigating Apr 29, 2026, 08:32 AM UTC
We have identified that customers in the UK, Ireland and ZA are getting an error message when trying to use the email functionality on the following products: -Sage 50 Accounts UK -Sage 50 Payroll UK -Sage 50 Payroll Ireland -Sage 50c ZA -Sage Pastel Payroll We are currently investigating.
-
investigating Apr 30, 2026, 11:09 AM UTC
We are continuing to investigate the cause of the issue. We apologise for any inconvenience this may cause.
-
resolved May 05, 2026, 08:37 AM UTC
Le problème est résolu et le service continue de fonctionner comme prévu. ----------------------------------- The issue is resolved and the service continues to perform as expected.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 08:19 AM UTC
- Resolved
- Apr 28, 2026, 10:42 AM UTC
- Duration
- 2h 22m
Affected: Developer Experience CommunityDeveloper Experience CommunityDeveloper Experience CommunityDeveloper Experience CommunityDeveloper Experience Community
Timeline · 3 updates
-
investigating Apr 28, 2026, 08:19 AM UTC
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
-
investigating Apr 28, 2026, 08:32 AM UTC
We have identified that customers globally are unable to use forms in Developer Experience (https://developer.sage.com/). When customers click on submit on the forms nothing happens, no error message is displayed.
-
resolved Apr 28, 2026, 10:42 AM UTC
The issue is resolved and the service is available and performing as expected.
Read the full incident report →
