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.

Source: systemstatus.netchex.com

28incidents recorded
27last 12 months
8last 90 days
6 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Netchex in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026113 of 720 (2%)
May 202622 of 744 (0%)
June 202610 of 720 (0%)
July 202679 of 744 (1%)
August 202611 of 744 (0%)
September 202656 of 720 (1%)
October 202626 of 744 (1%)
November 202600 of 222 (0%)

Incidents, newest first

Major November 18, 2025 Cloudflare Errors Resolved 1d 1h View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more

Started Nov 18, 2025, 01:03 PM UTC· resolved Nov 19, 2025, 02:50 PM UTC

  1. investigating Nov 18, 2025, 01:03 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: Our team is aware that our content delivery network provider, Cloudflare, is currently experiencing issues. Our engineering teams are currently working to mitigate the impact: Cloudflare Status

  2. investigating Nov 18, 2025, 02:18 PM UTC

    We have temporarily mitigated the issues with site accessibility, but users may still see some performance degradation until the global Cloudflare issues have been resolved. Additionally NetInsights Reporting remains unavailable.

  3. resolved Nov 19, 2025, 02:50 PM UTC

    Cloudflare resolved issues yesterday afternoon. Mitigations that were put in place yesterday morning were removed yesterday eventing and all systems remain operational.

Read the full incident report →

Major November 18, 2025 Issue Under Investigation: Cloudflare Errors 8m View Employees, Run Reports, Run Payroll, View and Edit Timecards and 3 more

Started Nov 18, 2025, 12:11 PM UTC· resolved Nov 18, 2025, 12:19 PM UTC

  1. investigating Nov 18, 2025, 12:11 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: Our team is aware that our content delivery network provider, Cloudflare, is currently experiencing issues. Our engineering teams are currently working to mitigate the impact: Cloudflare Status

  2. resolved Nov 18, 2025, 12:19 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. For additional information about this event, Cloudflare is posting updates here: Cloudflare Status

Read the full incident report →

Minor October 31, 2025 Investigating Reports of an Issue 12m View and Edit Timecards

Started Oct 31, 2025, 02:26 PM UTC· resolved Oct 31, 2025, 02:39 PM UTC

  1. investigating Oct 31, 2025, 02:26 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: [Insert early indicators—e.g., "Some users are unable to access the login page or complete punches."]

  2. resolved Oct 31, 2025, 02: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.

Read the full incident report →