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
Mar 22, 2019

No incidents reported today.

Mar 21, 2019

No incidents reported.

Mar 20, 2019

No incidents reported.

Mar 19, 2019
Resolved - This incident has been resolved. Please reach out to support with any additional questions.
Mar 19, 19:58 UTC
Monitoring - On 18th March 2019 our engineering team performed maintenance on one of our databases and accidentally soft deleted a small subset of customer accounts. This caused some customer and project information to appear missing or outdated. This was brought to our attention by some customers and we were able to restore the data to its original state. We sincerely apologize for any impact this has had on your day. Please reach out to support if you do not feel the situation has been rectified. Though we have fixed the root cause we are actively monitoring to ensure nothing else was affected. We will be reviewing our processes around data cleanup in order to avoid this from happening again. As well as reviewing our ability to identify issues like this sooner.
Mar 19, 16:28 UTC
Mar 18, 2019

No incidents reported.

Mar 17, 2019

No incidents reported.

Mar 16, 2019

No incidents reported.

Mar 15, 2019

No incidents reported.

Mar 14, 2019

No incidents reported.

Mar 13, 2019

No incidents reported.

Mar 12, 2019

No incidents reported.

Mar 11, 2019

No incidents reported.

Mar 10, 2019

No incidents reported.

Mar 9, 2019

No incidents reported.

Mar 8, 2019

No incidents reported.