ADP outage history

Users reported the ADP app failing to load due to server issues, with errors seen when trying to access the platform. The disruption began around 4:15 AM UTC and persisted as more users encountered loading problems. StatusGator recorded an Early Warning Signal at 5:20 AM UTC, with no official status page updates from ADP to acknowledge the incident. The issue appeared to ease later in the window, with access returning around 5:41 AM UTC. A steady stream of user reports during the period reflected broad impact on routine payroll and time-tracking workflows.

Users across the United States faced sign-in problems and trouble loading the ADP app, hindering payroll processing and time-entry tasks. Reports described errors when signing in or loading dashboards, with messages such as 'Hang on, we are busy' and 'We are really busy' appearing in multiple locations. The impact began around 2:31 PM UTC and persisted through the afternoon, peaking as users attempted authentication and access to payroll features. Access gradually stabilized after 5:26 PM UTC, though some intermittent issues continued for hours. ADP does not publish an official status page for this incident, so public updates were limited to user-reported symptoms and StatusGator notices.

Impact began around 3:00 PM UTC as ADP users across the United States reported sign-in failures and payroll portal errors. Users encountered login problems, error messages, and payroll submission delays while trying to access the payroll portal and submit hours. Messages indicating unusually heavy demand appeared in several places, and the outage affected core payroll tasks, potentially delaying payroll processing for employers and employees. StatusGator detected issues at Oct 28, 2026 3:44 PM UTC ahead of any provider acknowledgement.

Users across the United States and Canada reported sign-in failures, slow server responses, and payroll-processing problems beginning at 1:24 PM UTC. The outage affected authentication, access to employee profiles, timekeeping, and payroll calculations, preventing many organizations from signing in or running payroll and leaving payroll data inaccessible. Reports described server errors, timecard access issues, and widespread degradation of payroll workflows throughout the afternoon.

StatusGator detected the issue at Oct 27, 2026 1:24 PM UTC, ahead of any provider updates. The volume of user reports increased through the afternoon, with signs of sign-in and payroll service degradation observed across the US and Canada. The Early Warning Signal ended at 5:47 PM UTC, but there were no observed ADP status page updates in the data.

Users across the United States faced a widespread outage that left ADP's payroll portal, timecard data, and HR dashboards inaccessible or sluggish. Payroll calculations and timecard loading were hindered, and sign-in problems were common, disrupting day-to-day payroll processing for many employers. First user reports appeared around 1:00 PM UTC, and StatusGator issued an Early Warning Signal at Oct 26, 2026 1:37 PM UTC before an official provider acknowledgment. The impact persisted into the afternoon and evening.

ADP customers in the United States and Canada faced a widespread outage affecting time clocks and access to ADP payroll and timekeeping apps. Time clocks went offline, timecards were unavailable, and payroll dashboards showed errors, disrupting daily HR and payroll workflows for many organizations. StatusGator detected connectivity issues at 12:52 PM UTC, ahead of any official acknowledgement from ADP.

The impact appeared broad across the United States and Canada, with a substantial volume of user reports through the afternoon and evening indicating ongoing connectivity problems across Time & Attendance, Workforce Now payroll/timekeeping, and related timecard access. The incident progressed through the day and was recorded as ending for StatusGator at 8:23 PM UTC. While ADP did not publish an official status page, affected users experienced disrupted timekeeping and payroll functionality for several hours across multiple regions.

ADP users attempting to pay on the ADP Pay Page encountered errors as the page failed to load, preventing payment submission and checkout. The issue surfaced around 7:45 PM UTC with reports continuing into the evening, including a noticeable cluster around 8:30 PM UTC before a resolution was reached by 8:44 PM UTC. Because ADP does not operate an official status page, there were no provider updates to reference in the incident timeline. StatusGator logged an Early Warning Signal at 8:45 PM UTC indicating pay page load failures, highlighting user-facing impact in payments processing.

ADP users experienced a brief outage affecting the timecard page, with reports that the page would not load due to internal errors. The disruption began at 4:19 AM UTC and was resolved by 4:26 AM UTC. A small number of US-based users reported issues, including a Phoenix, Arizona report describing the timecard page not loading. StatusGator detected the issue at Sep 20, 2026 4:19 AM UTC, ahead of any official acknowledgment by ADP.

ADP experienced a server error that rendered the platform unavailable, disrupting login and access to payroll and time-tracking features. Users across the United States reported 500 internal server errors and login failures, with symptoms including being unable to sign in or access features after login. The impact began around 3:35 PM UTC and appeared to be resolved by 4:22 PM UTC, lasting for roughly forty-seven minutes and affecting authentication and core services.

ADP experienced a brief disruption in its timecard service, preventing users from saving or accessing timecards. The impact began at 11:42 AM UTC and was resolved by 11:49 AM UTC, lasting roughly seven minutes. US-based users reported issues from Mount Joy, PA; Rehoboth Beach, DE; and Raleigh, NC, with errors like "bad request" and "an unknown error occurred while trying to save the timecard." Because ADP does not maintain an official public status page, there were no provider updates published during the incident. StatusGator issued an Early Warning Signal at 11:42 AM UTC indicating timecard save/access failures.