pingoru pingoru Ropes had 14 outages in the last 2 years totaling 28h 13m of downtime, averaging 0.6 incidents per month.
There were 14 Ropes outages since October 29, 2025 totaling 28h 13m of downtime. Each is summarised below. Incident details, duration, and resolution information.
We've identified an outage at one of our inference providers, which is impacting our problem creation and result processing pipelines. Problem creation and result processing will be delayed at this time.
The issue with the inference provider is now resolved.
We've identified an infrastructure issue causing candidate workspaces to fail to load. Candidates may see a blank screen in place of their Ropes workspace.
Multiple fixes have been implemented, and we're monitoring for stability.
This incident has been resolved.
Ropes is experiencing degraded performance due to an outage on Node Package Manager. See npm status here: https://status.npmjs.org/
The issue is resolved. All functions operational.
We're observing increased errors rates when creating custom problems. Users may see delays when generating problems at this time. We've identified the root cause as authentication failures with GitHub, one of our providers. For the latest updates, refer to GitHub's status page: https://www.githubstatus.com/ We are not aware of any candidate-facing impact at this time.
GitHub has implemented a fix, and we are seeing error rates recover.
This incident has been resolved.
Some candidates are experiencing failures starting assessments, and some completed assessments are delayed in grading. We've identified the cause as high resource pressure on our workspace host and are actively mitigating.
We've identified the cause as a backlog of orphaned workspaces causing resource pressure on our assessment host. To protect in-progress candidates while we recover, we've temporarily paused new assessment starts. Cleanup is in progress and we'll re-enable starts once the host is healthy. We're reaching out directly to customers with affected in-progress assessments.
Cleanup is complete and we've successfully verified that new assessments can start. We've re-enabled assessment starts and are monitoring closely to confirm full recovery. Customers with candidates impacted during the outage will hear directly from our team.
Assessments are fully operational and candidates are starting new sessions successfully. Some completed assessments are still queued for grading and will finish processing over the next ~2 hours.
Candidates may see errors when attempting to start their assessment due to a downstream outage on GitHub. A portion of requests are still getting through. Track GitHub's status page for the latest updates: https://www.githubstatus.com/ Result processing and problem creation will also be delayed.
GitHub has implemented a fix. We are monitoring for any remaining errors.
This incident has been resolved.
Result processing is currently delayed due to a downstream outage by one of our model providers, OpenAI. Ropes Scout is also experiencing increased error rates. Candidates are not impacted. For the latest information, see the OpenAI status page https://status.openai.com/
The issue with the OpenAI API is now resolved. We are re-processing the backlog of results.
Due to an ongoing Bullhorn outage, we are seeing increased errors rates for customers running Ropes through the Bullhorn integration. Candidates are not impacted. For more information, see Bullhorn's status page: https://status.bullhorn.com/
Bullhorn has implemented a fix, and we are beginning to see recovery in error rates. Please let us know if you continue to see any issues sending Ropes assessments from Bullhorn.
This incident has been resolved.
GitHub is currently experiencing a major outage, which affects the availability of Ropes assessment workspaces. We will provide updates as we have them. For the most up-to-date outage information, see GitHub's status page directly: https://www.githubstatus.com/ We've toggled a setting to expose a banner informing candidates about the GitHub outage to ensure they are informed as to why they cannot begin the assessment.
According to its status page, GitHub has identified the source of the issue. We are continuing to monitor.
GitHub has implemented a mitigation, and our monitoring shows that requests to GitHub are now succeeding. Candidates can proceed with their assessments.
This incident has been resolved.
We're investigating the root cause and will post updates.
A fix has been implemented, and we are processing the existing queue. This may take ~1 hour to fully clear.
The pre-existing backlog of results has been processed. Thank you for your patience.
We've identified an issue causing workspaces to fail to start. The issue is caused by a downstream outage in one of our service providers, GitHub. We will provide updates as we have them. In the meantime, consult GitHub's status page for more information (https://www.githubstatus.com/).
GitHub has resolved their outage. Candidates can now access workspaces to complete their assessments.
We are currently investigating an issue causing results processing to be delayed. Results may take longer to transition from Processing to Completed states.
We have identified the issue causing results processing to be delayed. We're working on a fix to improve processing throughput and process queued requests.
A fix has been deployed and we are seeing signs of recovery. We appreciate your patience as our system processes the backlog of queued results.
Results processing has fully recovered. Processing times have returned to standard levels.
We are currently investigating delays with creating Ropes problems.
The delay is problem creation is due to the ongoing global outage from Microsoft Azure. You can follow Azure's status page (https://azure.status.microsoft/en-us/status) for the most up-to-date information on the outage. Once Azure sees signs of recovery, we will report back with an update.
Azure has deployed a fix, and we are starting to see problems get created again. Thank you for your patience.
The issue has been resolved. We appreciate your patience as our systems process all problem requests.