Company Logo

Is there an System Health outage?

System Health status: Systems Active

Last checked: 8 minutes ago

Get notified about any outages, downtime or incidents for System Health and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

System Health outages and incidents

Outage and incident data over the last 30 days for System Health.

There have been 0 outages or incidents for System Health in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for System Health

Outlogger tracks the status of these components for Xero:

Analytics Active
Compliance (compliance.geoforce.com) Active
Device Data Ingestion Active
Device Manager (devices.geoforce.com) Active
GraphQL API (api.geoforce.com) Active
Readings REST API (readings.geoforce.com) Active
Service Verification (dir.geoforce.com) Active
Track and Trace (app.geoforce.com) Active
Component Status
Analytics Active
Compliance (compliance.geoforce.com) Active
Device Data Ingestion Active
Device Manager (devices.geoforce.com) Active
GraphQL API (api.geoforce.com) Active
Readings REST API (readings.geoforce.com) Active
Service Verification (dir.geoforce.com) Active
Track and Trace (app.geoforce.com) Active

Latest System Health outages and incidents.

View the latest incidents for System Health and check for official updates:

Updates:

  • Time: Aug. 11, 2022, 7:38 p.m.
    Status: Resolved
    Update: This incident has been resolved. Customers should be able to retrieve readings via the Readings API once again for any date.
  • Time: Aug. 11, 2022, 6:04 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring results.
  • Time: Aug. 11, 2022, 5:50 p.m.
    Status: Identified
    Update: The issue has been identified and we are currently working on implementing a fix.
  • Time: Aug. 11, 2022, 5:03 p.m.
    Status: Investigating
    Update: We are continuing to investigate the issue.
  • Time: Aug. 11, 2022, 4:02 p.m.
    Status: Investigating
    Update: We are currently investigating slow requests and failures in the readings API.

Updates:

  • Time: Aug. 6, 2022, 4:26 a.m.
    Status: Resolved
    Update: Our final maintenance job completed a few minutes ago. The CPU usage has returned to normal and there have been no more timeouts on the readings API. We are calling this incident closed. A root cause analysis meeting will be scheduled for this week.
  • Time: Aug. 6, 2022, 4:26 a.m.
    Status: Resolved
    Update: Our final maintenance job completed a few minutes ago. The CPU usage has returned to normal and there have been no more timeouts on the readings API. We are calling this incident closed. A root cause analysis meeting will be scheduled for this week.
  • Time: Aug. 6, 2022, 4:16 a.m.
    Status: Monitoring
    Update: The team has put changes into place that reduce the load on the database servers, but we have more changes that need to be made to fully reduce the load to where it needs to be. Customers who rely on the Readings REST API may experience timeouts on their API requests. Over the last couple of hours, API call success rate has climbed from about 60% to about 80%. We've got one more maintenance operation that we plan on running tonight; in fact, the team kicked that off momentarily ago. We'll update you all when that maintenance operation has completed.
  • Time: Aug. 6, 2022, 4:16 a.m.
    Status: Monitoring
    Update: The team has put changes into place that reduce the load on the database servers, but we have more changes that need to be made to fully reduce the load to where it needs to be. Customers who rely on the Readings REST API may experience timeouts on their API requests. Over the last couple of hours, API call success rate has climbed from about 60% to about 80%. We've got one more maintenance operation that we plan on running tonight; in fact, the team kicked that off momentarily ago. We'll update you all when that maintenance operation has completed.
  • Time: Aug. 6, 2022, 12:48 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 6, 2022, 12:48 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 6, 2022, 12:42 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 6, 2022, 12:42 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 6, 2022, 12:42 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Aug. 6, 2022, 12:42 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Aug. 5, 2022, 11:46 p.m.
    Status: Investigating
    Update: We are currently investigating slow requests and failures in the readings API.
  • Time: Aug. 5, 2022, 11:46 p.m.
    Status: Investigating
    Update: We are currently investigating slow requests and failures in the readings API.

Updates:

  • Time: July 1, 2022, 5:22 p.m.
    Status: Resolved
    Update: Between 2022-07-01 00:30 UTC and 2022-07-01 06:00 UTC, Geoforce experienced significant delays when processing incoming device readings. The delays affected reading processing, and telemetry. No device readings are known to have been lost. The cause of the incident is still being investigated.

Updates:

  • Time: July 1, 2022, 5:22 p.m.
    Status: Resolved
    Update: Between 2022-07-01 00:30 UTC and 2022-07-01 06:00 UTC, Geoforce experienced significant delays when processing incoming device readings. The delays affected reading processing, and telemetry. No device readings are known to have been lost. The cause of the incident is still being investigated.

Updates:

  • Time: June 21, 2022, 5:53 p.m.
    Status: Postmortem
    Update: Between 2022-06-10 22:05 UTC and 2022-06-14 04:27 UTC, Geoforce experienced significant delays when processing incoming device readings. The delays affected reading processing, location enrichment, telemetry, and trips. No device readings are known to have been lost. The cause of the incident was determined to be a corrupted device reading. Additionally, Geoforce’s internal response to this issue revealed holes in our incident response processes that both increased the time it took to address the issue and delayed the publication of status updates that our customers rely on. Five urgently needed remediation tasks were identified and work began immediately.
  • Time: June 14, 2022, 2:16 p.m.
    Status: Resolved
    Update: This incident has been resolved. The post-processing backlog has been cleared.
  • Time: June 13, 2022, 11:15 p.m.
    Status: Investigating
    Update: We are running maintenance tasks that are planned to take a few hours. Our next update will be in the morning.
  • Time: June 13, 2022, 10:15 p.m.
    Status: Investigating
    Update: The backlog has started to climb again. Geoforce engineers are investigating the cause.
  • Time: June 13, 2022, 9:20 p.m.
    Status: Monitoring
    Update: We are continuing to watch the size of the post-processing backlogs and the amount of time it takes to perform the post processing tasks.
  • Time: June 13, 2022, 8:23 p.m.
    Status: Monitoring
    Update: The post-processing backlog is continuing to decrease in size.
  • Time: June 13, 2022, 7:15 p.m.
    Status: Identified
    Update: We have identified the issue that was causing the backlog, and the backlog has begun decreasing.
  • Time: June 13, 2022, 6:43 p.m.
    Status: Investigating
    Update: We have eliminated delays in initial processing for incoming messages. A backlog remains for post-processing.
  • Time: June 13, 2022, 6:41 p.m.
    Status: Investigating
    Update: We are continuing to track these delays. Delays are down to about 20 minutes.
  • Time: June 13, 2022, 6:37 p.m.
    Status: Investigating
    Update: We are investigating reports that we have delays in the processing and post-processing of incoming readings. Delays are averaging about 1 hour in length.

Check the status of similar companies and alternatives to System Health

Avalara
Avalara

Systems Active

Crisis Text Line
Crisis Text Line

Issues Detected

Jamf
Jamf

Systems Active

Mulesoft
Mulesoft

Systems Active

Meltwater
Meltwater

Systems Active

HashiCorp
HashiCorp

Systems Active

Datto
Datto

Issues Detected

Vox Media
Vox Media

Systems Active

Cradlepoint
Cradlepoint

Systems Active

Liferay
Liferay

Systems Active

Zapier
Zapier

Systems Active

Workato US
Workato US

Systems Active

Frequently Asked Questions - System Health

Is there a System Health outage?
The current status of System Health is: Systems Active
Where can I find the official status page of System Health?
The official status page for System Health is here
How can I get notified if System Health is down or experiencing an outage?
To get notified of any status changes to System Health, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of System Health every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free