Home
Services
Sage

Sage sage.com

Is Sage down right now? Live status and outage tracker

No, Sage is up.

No outage detected, and no user reports in the last hour.

Sage's own status page: status.sage.com

Live Updated 4 min ago Data refreshes every 5 minutes

Not working for you? Official status pageStatus page

User reports, last 24 hours, 15 minutes a segment: 96 flowing 0 slow (elevated) 0 jammed (outage)

User reports, last 24 hours

1 report in total, counted in 15-minute windows

No problem reports came in for Sage in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 1 report. Worldwide, most recent reports were about login (50%) and app (50%). There has been no spike in reports since 29 October. These are user reports from the UK, where most people report Sage problems.

Around the world right now: normal in 18 other countries. Most reports in the last hour: South Africa 1. By country

NormalClose to the usual level24 h · 1 report
ElevatedMore than 1.5 times the usual levelNone in this chart
OutageMore than twice the usual level and far above the day's averageNone in this chart
Usual levelWhat a usual day sees at that timeAlmost none at this time of day

Reports, last hour

Quiet

Uptime, 24 h

100.00%

No outage windows

Last outage

None

In the last 24 hours

Busiest 15 minutes

1 report, 9 h ago

Last 24 hours

Sage outages and problems

In the past 24 hours, 1 user report came in for Sage. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 1 report, about 9 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Sage stayed at their usual level the whole time.

Official status

What Sage's status page says

Checking status.sage.com…

Report categories

What people can report about Sage

What went wrong

What people said was wrong in recent problem reports for Sage worldwide.

Login50%
App50%

Share of 2 recent reports that said what was wrong, from every country listed below.

World map

Sage reports around the world

In the last 24 hours, 4 problem reports about Sage came in from 4 countries. Right now reports are at the usual level in every country.

Outage now
Problems now
Normal

Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Country	Now	Last hour	24 hours
South Africa	Normal	1	1
The US	Normal	0	1
The UK numbers above	Normal	0	1
France	Normal	0	1
Australia	Normal	0	0
Canada	Normal	0	0
The UAE	Normal	0	0
Hong Kong	Normal	0	0
Austria	Normal	0	0
Belgium	Normal	0	0
India	Normal	0	0
Germany	Normal	0	0

Each country's status compares its reports with the usual level there. 7 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Sage problem spikes, last 30 days

Since 29 October, Sage had no outage spikes or periods of elevated reports.

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

France19
The UK10
The US5
South Africa3
Portugal1
The UAE0
Austria0
Australia0

Country history starts on 29 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 29 October 2026. Monthly reports for all services

Troubleshooting

How to fix Sage not working

Sage is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach sage.com over your own connection, right now. Nothing is sent to us or stored.

Check the official status page
The status page at status.sage.com shows whether a fault sits on Sage's side, which saves you tearing through settings for a problem you cannot fix. If an incident is posted there, wait it out; nothing you change locally will shift the outcome.
Load it in a private window
A private or incognito window opens the app without your saved cookies and extensions, so it separates a browser problem from an account problem in seconds. Should the page load cleanly there, clear cookies and site data for the service in your normal browser and sign in again.
Restart the Connection Manager
The desktop program reaches its data through a background process called Connection Manager, and a hung process leaves you on a stuck splash screen or throws a message that the connection to the data has been lost. Open Task Manager, end Sage 50 Connection Manager on the Processes tab, then launch the program again.
Run Check Data on the company file
Open the company, then go to File > Maintenance > Check Data to see whether the file itself carries damage. Errors in that report point to a corrupt company file, so restore your most recent backup before you touch anything else. The help centre covers the restore routine if you have not done one recently.

While Sage is down: what to use instead

Sage web app If the mobile app will not load, try signing in through Sage on the web.
Sage Help Centre Use the help centre to look up steps for a product issue while you wait.
Sage official status page Check Sage's status page for service updates before retrying.

Your device

Fix Sage on Windows, Mac, Android and iPhone

Sage on Windows

Fix: Restart the Sage 50 Connection Manager service in your Windows Services panel, or clear your browser cache if using Sage Business Cloud. Running the Sage desktop application as an administrator can also resolve launch issues.
Check: Verify if the Sage Connection Manager icon in the system tray is active, or try accessing the Sage login page through a web browser. You can also check the official Sage Status page for platform-wide outages.

Command Prompt

ping sage.comTest whether Sage's servers reply

nslookup sage.comCheck that Sage's DNS resolves

tracert sage.comTrace where the connection drops

ipconfig /flushdnsClear the DNS cache, then reload

Sage on Mac

Fix: Clear your browser cache and cookies, or try accessing Sage Business Cloud using a different browser like Safari or Chrome. Ensure that any active VPNs or firewalls are not blocking Sage domains.
Check: Try loading the Sage login portal in an Incognito window to see if it loads without cache interference. Check the Sage Status website to see if their cloud services are currently online.

Terminal

ping -c 4 sage.comTest whether Sage's servers reply

nslookup sage.comCheck that Sage's DNS resolves

