Sage incident

Banking Service - Operational

Minor Resolved View vendor source →
Started
Mar 20, 2026, 03:34 PM UTC
Resolved
Mar 20, 2026, 03:34 PM UTC
Duration
Detected by Pingoru
Mar 20, 2026, 03:34 PM UTC

Affected components

Sage 200 Professional SPC (UKI)

Update timeline

  1. resolved Mar 20, 2026, 03:34 PM UTC

    We identified an issue in the UK preventing a subset of customers using open banking from authenticating bank feeds. All other product functionality was working as expected. Customers were being presented with an error message: "You did not complete the sign-in process. Click Sign in and enter your online banking information". As a workaround, customers were able to reauthenticate by retrying the connection or disconnecting and reconnecting. The products/services affected were: -Sage 200 Professional (UKI) versions 2018 - 2024 R1 The issue is now resolved and the service is available and performing as expected.

Looking to track Sage downtime and outages?

Pingoru polls Sage's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Sage reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Sage alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Sage for free

5 free monitors · No credit card required