Is Code Climate Down Right Now? Check if there is a current outage ongoing.

Users should no longer be experiencing hanging Quality statuses on newly opened pull requests. However, some users may continue to observe hanging Quality statuses on pull requests opened > 1-hour ago. In those cases, pushing a fresh commit should rectify the issue. We'll continue to monitor.

We have observed that one of our Git servers is experiencing difficulties in carrying out its usual activities. Some users may encounter high latency during Quality analysis.

Users should no longer be experiencing hanging Quality statuses on newly opened pull requests. However, some users may continue to observe hanging Quality statuses on pull requests opened > 1-hour ago. In those cases, pushing a fresh commit should rectify the issue. We'll continue to monitor.

We have observed that one of our Git servers is experiencing difficulties in carrying out its usual activities. Some users may encounter high latency during Quality analysis.

This incident has been resolved.

We've received reports of users hitting 504 errors when trying to access the Quality Classic application. We're currently investigating the issue.

This incident has been resolved.

We've identified the issue and implemented a fix. During this time, users may continue to experience delays in analysis while the system catches up. Additionally, if you notice that a Code Climate commit status is stuck in a yellow state, please push up a new commit.

We are investigating an issue with our database cluster used for Quality Analysis.

This incident has been resolved.

We are continuing to monitor for any further issues.

We've identified and resolved an issue with our analysis system. Users may experience slight delays in CI status checks.

This incident has been resolved.

The upstream provider has implemented a fix and analysis delays should begin to resolve. We're continuing to monitor.

Due to an ongoing issue with an upstream provider, some users may be experiencing delays in analysis. We're monitoring the situation.

Due to an ongoing issue with an upstream provider, some users may be experiencing delays in analysis. We're monitoring the situation.

The issue causing analysis delays due to upstream service issues has been resolved. Users should now experience normal processing times for analysis results. We will continue to monitor for any further issues.

Due to an upstream service currently experiencing issues, some users may continue to experience delayed analysis results. We are monitoring https://www.githubstatus.com/ for updates.

We are currently investigating an issue related to analysis delays.

This incident has been resolved.

After intervention, the code coverage processing time has increased and is now normal. We are operational and continuing to monitor.

We are currently investigating an internal alarm related to delays of processing code coverage results for some users.

This incident has been resolved

We are seeing an elevated rate of errors in the Velocity API and Velocity Web Application. Our Engineering team is currently investigating the cause of the errors.

This incident has been resolved.

The issue has been resolved

This incident has been resolved.

We are continuing to investigate this issue.

We have observed that one of our Git servers is experiencing difficulties in carrying out its usual activities. A small portion of users may encounter high latency during the analysis of pull requests.

This incident has been resolved.

Users should no longer be experiencing hanging Quality statuses on newly opened pull requests. However, some users may continue to observe hanging Quality statuses on pull requests opened > 1-hour ago. In those cases, pushing a fresh commit should rectify the issue. We'll continue to monitor.

We've identified the issue and implemented a remediation. We're continuing to monitor and will provide additional information shortly.

We've received reports that some users may be experiencing hanging builds on pull requests opened today. We're investigating and will provide more information as soon as possible.

We put in place a remediation that mitigates users hitting 500s when accessing their repositories on Quality. We'll continue to monitor.

We've received reports of some users hitting 500s when trying to view their repositories on Quality. We're investigating and will provide more information as soon as possible.

This incident has been resolved.

We implemented a fix and analysis times should begin to decrease for most users. We're continuing to monitor.

We've identified an issue which is causing delays in Quality analysis for some users. We're in the process of implementing a fix.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to monitor for any further issues.

We have taken steps to remediate the issue and will continue to monitor.

We're continuing to investigate site-wide issues with Quality at the moment. During this time, users may experience intermittent 500s when loading the app as well as delayed analysis.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Our monitoring has detected an issue with running code analysis in Quality. We are investigating the cause and will be working to get things back in order shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We've detected some issues with performing analysis on some of the repositories in Quality. We are investigating the cause now and will keep you updated as things develop.

This incident has been resolved.

We received customer reports experiencing 500 error responses when uploading coverage information. We are investigating.

This incident has been resolved.

We have noted an increase in the mean time associated with Quality Analysis. We are presently undertaking a comprehensive investigation to determine the underlying cause.

This incident has been resolved.

We have identified and fixed the issue. All API endpoints are now working as expected.

We are continuing to investigate this issue.

We are investigating elevated levels of errors in the Velocity API

This incident has been resolved.

Issue resolved

