Netchex incident

Azure Outage Confirmed Resolved

Minor Resolved View vendor source →

Netchex experienced a minor incident on April 24, 2026 affecting View Employees (View Employees) and Run Reports (Run Reports) and 1 more component, lasting 13h 3m. The incident has been resolved; the full update timeline is below.

Started
Apr 24, 2026, 01:12 PM UTC
Resolved
Apr 25, 2026, 02:15 AM UTC
Duration
13h 3m
Detected by Pingoru
Apr 24, 2026, 01:12 PM UTC

Affected components

View Employees (View Employees)Run Reports (Run Reports)Run Payroll (Run Payroll)View and Edit Timecards (View and Edit Timecards)Punch In / Punch Out (Punch In / Punch Out)Add Employees (Add Employees)Employee, Manager, and Admin Login (Employee, Manager, and Admin Login)

Update timeline

  1. 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: ...

  2. 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...

  3. 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. ...

  4. 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. ...

  5. 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...

  6. 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...

  7. 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...

  8. 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...

  9. 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...