Code Climate Outage History

Code Climate is up right now

Pingoru has recorded 1 incident for Code Climate: 1 in the last 12 months and 0 in the last 90 days.

Source: status.codeclimate.com

1incidents recorded
1last 12 months
0last 90 days
27 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Code Climate in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 20 (0%)

Incidents, newest first

Minor March 13, 2026 Data Ingestion Delays 1d 3h Code Climate Platform

Started Mar 13, 2026, 12:41 PM UTC· resolved Mar 14, 2026, 04:10 PM UTC

  1. investigating Mar 13, 2026, 12:41 PM UTC

    We are currently investigating an issue affecting data ingestion. As a result, some customers may experience delays or missing data for activity from March 12th onward. Our team is actively working to resolve this issue. Ingested data will backfill automatically once the issue is resolved - no action is required on your part. We will provide updates as we have more information.

  2. identified Mar 13, 2026, 02:44 PM UTC

    We have identified and resolved the root cause of the data ingestion delays. Our systems are now processing the backlog of data. We will provide another update once we have an estimated time for all data to be fully caught up.

  3. identified Mar 13, 2026, 07:03 PM UTC

    Our systems are continuing to work through the backlog. Data will update throughout the day as the backlog clears. We expect most of the backlog to clear today and all data sources to be caught up within the next 24 hours.

  4. resolved Mar 14, 2026, 04:10 PM UTC

    All of the delayed ingestion jobs have been processed and the system is now fully functional.

Read the full incident report →