Don't miss another incident from CodeShip.
Ctatus will help you monitor CodeShip and all your 3rd party services.
Give Ctatus a Try
No credit card required
CodeShip

CodeShip Status
Official status page

All Systems Operational
03/11
04/11
05/11
06/11
07/11
08/11
09/11
10/11
11/11
12/11
13/11
14/11
15/11
16/11
17/11
18/11
19/11
20/11
21/11
22/11
23/11
24/11
25/11
26/11
27/11
28/11
29/11
30/11
01/12
02/12
03/12

Latest Incidents

Resolved CodeShip Basic builds not completing

We are investigating an issue with CodeShip Basic builds not completing execution properly.

Resolved CodeShip builds not running

We are currently investigating this issue.

Resolved System upgrades - Application Servers

We are performing upgrades to our application servers (component updates). We do not expect any disruption of service, but builds may be temporarily delayed as we update the platform.

about 1 month ago Official incident report

Resolved [Security] Critical Security Notification - CodeShip Users

On Wednesday, September 16, 2020, CloudBees was notified by GitHub of suspicious activities targeting certain CodeShip accounts connected to GitHub via the CodeShip GitHub app and now deprecated CodeShip OAuth tokens. If your GitHub credentials are impacted, you already received or will shortly receive a notification from GitHub informing you of this incident. The activities point to tokens being used to access the “/user/repos” GitHub API endpoint (https://docs.github.com/en/[email protected]/rest/reference/repos#list-repositories-for-the-authenticated-user), which is used to list users’ GitHub repositories, including private repositories. It is possible your repositories were cloned, so please contact GitHub support as soon as possible. Because the suspicious activities involve user tokens, as a first step in response we revoked all GitHub related tokens and SSH keys to keep all accounts protected. You need to reauthenticate CodeShip with GitHub immediately to avoid a service impact. *Action Required* - If you use GitHub to sign in to CodeShip, sign out of all CodeShip sessions and sign back in. - If you have GitHub projects setup on CodeShip, first remove and reinstall the CodeShip GitHub app: https://documentation.codeship.com/general/projects/builds-are-not-triggered/#github - Next, generate a new SSH key for each CodeShip project. This will enable CodeShip to clone the repository for builds again: https://documentation.codeship.com/general/projects/project-ssh-key/ We are continuing to investigate the underlying issue and will update our blog to provide more information as soon as we better understand any additional implications and potential root causes. Thank you. The CloudBees Team

Resolved app.codeship.com down

We are currently investigating an outage on app.codeship.com

Resolved Website not available

We are currently investigating this issue.

Resolved Pro builds delayed due to AWS EC2 issues

AWS is reporting EC2 issues which is causing Pro builds to be delayed.

Resolved Hanging builds on Basic

Some builds are hanging on Basic. You may need to stop and restart builds that are not displaying logs. A fix is being implemented.

Resolved codeship.com marketing site down

The https://codeship.com marketing site is down and we are investigating. https://app.codeship.com is separate and running normally.

Resolved GitHub webhook delays

We are seeing GitHub webhook delays which causes delays with builds starting. Monitoring https://www.githubstatus.com/incidents/phnch1rww464 for additional updates.

Stats

1 incidents in the last 7 days

2 incidents in the last 30 days

Follow CodeShip and other services to get alerts about incidents in realtime.

Get started now
14 days of trial / No credit card required

Don't miss another incident in CodeShip!

Ctatus aggregates status page from services so you don't have to. Follow CodeShip and hundreds of services and be the first to know when something is wrong.

Get started now
14 days of trial / No credit card required