Feb 17, 14:35 UTC
Resolved - We have deployed a fix and confirmed it is working.
Feb 17, 13:58 UTC
Identified - We have confirmed an issue with CodeShip Pro builds displaying the wrong UI and making logs inaccessible.
We are in the process of restoring normal service for CodeShip Pro users.
Feb 17, 13:26 UTC
Investigating - We are hearing reports that some Pro builds are performing abnormally.
Please contact us ([email protected]) with more information if you are seeing any odd behavior, and we will continue investigating.
Feb 18, 05:35 UTC
Completed - The scheduled maintenance has been completed.
Feb 18, 04:36 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 18, 04:32 UTC
Scheduled - We are performing maintenance on the Bitbucket integration to improve reliability and performance.
Feb 19, 03:31 UTC
Completed - The scheduled maintenance has been completed.
Feb 19, 03:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 19, 03:26 UTC
Scheduled - As part of ongoing security work, we have activated the Sqreen (sqreen.io) Web Application Firewall on the main CodeShip application.
We have reviewed the logs over the last few weeks and do not expect any false positives.
If you are blocked, then please raise a support request (different system - different protection logic) and we'll get you unblocked ASAP.
Feb 28, 21:32 UTC
Completed - The scheduled maintenance has been completed.
Feb 28, 21:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 28, 21:07 UTC
Scheduled - We will be performing scheduled maintenance on the app.codeship.com site over the next hour.
Builds in-flight will continue to run (but will not report back immediately), new builds will not be scheduled.
Service interruption is expected to be limited to around 15 minutes.
Mar 1, 13:14 UTC
Resolved - This incident has been resolved.
Mar 1, 12:35 UTC
Monitoring - A fix has been implemented and we are monitoring the system.
If you noticed the build status page said "Trigger your first build" - then this was (incorrectly shown) because the build scheduling APIs were timing out.
Mar 1, 10:08 UTC
Identified - We are investigating a build scheduling performance issue.
There will be a short interruption to build process while we complete a system upgrade to alleviate stress on the system.
Mar 25, 14:59 UTC
Resolved - Service should now be properly restored.
Mar 25, 14:49 UTC
Identified - We are working to resolve issues preventing the CodeShip application from resolving. Service should be restored shortly.
Mar 25, 15:50 UTC
Resolved - This incident has been resolved.
Mar 25, 15:38 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 25, 15:31 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 25, 15:28 UTC
Investigating - We are currently investigating this issue.
May 17, 17:17 UTC
Resolved - This incident has been resolved.
May 17, 15:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 17, 12:59 UTC
Investigating - Some builds are failing to clone the repository. The issue is currently being investigated
Jun 8, 16:21 UTC
Resolved - This incident has been resolved.
Jun 8, 14:40 UTC
Monitoring - A fix has been implemented and the CodeShip site is up again.
Jun 8, 14:33 UTC
Investigating - The CodeShip site is currently not reachable
Sep 27, 18:00 UTC
Resolved - This incident has been resolved.
Sep 27, 16:20 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 27, 14:40 UTC
Investigating - Upstream providers indicated issues are resolved, but we are continuing to see some instability in our systems. We are working to further diagnose the problem.
Sep 27, 05:48 UTC
Identified - Our service provider continues remediation efforts on the affected data services.
(Heroku Incident - https://status.heroku.com/incidents/2361)
(AWS is also flagging an issue with EBS volumes in US-EAST-1 - Heroku has not confirmed if that is the root cause as yet - although they have confirmed that it is an upstream provider issue for them too)
Sep 27, 02:49 UTC
Investigating - We are investigating an issue with the platform.
Initial investigations indicate a problem with the data services offered by our platform provider.
Heroku are aware of the incident - https://status.heroku.com/incidents/2361