Netchex Outage History
Netchex unknown View live status →Pingoru has recorded 28 incidents for Netchex: 27 in the last 12 months and 8 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 13 of 720 (2%) |
| May 2026 | 2 | 2 of 744 (0%) |
| June 2026 | 1 | 0 of 720 (0%) |
| July 2026 | 7 | 9 of 744 (1%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 5 | 6 of 720 (1%) |
| October 2026 | 2 | 6 of 744 (1%) |
| November 2026 | 0 | 0 of 222 (0%) |
Incidents, newest first
Major October 27, 2026 Issue Under Investigation 3h 39m Employee, Manager, and Admin Login
Started Oct 27, 2026, 12:00 PM UTC· resolved Oct 27, 2026, 03:39 PM UTC
- investigating Oct 27, 2026, 01:33 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We're treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Some users are unable to reach Netchex from desktop web browsers and receive a "site can't be reached" error. The Netchex mobile app and mobile browsers are working normally.
- investigating Oct 27, 2026, 01:59 PM UTC
We've identified the root cause and are focused on implementing a solution. This remains a critical priority with all relevant teams engaged and collaborating. We'll provide updates on expected resolution time as progress continues. Known Impact / Preliminary Findings: Some users whose office network uses a Fortinet firewall are unable to reach Netchex from desktop web browsers following a recent firmware update to those devices. Netchex systems are operating normally. If you are affected, please contact your IT team or technology provider for assistance with your Fortinet device. In the meantime, you can regain access by connecting to a network that is not behind a Fortinet device, such as a mobile hotspot, or by using the Netchex mobile app.
- investigating Oct 27, 2026, 02:30 PM UTC
We've identified the root cause and are focused on implementing a solution. This remains a critical priority with all relevant teams engaged and collaborating. We'll provide updates on expected resolution time as progress continues. Known Impact / Preliminary Findings: Some users whose office network uses a Fortinet firewall are unable to reach Netchex following a recent firmware update to those devices. This affects any device connected to that network, including phones on the office Wi-Fi. Netchex systems are operating normally. If you are affected, please contact your IT team or technology provider for assistance with your Fortinet device. In the meantime, you can regain access by connecting to a network that is not behind a Fortinet device, such as a mobile hotspot, or by using your phone's cellular data instead of the office Wi-Fi.
- investigating Oct 27, 2026, 03:02 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we're closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: Our network provider has implemented a workaround that should restore access for clients whose office network uses a Fortinet firewall. If you are still unable to reach Netchex, please contact your IT team or technology provider for support with your Fortinet device. In the meantime, you can continue to work around the issue by connecting to a different network, such as a mobile hotspot or your phone's cellular data instead of the office Wi-Fi.
- resolved Oct 27, 2026, 03:39 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Major October 6, 2026 Issue Under Investigation 2h 13m View and Edit Timecards, Employee, Manager, and Admin Login
Started Oct 06, 2026, 01:22 PM UTC· resolved Oct 06, 2026, 03:35 PM UTC
- investigating Oct 06, 2026, 01:38 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We're treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Beginning around 8:20 AM CT, some users may be unable to log in to Netchex, or may see pages load slowly or not at all after signing in.
- investigating Oct 06, 2026, 01:48 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We're treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Some users continue to have trouble logging in, and pages may load slowly or fail to load after signing in, including the employee home page and timecards. Time clock punches are not affected. Our teams have identified a likely contributing change and are working on mitigation.
- investigating Oct 06, 2026, 02:23 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we're closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: Fixes have been applied and login and page load times are returning to normal. Users who still see slow loading or a spinning page should refresh their browser.
- investigating Oct 06, 2026, 02:41 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we're closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: Login and page load times have returned to normal and all services are operating. We are continuing to monitor closely before confirming full resolution. Users who still see a spinning page should refresh their browser.
- resolved Oct 06, 2026, 03:35 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Major September 30, 2026 Payroll run is currently failing 13m Run Payroll
Started Sep 30, 2026, 09:50 PM UTC· resolved Sep 30, 2026, 10:03 PM UTC
- investigating Sep 30, 2026, 09:50 PM UTC
The development team is currently investigating the issue
- resolved Sep 30, 2026, 10:03 PM UTC
The payroll run issue is resolved
Major September 24, 2026 Issue Under Investigation 1h Run Payroll
Started Sep 24, 2026, 05:03 PM UTC· resolved Sep 24, 2026, 06:03 PM UTC
- investigating Sep 24, 2026, 05:57 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We're treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. **Known Impact / Preliminary Findings:** Some clients are unable to submit payroll after running it and receive an error message. Running and reviewing payroll are not affected.
- resolved Sep 24, 2026, 06:03 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Minor September 21, 2026 Some reports are unavailable 2h Run Reports
Started Sep 21, 2026, 03:00 PM UTC· resolved Sep 21, 2026, 05:00 PM UTC
- identified Sep 21, 2026, 03:00 PM UTC
We detected that some reports are unavailable in Netchex NetInsight Reporting is affected Total Compensation Statements The team is actively working on fixing these reports.
- resolved Sep 21, 2026, 05:00 PM UTC
The issue has been mitigated and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization.
Minor September 17, 2026 Investigating Reports of an Issue 50m Employee, Manager, and Admin Login
Started Sep 17, 2026, 12:26 AM UTC· resolved Sep 17, 2026, 01:17 AM UTC
- investigating Sep 17, 2026, 12:26 AM UTC
We've received reports of a potential service disruption. We're urgently investigating and working to understand the scope of impact. Our SRE and engineering teams have been activated and are treating this as a top priority. Known Impact / Preliminary Findings: Issues logging into employee dashboard
- investigating Sep 17, 2026, 01:04 AM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: We have identified the issue and are releasing a fix.
- resolved Sep 17, 2026, 01:17 AM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Minor September 16, 2026 Fix Deployment in Progress 2h 8m View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more
Started Sep 16, 2026, 05:50 PM UTC· resolved Sep 16, 2026, 07:58 PM UTC
- investigating Sep 16, 2026, 05:50 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery.
- investigating Sep 16, 2026, 06:35 PM UTC
A fix is continuing to be applied to affected systems. We are seeing services return to normal under most circumstances. All hands continue to be on deck and we’re closely monitoring the rollout to confirm full recovery.
- resolved Sep 16, 2026, 07:58 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust; resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Minor August 25, 2026 System Slowness 30m View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more
Started Aug 25, 2026, 07:30 PM UTC· resolved Aug 25, 2026, 08:00 PM UTC
- investigating Aug 25, 2026, 07:30 PM UTC
We’ve identified the root cause and are focused on implementing a solution. This remains a critical priority with all relevant teams engaged and collaborating. We’ll provide updates on expected resolution time as progress continues. Known Impact / Preliminary Findings: A recent deployment drove increased system load.
- investigating Aug 25, 2026, 07:55 PM UTC
Recent changes have been reverted and performance is returning to normal.
- resolved Aug 25, 2026, 08:00 PM UTC
Performance has been restored
Minor July 30, 2026 Investigating Reports of an Issue 7h 46m Run Payroll
Started Jul 30, 2026, 02:15 PM UTC· resolved Jul 30, 2026, 10:01 PM UTC
- investigating Jul 30, 2026, 02:15 PM UTC
We've received reports of a potential service disruption. We're urgently investigating and working to understand the scope of impact. Our SRE and engineering teams have been activated and are treating this as a top priority. Known Impact / Preliminary Findings: Our integration with Dealertrack is currently experiencing elevated errors.
- investigating Jul 30, 2026, 02:18 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: We are deploying an update to address the errors being seen in our Dealertrack integration.
- investigating Jul 30, 2026, 02:33 PM UTC
Unfortunately, the initial fix did not fully resolve the issue. Our engineering and SRE teams are analyzing new data and actively pursuing alternative solutions. This remains our highest priority, and we are committed to resolving it as quickly and effectively as possible. Known Impact / Preliminary Findings: Initial attempt has not resolved the issue. We are actively working with Dealertrack to identify and resolve the problem.
- investigating Jul 30, 2026, 04:20 PM UTC
Unfortunately, the initial fix did not fully resolve the issue. Our engineering and SRE teams are analyzing new data and actively pursuing alternative solutions. This remains our highest priority, and we are committed to resolving it as quickly and effectively as possible. Known Impact / Preliminary Findings: We are continuing to work with dealertrack to resolve this problem
- investigating Jul 30, 2026, 06:21 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: We have identified the issue in partnership with Dealertrack. A recent update to their security infrastructure has blocked traffic coming from Netchex. Netchex deployed an update earlier today to support the new infrastructure, but a lingering issue is currently being addressed by Dealertrack.
- resolved Jul 30, 2026, 10:01 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Minor July 28, 2026 Issue Under Investigation 12m View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more
Started Jul 28, 2026, 07:25 PM UTC· resolved Jul 28, 2026, 07:38 PM UTC
- investigating Jul 28, 2026, 07:25 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We’re treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Slowness and timeouts being reported on mulitple pages across Netchex
- investigating Jul 28, 2026, 07:32 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: A fix is currently underway. Most users should begin seeing normal performance again. We are continuing to monitor for any other impacts.
- resolved Jul 28, 2026, 07:38 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Notice July 15, 2026 Service Restored –
Started Jul 15, 2026, 01:30 PM UTC· resolved Jul 15, 2026, 01:30 PM UTC
- resolved Jul 15, 2026, 01:30 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization.
Minor July 15, 2026 Fix Deployment in Progress – Punch In / Punch Out
Started Jul 15, 2026, 01:30 PM UTC· resolved Jul 15, 2026, 01:30 PM UTC
- resolved Jul 15, 2026, 01:30 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery.
Minor July 15, 2026 Investigating Reports of an Issue – Punch In / Punch Out
Started Jul 15, 2026, 12:26 PM UTC· resolved Jul 15, 2026, 12:26 PM UTC
- resolved Jul 15, 2026, 12:26 PM UTC
We've received reports of a potential service disruption in Time and Attendance. Specifically that users are getting a blank page when trying to punch in or out. We're urgently investigating and working to understand the scope of impact. Our SRE and engineering teams have been activated and are treating this as a top priority.
Minor July 13, 2026 Fix Deployment in Progress – View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more
Started Jul 13, 2026, 08:35 PM UTC· resolved Jul 13, 2026, 08:35 PM UTC
- resolved Jul 13, 2026, 08:35 PM UTC
A fix has been deployed across affected systems around 11:15 am this morning. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery.
Minor July 10, 2026 Investigating Reports of an Issue 1h 26m View and Edit Timecards, Punch In / Punch Out
Started Jul 10, 2026, 03:00 PM UTC· resolved Jul 10, 2026, 04:27 PM UTC
- investigating Jul 10, 2026, 03:00 PM UTC
We've received reports of a potential service disruption. We're urgently investigating and working to understand the scope of impact. Our SRE and engineering teams have been activated and are treating this as a top priority. Known Impact / Preliminary Findings: Slow or intermittent failures viewing timecards, and some users are seeing errors when punching in and out.
- resolved Jul 10, 2026, 04:27 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Notice June 10, 2026 Issues with Payroll Run - Service Restored – Run Payroll
Started Jun 10, 2026, 04:46 PM UTC· resolved Jun 10, 2026, 04:46 PM UTC
- resolved Jun 10, 2026, 04:46 PM UTC
Around 11:46 AM, our team identified an issue with Payroll Run that impacted a subset of clients. The issue was triaged and determined to be associated with a partial release that was subsequently rolled back. The issue should now be resolved. All systems are currently stable. Our teams will continue to monitor closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization.
Minor May 20, 2026 Investigating Reports of an Issue 1h 19m View Employees, Run Reports
Started May 20, 2026, 04:21 PM UTC· resolved May 20, 2026, 05:40 PM UTC
- investigating May 20, 2026, 04:21 PM UTC
We've received reports of a potential service disruption. We're urgently investigating and working to understand the scope of impact. Our SRE and engineering teams have been activated and are treating this as a top priority. Known Impact / Preliminary Findings: We are investigating reports of some pages not showing updates for recent changes.
- resolved May 20, 2026, 05:40 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Major May 7, 2026 Issue Under Investigation - Punch In/Punch Out Outage 47m Punch In / Punch Out
Started May 07, 2026, 08:00 PM UTC· resolved May 07, 2026, 08:47 PM UTC
- investigating May 07, 2026, 08:00 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We’re treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Punch In/Punch Out Outage
- resolved May 07, 2026, 08:47 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization.
Minor April 24, 2026 Azure Outage Confirmed Resolved 13h 3m View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more
Started Apr 24, 2026, 01:12 PM UTC· resolved Apr 25, 2026, 02:15 AM UTC
- investigating Apr 24, 2026, 01:12 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We’re treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Performance issues one employee and timecard pages
- investigating Apr 24, 2026, 01:37 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: We have identified the cause of the performance issue, a mitigation is being rolled out and services should begin restoring shortly
- investigating Apr 24, 2026, 04:14 PM UTC
Unfortunately, the initial fix did not fully resolve the issue. Our engineering and SRE teams are analyzing new data and actively pursuing alternative solutions. This remains our highest priority, and we are committed to resolving it as quickly and effectively as possible. Known Impact / Preliminary Findings: Ongoing issues in navigation menus
- investigating Apr 24, 2026, 05:03 PM UTC
Unfortunately, the initial fix did not fully resolve the issue. Our engineering and SRE teams are analyzing new data and actively pursuing alternative solutions. This remains our highest priority, and we are committed to resolving it as quickly and effectively as possible. Known Impact / Preliminary Findings: Microsoft Azure has acknowledged a service outage impacting our region. We are beginning failover procedures for impacted services: https://azure.status.microsoft/en-us/status
- investigating Apr 24, 2026, 06:42 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: Azure is reporting a fix being rolled out to our region. We are seeing services recover as well. Our team is continuing to actively monitor: https://azure.status.microsoft/en-us/status
- investigating Apr 24, 2026, 08:37 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
- investigating Apr 24, 2026, 09:13 PM UTC
Our top engineering and SRE teams are actively investigating the issue. We’re treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Seeing additional reports of peformance issues. Azure is still reporting impacts in our region: https://azure.status.microsoft/en-us/status
- investigating Apr 25, 2026, 12:29 AM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: Azure is reporting restoration of services again. We are seeing conditions in Netchex return to normal. Our team is continuing to monitor at this time.
- resolved Apr 25, 2026, 02:15 AM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
- postmortem May 04, 2026, 11:13 PM UTC
On Friday, April 24, 2026, the Netchex platform experienced extended, intermittent service disruption throughout the day, including failed sign-ins, slow or failed page loads, and difficulty reaching key parts of the system. We sincerely apologize for the impact this had on you and your employees. Your trust matters to us. Below is what happened, how we worked through it, and the steps we’re taking to reduce the chance of a repeat. What Happened Customers experienced intermittent disruption from approximately 8:12 AM CT until full resolution at 9:15 PM CT, in two main waves. The first wave began at approximately 8:12 AM CT, with performance issues and intermittent failures on employee and timecard pages, later extending to platform navigation menus. Mitigations rolled out during the morning, and conditions partially improved through the early afternoon as our cloud provider deployed their fix. A second, broader wave began at approximately 4:13 PM CT as the upstream condition re-emerged, affecting sign-in, navigation, and overall site responsiveness. Conditions began returning to normal at approximately 7:29 PM CT, and we posted the all-clear at 9:15 PM CT after close monitoring. No customer data was lost, altered, or exposed, and there was no compromise to authentication or account security. Failed requests produced error pages and sign-in failures, not partial or incorrect data. What Caused It The disruption was caused by a regional incident in Microsoft Azure’s East US region, where portions of the Netchex platform are hosted. A prior update to core Azure regional infrastructure contained a latent defect that surfaced under load Friday morning. As Microsoft executed a staged rollback, the same condition appeared in turn across all three availability zones in the region. Several Netchex services are deployed redundantly across these zones so that any single-zone failure does not affect customers. Because all three zones were impacted at different points, that protection was not sufficient on its own. The morning and late-afternoon waves were two symptoms of the same regional event — first appearing in one zone, then re-appearing in another during Microsoft’s recovery. How We Fixed It Our Engineering and SRE teams launched a coordinated response as soon as the morning impact was identified, restarting affected services and deploying targeted mitigations to clear stuck connections and restore capacity while the upstream condition persisted. After Microsoft acknowledged the regional incident around midday, we began failover procedures for impacted services and prepared a larger contingency to move affected services onto infrastructure outside the impacted region. When the second wave began in the late afternoon, the team continued operational mitigations and stayed ready to execute the contingency. Microsoft completed their rollback before that was needed; conditions began returning to normal at approximately 7:29 PM CT, and we validated end-to-end functionality before posting the all-clear at 9:15 PM CT. Our Commitment to Improvement We fell short of the reliability standard you expect from us. While the originating fault was in our cloud provider’s infrastructure, we own the customer experience on our platform, and there is meaningful work we can do to limit how much an upstream regional event reaches you. The following actions are underway or being accelerated as a direct result of this incident. Granular per-service regional failover. Our business continuity plan supports a full-site cross-region failover, and that capability remains in place — but this incident showed it is the wrong tool for a partial regional impairment. We are accelerating in-flight work to enable per-service failover at a much finer granularity, redirecting only the specific services affected to a healthy region without moving the entire platform. This will materially reduce both the scope and duration of customer impact during regional events. Faster detection and triage. We are reviewing how the morning impact was detected and how quickly customer communication began, and tightening internal alerting on cloud dependency health so early signals reach our on-call engineers — and our status page — faster than they did on Friday. Improved handling of unhealthy service instances. During the morning impact, a small number of instances entered a degraded state and kept receiving a share of customer traffic before being recycled. We are tightening the health-check and pool-eviction settings so persistently unhealthy instances are removed from rotation automatically rather than continuing to serve requests. We are committed to providing a platform you can depend on. These actions are how we learn from this incident and earn back your full confidence. Thank you for your patience and continued partnership.
Minor March 4, 2026 Investigating Reports of an Issue 41m Run Payroll
Started Mar 04, 2026, 02:37 PM UTC· resolved Mar 04, 2026, 03:18 PM UTC
- investigating Mar 04, 2026, 02:37 PM UTC
We've received reports of a potential service disruption. We're urgently investigating and working to understand the scope of impact. Our SRE and engineering teams have been activated and are treating this as a top priority. Known Impact / Preliminary Findings: Dealertrack Imports and GL Submissions
- resolved Mar 04, 2026, 03:18 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Major February 6, 2026 Service Instability 12h 25m Employee, Manager, and Admin Login
Started Feb 06, 2026, 08:30 AM UTC· resolved Feb 06, 2026, 08:55 PM UTC
- identified Feb 06, 2026, 08:30 AM UTC
We are currently investigating reports of potential issues affecting log in. Our engineering team is actively looking into the root cause, and we will provide an update as soon as we have more information.
- resolved Feb 06, 2026, 08:55 PM UTC
We have identified the issue and implemented a fix.
Major January 12, 2026 Timecard Editor is failing to show employees – View and Edit Timecards
Started Jan 12, 2026, 09:51 PM UTC· resolved Jan 12, 2026, 09:51 PM UTC
- resolved Jan 12, 2026, 09:51 PM UTC
The issue has been resolved in production
Minor January 8, 2026 Issue Under Investigation - Move to Pay 1h 43m Run Payroll
Started Jan 08, 2026, 02:46 PM UTC· resolved Jan 08, 2026, 04:30 PM UTC
- investigating Jan 08, 2026, 02:46 PM UTC
Our top engineering and SRE teams are actively investigating reports of issues with moving to pay. We’re treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Moving to pay is currently not functional
- investigating Jan 08, 2026, 03:04 PM UTC
A possible fix is being deployed across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: During the deployment of this fix some services may be temporarily unavailable. Any affected services will return to full functionality shortly after the deployment of this fix is complete.
- investigating Jan 08, 2026, 04:16 PM UTC
A possible fix is being finalized across affected systems. If successful, services should begin returning to normal shortly. All hands are on deck and we’re closely monitoring the rollout to confirm full recovery. Known Impact / Preliminary Findings: During this time some services, including move to pay and NetGuide task assignment, will remain unavailable. Other services may be briefly unavailable while we apply the fix.
- resolved Jan 08, 2026, 04:30 PM UTC
The issue has been resolved and all systems are currently stable. Our teams will continue to monitor performance closely to ensure full recovery holds. We appreciate your patience and trust—resolving this was a top priority across our organization. More technical details on the issue and resolution will be shared shortly.
Minor November 22, 2025 Company Selection Issues - Resolved 1d 14h
Started Nov 22, 2025, 04:00 AM UTC· resolved Nov 23, 2025, 06:40 PM UTC
- investigating Nov 22, 2025, 04:00 AM UTC
Our top engineering and SRE teams are actively investigating the issue. We’re treating this with the highest urgency and working to identify the root cause. Thank you for your patience as we work quickly toward resolution. Known Impact / Preliminary Findings: Company Dropdown not functioning properly for clients with multi-company organizations
- resolved Nov 23, 2025, 06:40 PM UTC
The issue has been resolved. If you continue to see the issue, please perform a hard refresh (CTRL+SHIFT+R), try with Incognito, or clear your local browser cache. Thanks for your patience while we resolved the issue.
Minor November 19, 2025 Performance Restored 27m View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more
Started Nov 19, 2025, 03:15 PM UTC· resolved Nov 19, 2025, 03:43 PM UTC
- identified Nov 19, 2025, 03:15 PM UTC
We are currently experiencing system-wide performance degradation, resulting in slower page load times and occasional errors. Our engineering team has identified the root cause and is actively deploying the fix. We anticipate service stability to be fully restored within the next hour. We apologize for the inconvenience and will provide a final update once complete.
- resolved Nov 19, 2025, 03:43 PM UTC
The engineering team has successfully applied the fix and performance metrics have returned to normal. We appreciate your patience and apologize for any disruption this incident may have caused.