CodeShip
All Systems Operational

About This Site

Status of CodeShip and integrated services

CodeShip Operational
Website ? Operational
Application & API Servers ? Operational
Build Dispatcher ? Operational
Documentation ? Operational
Support ? Operational
CodeShip Basic Operational
Builds Operational
CodeShip Pro ? Operational
Builds Operational
Caching Operational
Docker Registry Operational
Quay.io Registry Operational
Google Container Registry Operational
SCM Providers Operational
Atlassian Bitbucket API Operational
Atlassian Bitbucket Webhooks Operational
GitLab Operational
GitHub API Requests Operational
GitHub Git Operations Operational
Notifications Operational
Flowdock Operational
Slack ? Operational
3rd Party Package Managers Operational
npm, Inc. Registry Reads Operational
Packagist ? Operational
Python Infrastructure pypi.python.org Operational
RubyGems.org Dependency API Operational
RubyGems.org Gem Downloads Operational
RubyGems.org Gem Index API (new) Operational
Infrastructure Operational
AWS EC2 Operational
Braintree API ? Operational
DNSimple Operational
Heroku Operational
Pusher Pusher REST API ? Operational
Pusher WebSocket client API ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Uptime
Fetching
Past Incidents
Feb 24, 2019

No incidents reported today.

Feb 23, 2019

No incidents reported.

Feb 22, 2019

No incidents reported.

Feb 21, 2019
Resolved - Last night, we were made aware that environment variables configured on CodeShip Basic builds with pre-configured deployment pipeline options (such as Heroku, AWS and Google App Engine) were being printed in your build logs. This was an unintended side effect of recent infrastructure work.

Immediately after being notified, our on-call team determined that the issue began several weeks ago as part of a new backend system rollout for handling build logs. Within minutes, we turned off this new log function as a short term fix and deployed a permanent solution later in the evening.

There are several important things to note about what was, and wasn’t exposed so that you can make the appropriate decision on what keys you may need to rotate.

- This problem impacted CodeShip Basic builds using one of our pre-configured deployment pipelines. CodeShip Pro and Basic custom script deployments were not impacted.

- No external user had access to data at any point, as our logs are not available via API and are not downloadable. Only team members you have added to your projects on CodeShip had access to the build logs which included the secrets - but these logs were accessible by all team members.

- We have scrubbed all the relevant build logs, including those from all our backup systems, for the entire impacted period of time.

The root cause of the issue was that our new logging system was not accounting for the deployment context of these specific types of CodeShip Basic steps, which is an oversight of both automated and manual testing on our end.

We are working to add more precise testing around all relevant scenarios, and as our longer-term plans for improving secret handling become clear, we will share them with you for feedback. We’re sorry for the issue - we take security very seriously and our team has been working as hard as possible to resolve the issue and put steps in place to prevent any possible recurrence in the future.
Feb 21, 19:06 UTC
Feb 20, 2019

No incidents reported.

Feb 19, 2019
Resolved - This incident has been resolved.
Feb 19, 15:40 UTC
Identified - Github is having difficulties processing webhooks, resulting in delayed CodeShip builds. We are monitoring https://www.githubstatus.com/ for more information.
Feb 19, 15:29 UTC
Feb 18, 2019

No incidents reported.

Feb 17, 2019

No incidents reported.

Feb 16, 2019

No incidents reported.

Feb 15, 2019

No incidents reported.

Feb 14, 2019

No incidents reported.

Feb 13, 2019

No incidents reported.

Feb 12, 2019

No incidents reported.

Feb 11, 2019

No incidents reported.

Feb 10, 2019

No incidents reported.