Code Climate Status

All Systems Operational

codeclimate.com Website and API Operational

Test Coverage Operational

Quality Analysis Operational

Code Climate Velocity (Beta) Operational

GitHub Operational

AWS ec2-us-east-1 Operational

AWS s3-us-standard Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

System Metrics Month Week Day

Error Rate

Fetching

Analysis processing time

Fetching

Past Incidents

Jun 25, 2018

No incidents reported today.

Jun 24, 2018

No incidents reported.

Jun 23, 2018

No incidents reported.

Jun 22, 2018

No incidents reported.

Jun 21, 2018

No incidents reported.

Jun 20, 2018

[Quality] Delayed Analysis Results

Resolved - The incident has been resolved.
Jun 20, 11:38 EDT

Monitoring - The service that schedules code analysis was briefly unavailable this morning, causing work to queue up. Service has been restored and the backlog is being processed. Apologies for the inconvenience.
Jun 20, 10:06 EDT

Jun 19, 2018

No incidents reported.

Jun 18, 2018

No incidents reported.

Jun 17, 2018

No incidents reported.

Jun 16, 2018

No incidents reported.

Jun 15, 2018

No incidents reported.

Jun 14, 2018

[Velocity] Degraded performance processing data

Resolved - This incident has been resolved.
Jun 14, 18:09 EDT

Update - We are continuing to investigate this issue.
Jun 14, 18:08 EDT

Update - We are continuing to investigate this issue.
Jun 14, 12:31 EDT

Investigating - Our high-priority data processing pipeline is behind. We're investigating.
Jun 14, 12:30 EDT

[Velocity] Degraded performance processing data

Resolved - This incident has been resolved.
Jun 14, 11:53 EDT

Identified - We've identified an issue preventing new servers from provisioning correctly during a scheduled rotation. This caused reduced capacity and eventually caused our queues to back up. We've fixed the problem and expect the pipeline to catch up.
Jun 14, 02:50 EDT

Jun 13, 2018

[Velocity] Degraded performance processing data

Resolved - This incident has been resolved.
Jun 13, 18:48 EDT

Monitoring - Our systems have caught up but we're still unclear on the cause of the spike and will continue to investigate.
Jun 13, 18:26 EDT

Investigating - Our high-priority data processing queue is behind. We're investigating.
Jun 13, 16:51 EDT

Jun 12, 2018

No incidents reported.

Jun 11, 2018

No incidents reported.