New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages — May 2026
Monitor Features overview Vendor status Uptime & synthetic checks Certificate lifecycle Operate Incident management Live demo
By goal Replace your stack Why ServiceAlert Competitor comparisons Alternatives directory By signal Reliability hub   · Uptime rankings   · SLA compliance Outage map
Services
Check & scan SSL security grader Status checker DNS lookup Response time WHOIS lookup Calculators SLA calculator Downtime calculator Embed Status badges All tools →
Pricing
Guides Help center Uptime monitoring RUM & analytics Teams & shared monitors Developer API reference Status badges Learn Blog Outage reports FAQ Changelog
Dashboard
Sage

Banking Service - Partial Outage

Minor Impact Identified Ongoing May 18, 2026

Incident Lifecycle

Investigating Investigating Investigating Identified Identified Identified Identified Identified

Incident Timeline

Identified
Third-Party FNB has applied a fix to the issue. Please note that while customers are able to complete an onboard there will be a delay in the new transactions coming through and therefore transactions will be pulled throughout today, 21st of May and back to normal tomorrow on the 22nd of May.
May 21, 2026 at 9:10 AM UTC
Identified
Third-party provider, FNB is working on a fix. Thank you for your patience as we work to resolve this issue.
May 20, 2026 at 12:13 PM UTC
Identified
The third-party provider, FNB is continuing to investigate the issue. We appreciate your patience as we work to resolve this issue.
May 19, 2026 at 4:10 PM UTC
Identified
We are continuing to work on a fix for this issue.
May 19, 2026 at 1:22 PM UTC
Identified
Third-Party FNB has acknowledged the issue and are working on resolving it as a top priority. We appreciate your patience as we work to resolve this issue.
May 18, 2026 at 3:37 PM UTC
Investigating
We have identified an issue in South Africa where customers using FNB bank are experiencing re-authentication errors when trying to onboard new customers and syncing the latest transactions. Customers are presented with “authorization code not accepted when clients enter the authorisation code” error message.

The product/service impacted:
SBC Accounting ZA
Sage 50 ZA
Sage 200 Evolution
Sage Intacct

We are currently investigating.
May 18, 2026 at 8:54 AM UTC
Investigating
We have identified that customers in South Africa are experiencing severe slowness and failures when trying to use the product. The issue started at approximately 07:00 UTC on the 18th of May.

We are currently investigating.
May 18, 2026 at 8:44 AM UTC
Investigating
We are investigating a potential issue with the service. An update will be provided within 30 minutes.
May 18, 2026 at 8:17 AM UTC
Was your business affected by this Sage outage?
Set up instant alerts for Sage, be the first to know about outages via email, Slack, Teams, or Discord.
Set Up Alerts → View Sage History

Similar Sage Incidents

Sage Intacct - Partial Outage Minor May 25, 2026 Sage Intacct - Partial Outage Minor May 21, 2026 Banking Service - Partial Outage Minor May 20, 2026 Sage Active - Partial Outage Minor May 15, 2026 Sage People - Partial Outage Minor May 15, 2026