Snapshot 20093

Document
Registry listing
URL
https://clayhr.statuspage.io/history.json
Fetched
HTTP status
200
Content type
application/json
Fetch mode
api
Size
10137 bytes
SHA-256 (raw)
0b0872d0027ebb06a997eb7ef1f265a53ac36a603185c7d42b6db27ea84793b2
SHA-256 (normalized text)
35222c795332099fc2c56fd9af0064787cc626dd1141ae5b6d9e27fdc516e4d7

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

{
  "pages": [
    {
      "end_time": "2026-09-30T23:59:59Z",
      "months": [
        {
          "incidents": [],
          "name": "September",
          "year": 2026
        },
        {
          "incidents": [],
          "name": "August",
          "year": 2026
        },
        {
          "incidents": [],
          "name": "July",
          "year": 2026
        }
      ],
      "start_time": "2026-07-01T00:00:00Z",
      "time_zone": "UTC"
    },
    {
      "end_time": "2026-06-30T23:59:59Z",
      "months": [
        {
          "incidents": [],
          "name": "June",
          "year": 2026
        },
        {
          "incidents": [
            {
              "code": "m7r8tk634n9t",
              "impact": "maintenance",
              "message": "The scheduled maintenance has been completed.",
              "name": "[Scheduled] Scheduled database maintenance – Cape Town (Africa Tikkun)",
              "timestamp": "May \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e06:00\u003c/var\u003e - \u003cvar data-var='time'\u003e08:58\u003c/var\u003e UTC"
            },
            {
              "code": "gkrfv3r3ztdx",
              "impact": "maintenance",
              "message": "The scheduled maintenance has been completed.",
              "name": "[Scheduled] Scheduled database maintenance – Africa (Cape Town)",
              "timestamp": "May \u003cvar data-var='date'\u003e23\u003c/var\u003e, \u003cvar data-var='time'\u003e06:00\u003c/var\u003e - \u003cvar data-var='time'\u003e07:59\u003c/var\u003e UTC"
            },
            {
              "code": "9zn51gfcyvxb",
              "impact": "maintenance",
              "message": "The scheduled maintenance has been completed.",
              "name": "[Scheduled] Scheduled database maintenance – North Virgnia (Prudential)",
              "timestamp": "May \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e06:00\u003c/var\u003e - \u003cvar data-var='time'\u003e08:28\u003c/var\u003e UTC"
            },
            {
              "code": "rlt9my84dgts",
              "impact": "maintenance",
              "message": "The scheduled maintenance has been completed.",
              "name": "[Scheduled] Scheduled database maintenance – North Virgnia (Prudential)",
              "timestamp": "May \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e08:59\u003c/var\u003e - \u003cvar data-var='time'\u003e08:59\u003c/var\u003e UTC"
            }
          ],
          "name": "May",
          "year": 2026
        },
        {
          "incidents": [
            {
              "code": "b23nsc61x136",
              "impact": "critical",
              "message": "ClayHR customers in the Singapore region experienced login issues due to a disruption in the secure communication channel between the authentication server and the application server. The application servers and database remained healthy throughout the incident; however, because the login flow depends on this secure channel, new login attempts were unable to complete. Users who were already logged into the system were not affected and could continue using the application without disruption. Our engineering team identified the broken secure communication link, restored the link between the authentication and application servers, and verified login flows were functioning correctly across the stack.",
              "name": "Login Issues in Singapore Region Due to Authentication Server Communication Failure",
              "timestamp": "Apr \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e00:15\u003c/var\u003e - \u003cvar data-var='time'\u003e00:15\u003c/var\u003e UTC"
            },
            {
              "code": "xxcqwy69s3wn",
              "impact": "major",
              "message": "A scheduled silent system upgrade was performed on multiple ClayHR stacks. Silent upgrades are designed to be deployed with zero downtime; however, in this instance the application entered an inconsistent state following the upgrade. The issue did not surface immediately — it took a few hours for the symptoms to manifest across affected stacks, after which our engineering team identified the root cause and worked to restore normal application behavior. During the period of inconsistency, some users may have experienced unexpected behavior or errors while using the application. We apologize for the inconvenience caused and appreciate your patience while we worked to fully stabilize the affected stacks.",
              "name": "Silent System Upgrade Caused Application Inconsistency Across Multiple Stacks",
              "timestamp": "Apr \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e19:00\u003c/var\u003e - \u003cvar data-var='time'\u003e19:00\u003c/var\u003e UTC"
            },
            {
              "code": "xyck2n6ws3nk",
              "impact": "maintenance",
              "message": "The scheduled maintenance has been completed.",
              "name": "[Scheduled] Scheduled database maintenance – Asia Pacific (Singapore)",
              "timestamp": "Apr \u003cvar data-var='date'\u003e19\u003c/var\u003e, \u003cvar data-var='time'\u003e05:57\u003c/var\u003e - \u003cvar data-var='time'\u003e08:38\u003c/var\u003e UTC"
            },
            {
              "code": "nlsf74v86b0w",
              "impact": "maintenance",
              "message": "The scheduled maintenance has been completed.",
              "name": "[Scheduled] Scheduled database maintenance – Europe (Stockholm)",
              "timestamp": "Apr \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e05:56\u003c/var\u003e - \u003cvar data-var='time'\u003e09:00\u003c/var\u003e UTC"
            }
          ],
          "name": "April",
          "year": 2026
        }
      ],
      "start_time": "2026-04-01T00:00:00Z",
      "time_zone": "UTC"
    },
    {
      "end_time": "2026-03-31T23:59:59Z",
      "months": [
        {
          "incidents": [
            {
              "code": "30z71vyd8fsk",
              "impact": "maintenance",
              "message": "The scheduled maintenance has been completed.",
              "name": "[Scheduled] Scheduled Database Maintenance – Service Downtime",
              "timestamp": "Mar \u003cvar data-var='date'\u003e29\u003c/var\u003e, \u003cvar data-var='time'\u003e06:11\u003c/var\u003e - \u003cvar data-var='time'\u003e10:30\u003c/var\u003e UTC"
            }
          ],
          "name": "March",
          "year": 2026
        },
        {
          "incidents": [
            {
              "code": "z98g047dcp88",
              "impact": "none",
              "message": "We rolled back the January 29th release to the previous stable version after observing instability and 15% performance degradation. The rollback was completed successfully and the platform is currently operating on the prior release. Our teams are actively investigating the root cause to ensure long-term stability. We will provide further updates once we have more information to share, and will deploy the newer release as soon as possible.",
              "name": "Service Update Following Rollback from Jan 29th 2026 Drop",
              "timestamp": "Feb \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e12:53\u003c/var\u003e - \u003cvar data-var='time'\u003e12:53\u003c/var\u003e UTC"
            }
          ],
          "name": "February",
          "year": 2026
        },
        {
          "incidents": [
            {
              "code": "ky8c71c5bdww",
              "impact": "minor",
              "message": "The issue has been fully resolved, and services are operating normally.",
              "name": "North Virginia Center: Intermittent Service Disruptions for Customers",
              "timestamp": "Jan \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e17:30\u003c/var\u003e - \u003cvar data-var='time'\u003e17:58\u003c/var\u003e UTC"
            },
            {
              "code": "0ztf83v04035",
              "impact": "major",
              "message": "This incident has been resolved. Team will continue to monitor in the coming days.",
              "name": "Asia Pacific Data Center Customers facing intermittent issues.",
              "timestamp": "Jan \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e11:42\u003c/var\u003e - \u003cvar data-var='time'\u003e12:34\u003c/var\u003e UTC"
            },
            {
              "code": "b282363rvb9m",
              "impact": "major",
              "message": "The UI-related issue affecting the ClayHR iOS application on devices running iOS 26.0 and above has been resolved.\nA fix has been implemented and released as part of iOS app version 2.5.68, addressing the compatibility issues introduced by recent iOS system-level changes.\nResolution Details:\n-- Issue fully resolved in version 2.5.68.\n-- Verified and validated on iOS 26.0 and above.\nNo data loss or functional impact observed\nUsers are advised to update the app to version 2.5.68 to ensure optimal performance.\nThank you for your patience and cooperation.",
              "name": "iOS App UI Issue on iOS 26.0 and Above",
              "timestamp": "Jan \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e23:15\u003c/var\u003e - Jan \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e07:04\u003c/var\u003e UTC"
            }
          ],
          "name": "January",
          "year": 2026
        }
      ],
      "start_time": "2026-01-01T00:00:00Z",
      "time_zone": "UTC"
    },
    {
      "end_time": "2025-12-31T23:59:59Z",
      "months": [
        {
          "incidents": [
            {
              "code": "7j6lk1kytxmf",
              "impact": "major",
              "message": "We identified that this incident was caused by a sudden spike in requests, along with a significant issue in our auto-scaling group that prevented our infrastructure from scaling up as expected.\n\nAs a result, the ClayHR application became temporarily unavailable for our North Virginia core production customers. During this period, some users experienced errors such as a 504 Application Gateway Timeout when trying to access the application.\n\nOur engineering team immediately investigated the issue, stabilized the environment, and corrected the auto-scaling configuration to prevent this from happening again. The total downtime experienced by affected customers was 40 minutes.\n\nWe have also implemented additional monitoring and safeguards to detect similar patterns more effectively in the future. We sincerely apologize for the inconvenience this caused and appreciate your patience while we worked to restore normal service.",
              "name": "ClayHR Application Down – North Virginia Region (504 Application Gateway Timeout)",
              "timestamp": "Dec \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e21:00\u003c/var\u003e - \u003cvar data-var='time'\u003e21:00\u003c/var\u003e UTC"
            }
          ],
          "name": "December",
          "year": 2025
        },
        {
          "incidents": [
            {
              "code": "9m0lqnz56knt",
              "impact": "major",
              "message": "ClayHR customers in North America and South America regions experienced application outage due to application started returning increased 504 Gateway Timeout errors.\n\nClayHR team identified that a sudden spike in incoming requests had overloaded the existing instances behind the Application Load Balancer, causing high response times and auto scaling failed to automatically replace these unhealthy instances.\n\nUnhealthy instances were manually rebotted.\n\nTotal downtime of 39 minutes was experienced for selected customers in North America and South American regions.",
              "name": "Selected customers in NA/SA regions not able to access ClayHR",
              "timestamp": "Nov \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e03:00\u003c/var\u003e - \u003cvar data-var='time'\u003e03:00\u003c/var\u003e UTC"
            }
          ],
          "name": "November",
          "year": 2025
        },
        {
          "incidents": [],
          "name": "October",
          "year": 2025
        }
      ],
      "start_time": "2025-10-01T00:00:00Z",
      "time_zone": "UTC"
    }
  ]
}