by HonkWatch

Is Sage down in Bosnia and Herzegovina?

No problems reported with Sage right now

Bosnia and Herzegovina No reports in the last hour checked just now
Sage reports no current incident. Updated 7 Nov, 01:38 UTC, just now · Official status page
Report a problemFollow community reports
Change country

Reports from people in Bosnia and Herzegovina

Last 24 hours · Bosnia and Herzegovina · times in UTC

0 reports

No community reports in the last 24 hours from Bosnia and Herzegovina. Having trouble? Add your report.

024 06:0012:0018:0000:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 7 Nov, 01:38 UTC

Report a problem with Sage

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Bosnia and Herzegovina

Monitor the provider status with HonkWatch

Get monitoring alerts for Sage

HonkWatch watches the Sage status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. Sage is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Bosnia and Herzegovina. The report chart above is filtered to Bosnia and Herzegovina.

Our own checks of sage.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Port Louis: loaded in 169 ms Doha: loaded in 974 ms Madrid: loaded in 129 ms Cape Town: loaded in 165 ms Tokyo: loaded in 209 ms New York: loaded in 164 ms Johannesburg: loaded in 132 ms Toronto: loaded in 153 ms Bangalore: loaded in 335 ms Seoul: loaded in 178 ms Amsterdam: loaded in 135 ms Seattle: loaded in 144 ms London: loaded in 150 ms São Paulo: loaded in 1852 ms Frankfurt: loaded in 135 ms Querétaro: loaded in 154 ms Sydney: loaded in 139 ms New Jersey: loaded in 263 ms Tel Aviv: loaded in 191 ms St. Louis: loaded in 311 ms Singapore: loaded in 165 ms Osaka: loaded in 203 ms Santiago: loaded in 156 ms Lauterbourg: loaded in 153 ms Dallas: loaded in 224 ms Melbourne: loaded in 288 ms Hong Kong: loaded in 144 ms Portsmouth: loaded in 214 ms Warsaw: loaded in 285 ms Los Angeles: loaded in 291 ms Jakarta: loaded in 146 ms Mumbai: loaded in 135 ms Hamina: loaded in 206 ms Atlanta: loaded in 174 ms Delhi: loaded in 130 ms
  • Port LouisReachable169 ms, just now
  • DohaReachable974 ms, just now
  • MadridReachable129 ms, just now
  • Cape TownReachable165 ms, just now
  • TokyoReachable209 ms, just now
  • New YorkReachable164 ms, just now
  • JohannesburgReachable132 ms, just now
  • TorontoReachable153 ms, just now
  • BangaloreReachable335 ms, just now
  • SeoulReachable178 ms, just now
  • AmsterdamReachable135 ms, just now
  • SeattleReachable144 ms, just now
  • LondonReachable150 ms, just now
  • São PauloReachable1852 ms, just now
  • FrankfurtReachable135 ms, just now
  • QuerétaroReachable154 ms, just now
  • SydneyReachable139 ms, just now
  • New JerseyReachable263 ms, 4 min ago
  • Tel AvivReachable191 ms, 4 min ago
  • St. LouisReachable311 ms, 4 min ago
  • SingaporeReachable165 ms, 4 min ago
  • OsakaReachable203 ms, 4 min ago
  • SantiagoReachable156 ms, 4 min ago
  • LauterbourgReachable153 ms, 4 min ago
  • DallasReachable224 ms, 4 min ago
  • MelbourneReachable288 ms, 4 min ago
  • Hong KongReachable144 ms, 4 min ago
  • PortsmouthReachable214 ms, 4 min ago
  • WarsawReachable285 ms, 4 min ago
  • Los AngelesReachable291 ms, 4 min ago
  • JakartaReachable146 ms, 5 min ago
  • MumbaiReachable135 ms, 5 min ago
  • HaminaReachable206 ms, 5 min ago
  • AtlantaReachable174 ms, 5 min ago
  • DelhiReachable130 ms, 5 min ago

This is separate from the status page: we request sage.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Sage

Sage

All 523 listed parts are working.

Incidents and maintenance

Open incidents

  • Certificates Renewal Sage 50 / 200 / Payroll - Operational (monitoring) Since 6 Nov, 15:36 UTC. Affects Sage 50 Accounts, Sage 200 Standard (UKI), Sage Business Cloud Payroll · Details
  • Sage 50 US/CA Authentication Issues - Operational (monitoring) Since 5 Nov, 22:32 UTC. Affects Sage 50 · Details
  • Remote Data Access (RDA) NA - Degraded Performance (monitoring) Since 30 Oct, 10:41 UTC. Affects Sage 50 · Details

