JumpRope incident

Reporting Server Unresponsive

Resolved on January 2, 2024.

postmortem Jan 02, 2024, 08:51 PM UTC

Due to a long-standing known issue, our administrative reporting server - which handles scheduled reports and certain read-only reporting views for admins and internal use - needs to be periodically rebooted or it will eventually crash. This normally occurs as part of our schedule devops duties, but was not performed as scheduled over the holiday break. We’ll add some automations to prevent this lapse in the future. We apologize for any inconvenience.

Started
Jan 02, 2024, 02:00 PM UTC
Resolved
Jan 02, 2024, 02:00 PM UTC
Duration
–
Detected by Pingoru
Jan 02, 2024, 02:00 PM UTC

Update timeline

  1. resolved Jan 02, 2024, 08:51 PM UTC

    For a brief period this morning, our administrative reporting server forgot to come back to work after the holiday break. It was restarted and operational by approximately 9:45am ET and only impacted certain read-only reports under Admin > Reports.

  2. postmortem Jan 02, 2024, 08:51 PM UTC

    Due to a long-standing known issue, our administrative reporting server - which handles scheduled reports and certain read-only reporting views for admins and internal use - needs to be periodically rebooted or it will eventually crash. This normally occurs as part of our schedule devops duties, but was not performed as scheduled over the holiday break. We’ll add some automations to prevent this lapse in the future. We apologize for any inconvenience.

Your product runs on more than JumpRope

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →