Rapidly release code with confidence on CircleCI's modern continuous integration and delivery platform.
Homepage: https://circleci.com/
Status Page: https://status.circleci.com/
Action | Date | Description |
---|---|---|
Postmortem | 2017-01-31 19:08:00 | At 4:30 PM PST our customers started to notice extreme slowness with all parts of our site and around 4:50 PM PST we declared an incident.During investigations into the root cause we determined that GitHub was suffering from extreme latency for some of their API's. This latency was having an impact on CircleCI at all levels which translated into site slowness and/or build failures.GitHub resolved their issue around 5:50 PM PST which then also returned out site back to normal. |
Resolved | 2017-01-31 01:54:00 | We're no longer experiencing issues with Github's API. Please reach out to support@circleci.com if you have any issues. |
Update | 2017-01-31 01:42:00 | We're still seeing slow response times from Github's API, however there are signs of improvement. We'll continue to monitor and update again in 20 minutes. |
Monitoring | 2017-01-31 01:13:00 | We're continuing to monitor slow response times from Github's API, we'll update again in 20 minutes. |
Investigating | 2017-01-31 00:53:00 | We are noticing slow response times from GitHub webhooks. We are monitoring and will update again in 20 minutes. |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-27 19:12:00 | This incident has been resolved. |
Monitoring | 2017-01-27 18:01:00 | The website response is back to normal, we will continue to monitor to verify. Thank you |
Investigating | 2017-01-27 17:42:00 | We are looking into reports of the site being slow to load |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-26 16:51:00 | We are no longer seeing any issues related to GitHub. Please contact support if you have any further issues. |
Update | 2017-01-26 16:44:00 | GitHub hooks and events are coming in again. We will be monitoring the situation. |
Monitoring | 2017-01-26 16:25:00 | We're seeing a drop in incoming notifications from GitHub. We're monitoring the situation and making sure we have capacity for when it is resolved. |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-20 01:38:00 | This incident has been resolved. |
Monitoring | 2017-01-20 01:13:00 | We've resolved the issue with broken builds from API and non-CircleCI accounts, and we'll continue to monitor closely. If you have any builds marked as Not Running, hitting the rebuild button will fix the issue. If you see anything amiss, please reach out to support@circleci.com. |
Investigating | 2017-01-20 00:41:00 | Builds triggered via API, or pushed by users that don't have a CircleCI account are currently broken. We have determined the cause, and are pushing a fix. |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-13 17:27:00 | We are no longer seeing any issues related to GitHub. Please do contact support if you have any further issues. |
Monitoring | 2017-01-13 16:43:00 | GitHub hooks and events are flowing. We will be monitoring the situation. |
Identified | 2017-01-13 16:27:00 | GitHub is reporting major outage. We will be unable to process many requests and our ability to check permissions is severly limited. |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-12 01:56:00 | The follow projects issue is resolved. We're continuing to monitor closely. If you're seeing anything that looks awry, please reach out to support@circleci.com and our support engineers will dig in. |
Monitoring | 2017-01-12 01:40:00 | We've rolled out the fix to the follow projects issue and are closely monitoring. Thanks for your patience, and if you see anything that looks amiss, please reach out to our support engineers at support@circleci.com. |
Identified | 2017-01-12 01:09:00 | Weve identified the root issue as an update to the library used to communicate with GitHub. Weve identified a fix and are in the process of rolling it out. Thanks for your patience. |
Investigating | 2017-01-12 00:57:00 | We're seeing an issue with users and their ability to follow projects. This will primarily affect starting projects that have never built on CircleCI before. We have are currently working on a fix and will update shortly. |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-11 23:08:00 | TLS Certificate reverted and we have had no reports for 20 minutes, marking as resolved. |
Identified | 2017-01-11 22:45:00 | TLS Certificate update failed and has been reverted, we are monitoring to ensure the rollback worked. |
Action | Date | Description |
---|---|---|
Resolved | 2017-01-10 22:07:00 | We're no longer seeing any queued builds or issues with the AWS API. Please don't hesitate to reach out to support@circleci.com if you experience any issues. |
Monitoring | 2017-01-10 21:22:00 | We are witnessing infrequent build queueing due to errors from the AWS API. Only seeing short, intermittent delays for now, but we are monitoring closely. |
Action | Date | Description |
---|---|---|
Resolved | 2016-12-25 17:47:00 | Everything continues to operate normally. |
Monitoring | 2016-12-25 17:10:00 | Fix is deployed and artifacts are downloading again. Monitoring closely. |
Update | 2016-12-25 16:51:00 | We are currently deploying an expected fix. Will update again within 30 mins. |
Identified | 2016-12-25 16:26:00 | Download of artifacts is currently not working. The issue has been identified and we are currently working on a fix. Will update in 30 mins. |
Action | Date | Description |
---|---|---|
Resolved | 2016-12-22 21:30:00 | This incident has been resolved. |
Monitoring | 2016-12-22 16:57:00 | Slack notifications for build messages may be delayed |