Maintenance

  • Sage Intacct - Global - Scheduled Maintenance (planned) 7 Nov, 03:30 UTC to 7 Nov, 07:30 UTC. Affects Sage Intacct, Sage Intacct, Sage Intacct, Sage Intacct · Details
  • Sage Operations (SO) Global - Scheduled Maintenance (planned) 7 Nov, 04:00 UTC to 7 Nov, 07:00 UTC. Affects Sage Operations (SO), Sage Operations (SO), Sage Operations (SO), Sage Operations (SO) · Details
  • Sage Provisioning Portal (SEOS) - Scheduled Maintenance (planned) 8 Nov, 16:00 UTC to 8 Nov, 18:00 UTC. Affects Sage 300 People Managed Services, Sage 50 Cloud (US), Sage 100 Contractor Cloud, Sage 100 Partner Cloud (NA) and 10 more · Details
  • Ciel Données Mobiles for Sage 50 FR - Scheduled Maintenance (planned) 9 Nov, 20:00 UTC to 9 Nov, 22:00 UTC. Affects Ciel Données Mobiles for Sage 50 FR · Details
  • Sage People SFTP - Scheduled Maintenance (planned) 10 Nov, 18:00 UTC to 10 Nov, 20:00 UTC. Affects Sage People SFTP, Sage People SFTP · Details
  • Sage Intacct - Global - Scheduled Maintenance (planned) 14 Nov, 03:30 UTC to 14 Nov, 07:30 UTC. Affects Sage Intacct, Sage Intacct, Sage Intacct, Sage Intacct · Details
  • Sage Intacct - Global - Scheduled Maintenance (planned) 21 Nov, 03:30 UTC to 21 Nov, 07:30 UTC. Affects Sage Intacct, Sage Intacct, Sage Intacct, Sage Intacct · Details
Outage history

Last problem: 6 Nov, 15:42 UTC, partial outage for 1 h 21 min (1 of 513 parts affected: Europe / Sage Token Service).

Last 9030 days

12.85% of the time without a reported outage, since 2 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 84 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of sage.com that failed (9,445 checks). Shaded: when Sage's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 06:0012:0018:0000:00 0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 101 checks failed0% of 109 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 100 checks failed0% of 98 checks failed0% of 95 checks failed0% of 109 checks failed0% of 98 checks failed1% of 101 checks failed0% of 107 checks failed0% of 81 checks failed0% of 80 checks failed0% of 116 checks failed0% of 78 checks failed0% of 117 checks failed0% of 99 checks failed0% of 94 checks failed0% of 76 checks failed0% of 100 checks failed0% of 104 checks failed0% of 100 checks failed0% of 91 checks failed0% of 85 checks failed0% of 96 checks failed0% of 88 checks failed0% of 96 checks failed0% of 78 checks failed0% of 64 checks failed0% of 90 checks failed0% of 74 checks failed0% of 86 checks failed0% of 80 checks failed0% of 91 checks failed0% of 85 checks failed0% of 86 checks failed0% of 93 checks failed0% of 105 checks failed0% of 82 checks failed0% of 105 checks failed0% of 99 checks failed0% of 110 checks failed0% of 76 checks failed0% of 64 checks failed0% of 107 checks failed0% of 83 checks failed0% of 82 checks failed0% of 108 checks failed1% of 109 checks failed0% of 105 checks failed0% of 105 checks failed0% of 84 checks failed0% of 88 checks failed0% of 124 checks failed0% of 99 checks failed0% of 107 checks failed0% of 98 checks failed0% of 112 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 52 checks failed

Recent problems

6 Nov, 15:42 UTCPartial outage1 h 21 min1 of 513 parts affected: Europe / Sage Token Service
2 Nov, 10:49 UTCPartial outage3 d 23 hOpen incident: Sage Intacct - Operational
What can I try?

Having trouble with Sage?

  1. Compare reports from Bosnia and Herzegovina and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Sage down, or is it just me?

The Sage status page reports no problem and our own checks reach sage.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official Sage status page and load sage.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 7.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in Finance and accounting

See the live outage feed for Bosnia and Herzegovina · Find another service