traceroute sage.comTrace where the connection drops

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Sage on Android

Fix: Clear the Sage app cache in your device settings and check the Google Play Store for any pending updates. If the issue persists, reinstall the Sage app and restart your phone.
Check: Check if the Sage app displays connection errors on launch, or try logging into the Sage web portal using your mobile browser. Look for service alerts on the Sage status page.

Sage on iPhone and iPad

Fix: Update the Sage app via the App Store, or reinstall it to clear cached application data. Make sure that cellular data access is enabled for the Sage app in your iPhone settings.
Check: See if the Sage app fails to load beyond the splash screen or displays authentication errors. Check the Sage Status page using Safari to confirm if there is a wider server outage.

About

What happens when Sage goes down

Sage makes accounting and payroll software for small businesses, bookkeepers, and finance teams, with desktop and cloud products covering invoicing, bank feeds, and payroll runs. An outage interrupts the daily work of posting transactions, reconciling accounts, running payroll, and closing the month.

Logins usually stall first: the sign-in page accepts your credentials and then hangs, or the dashboard loads with empty panels. Posting an invoice can fail at save, and bank feeds stop refreshing, so reconciliation waits. Payroll runs are worse. A submission that times out leaves you unsure whether payslips went through, and problems are often partial, with one product or region down while another stays up, so check the official status page before you assume the whole service is out.

Servers and network

Sage IP address, servers and network

IPv4 addresses: 104.18.32.86
Show all 2
172.64.155.170
IPv6: Not offered
Network: AS13335 · Cloudflare, Inc., registered in the United States
Served through: Cloudflare · our check was answered by its Frankfurt (FRA) data centre
DNS hosted by: Cloudflare
HTTPS certificate: Issued by DigiCert Inc, valid until 21 Jan 2027 (81 days)
HTTP/3: Not advertised
Our check: Answered in 81 ms (it turned away our automated check, which is common)

Checked from our server in Frankfurt, Germany, 39 h ago, for www.sage.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from www.sage.com. Fastest from Milan (29 ms), slowest from Singapore (197 ms). Every location connected through Cloudflare, Inc. (AS13335), using 2 different addresses.

Location	Result	Time	Address reached
FrankfurtGermany	Up · HTTP 302	33 ms	104.18.32.86
ViennaAustria	Up · HTTP 302	42 ms	104.18.32.86
MilanItaly	Up · HTTP 302	29 ms	172.64.155.170
ParisFrance	Up · HTTP 302	48 ms	172.64.155.170
AmsterdamNetherlands	Up · HTTP 302	45 ms	172.64.155.170
MadridSpain	Up · HTTP 302	43 ms	172.64.155.170
WarsawPoland	Up · HTTP 302	93 ms	104.18.32.86
Los AngelesUSA	Up · HTTP 302	45 ms	172.64.155.170
São PauloBrazil	Up · HTTP 302	36 ms	104.18.32.86
SingaporeSingapore	Up · HTTP 302	197 ms	172.64.155.170
TokyoJapan	Up · HTTP 302	51 ms	172.64.155.170

Checked with check-host.net from its servers in these cities 39 h ago, for www.sage.com. Time is how long each server took to load the page.

Questions

Sage FAQ

Is Sage down right now?

The status at the top of this page shows whether user problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. It does not ping or probe anything, so check the official status page for platform-wide incidents. To tell whether the problem is only on your side, try signing in from a different network and open the same page in a private window.

Why does Sage Accounting say my invoice could not be saved?

A save error often comes from a lost connection during the upload or a session that timed out. Copy the invoice text somewhere safe, refresh the page, sign in again, and retry. If it still fails, try the mobile app on a different network, then contact Sage support through the help centre.

Why is my Sage 50 desktop app stuck on the splash screen?

A stuck splash screen usually points to a damaged local data path or an antivirus tool holding a file open. Restart the PC and check that your data folder is reachable from File Explorer. If the screen still hangs, reinstall the desktop client and restore from a recent backup.

Why does my Sage payroll submission keep getting rejected?

Payroll rejections often come from a mismatch between the employee details in the app and the records held by the tax authority, or from an expired payroll period that you are trying to submit late. Check each employee's name and tax identifier before you resubmit. If the rejection names a specific field, fix that field first; if it does not, download the latest payroll update and try again.

Why is my bank feed in Sage Accounting not updating?

Bank feeds can stall when the bank changes its login flow or when your connection consent expires. Open the banking area and reconnect the bank if the app shows a broken link. You can also delete and re-add the feed as a last resort, but download a statement first so you can match any missing entries.

For your site

Put the Sage status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

HTML

<a href="https://isitdownrightnow.app/services/sage/"><img src="https://isitdownrightnow.app/badge/sage.svg" alt="Sage status" height="20"></a>

Markdown, for README files

[![Sage status](https://isitdownrightnow.app/badge/sage.svg)](https://isitdownrightnow.app/services/sage/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Sage

The status on this page comes from user-submitted problem reports for Sage, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Sage, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Sage's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.