We are continuing to work on a fix for this issue.

Reports Builder is temporarily offline while we apply a necessary version upgrade

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We're investigating an issue with hanging analyses affecting some customers intermittently.

This incident has been resolved.

GitHub issues reported at https://www.githubstatus.com/ may result in customers experiencing some latency with Quality analysis.

This incident has been resolved.

A fix has been implemented and most data is now up to date. Contribution analysis remains delayed by approx. 4 hours; we expect this to resolve shortly.

We are continuing to investigate this issue.

Analysis of Engineering Data in the Velocity Web Application is delayed. Real time alerts are working as expected. Our Engineering team is investigating the issue.

This incident has been resolved.

We are continuing to work on a fix for this issue.

We are currently experiencing some issues when logging in the application. We are actively working on fixing the issue.

All systems are operating normally, so your analyses should be processing now as expected. If you are still seeing issues with hanging PR checks, please try pushing a new commit and that should resolve the issue.

We've rolled out a fix for the issue and are seeing analysis wait times dropping. Please continue to be patient and we should be back to normal shortly

We've identified the issue as having to do with our data processing infrastructure and are in the process of rolling out a fix to account for this. Users during this time might notice a delay in analysis but should be back to normal shortly.

We are noticing a spike in issues with Quality Analysis and are investigating what the issue might be.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue appears to be related to a recent DNS change internally. We have deployed a fix and are monitoring to make sure everything is working as expected.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Our data ingestion pipeline is experiencing some slowness; we are actively working on identifying the root cause and ingesting any missing data

The root cause has been identified and resolved. The Velocity application is now fully available for all users.

Stylesheets are failing to load for all users, affecting the Velocity Web Application. The Engineering team is actively investigating and will provide regular updates.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We have identified the problem and are working to get data up to date.

This incident has been resolved.

We've identified that some users may be experiencing a delay in Quality analysis results. We're investigating the cause.

This incident has been resolved.

Root cause has been identified and analysis latency is improving.

We are currently investigating this issue.

This incident has been resolved.

Reports on reports.codeclimate.com are currently being impacted.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

We are currently investigating this issue.

This incident has been resolved.

We are currently observing delays in data ingestion for the Velocity product. You may see delays in commits and issues being reflected in the Velocity web application. We are working to resolve this issue, and will provide an update once resolved.

This incident has been resolved.

Most users should no longer be experiencing delays in analysis, but we're continuing to monitor. For any users who continue to notice delays in analysis on pull request integration, pushing a new commit to the impacted branch may help.

We've identified issues with an upstream service which may be impacting analysis delays. We'll continue to monitor.

Some users may currently be experiencing delayed results on Quality analysis. We're investigating the cause.

This incident has been resolved.

We've identified a possible root cause and have made changes to mitigate the problem. While analysis times have improved, we'll continue to monitor the situation and provide updates.

We are currently experiencing issues performing analysis on repositories using Quality and builds appear to be hanging. Our engineering team is investigating what is causing the issue and will try and get things moving shortly.

The incident was resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We've identified the root cause of the issue and implemented a fix. We're continuing to monitor.

Some users may be experiencing delays in receiving analysis results. We're investigating the cause.

We are now all caught up with the delayed data

Our system is almost caught up, we are re enabling more computing power to handle new events

We are actively working on catching up with delayed data Events moving forward are ingested as they come

We are actively working on catching up with delayed data

Some data is still being delayed, but most recent data is coming through

We are currently investigating this issue.

This incident has been resolved.

We're investigating reports of 504s across varying codeclimate.com pages.

This incident has been resolved.

We are monitoring now the services.

The team identified the issue. We are processing data, but the agents are a few hours behind. However, today's data should be accessible.

We are currently investigating this issue. You may see data missing in reports.

At this time, users who push new commits should no longer be experiencing hanging pull request analysis. If you notice that an existing pull request continues to experience a hanging Code Climate status, it may require a new push to that branch.

We've implemented a fix and users should begin to see hanging pull request analysis clear shortly. We will continue to monitor.

We're aware that some users are still experiencing analysis delays and we are continuing to investigate. During this time, some users may notice an increase in failed builds and hanging statuses on their pull requests.

We've identified the cause of the analysis delays and implemented a fix. We will continue to monitor.

We are currently investigating this issue.

This incident has been resolved.

We've identified the issue and put a remediation in place. Some users may continue to experience delayed analysis results in the short-term. We will continue to monitor.

Some Quality users may be experiencing delays in pull request analysis. We're currently investigating the issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Customers using SAML for authentication are not able to login