All Systems Operational
codefresh.io ? Operational
90 days ago
99.83 % uptime
Today
Codefresh Docker build service Operational
Codefresh Docker run service Operational
GitHub Operational
Atlassian Bitbucket Git via HTTPS Operational
Atlassian Bitbucket Webhooks Operational
Atlassian Bitbucket API Operational
Google Cloud Platform Google Cloud Storage Operational
Google Cloud Platform Google Cloud DNS Operational
Google Cloud Platform Google Container Engine Operational
Stripe API Operational
Slack Operational
SLA ? Operational
Intercom Intercom Web Application Operational
Docker System Status ? Operational
AWS route53-us-east-1 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Aug 10, 2020

No incidents reported today.

Aug 9, 2020

No incidents reported.

Aug 8, 2020

No incidents reported.

Aug 7, 2020

No incidents reported.

Aug 6, 2020

No incidents reported.

Aug 5, 2020

No incidents reported.

Aug 4, 2020

No incidents reported.

Aug 3, 2020

No incidents reported.

Aug 2, 2020

No incidents reported.

Aug 1, 2020

No incidents reported.

Jul 31, 2020

No incidents reported.

Jul 30, 2020

No incidents reported.

Jul 29, 2020
Resolved - The root cause of this issue has been identified.
It's related to a networking issue impacting GCP.
More information here:
https://status.cloud.google.com/incident/cloud-networking/20008

Their incident is already resolved, and our service is back to normal.
Jul 29, 22:30 UTC
Update - The issue has been resolved, but we continue to investigate the cause.
Jul 29, 20:50 UTC
Investigating - We're experiencing an issue with loading our website, and are currently looking into the issue.
Jul 29, 20:33 UTC
Jul 28, 2020
Resolved - The following information is published by AWS:
4:37 AM PDT Between 1:22 AM and 4:13 AM PDT, customers experienced an increase in DNS resolution errors from EC2 instances in a single Availability Zone of the US-EAST-1 Region. This could have also impacted functionality of other services that use EC2, such as RDS, SageMaker, EMR, WorkMail, MSK, AWS IoT Analytics Service, Amazon ElasticSearch, Cloud9, AppMesh, Amazon Managed Blockchain, Glue, and AWS Transfer. The issue has been resolved and all DNS queries are being answered normally.
Jul 28, 11:40 UTC
Update - An update from AWS:
4:19 AM PDT DNS resolution failures in a single Availability Zone in the US-EAST-1 Region have largely been mitigated, and we are continuing to work towards full mitigation.
Jul 28, 11:32 UTC
Identified - An update from AWS:
3:44 AM PDT We are implementing a mitigation to the increased DNS resolution errors from EC2 instances in a single Availability Zone in the US-EAST-1 Region, and are starting to see recovery. This issue could also impact functionality of other services that use EC2, such as App Mesh, Cloud9, ElasticSearch, EMR, Managed Blockchain, SageMaker, Transfer for SFTP, WorkMail, RDS, and Glue.
Jul 28, 10:54 UTC
Update - An update from AWS:
2:57 AM PDT We are continuing to investigate increased DNS resolution errors from EC2 instances in a single Availability Zone of the US-EAST-1 Region. This could also impact functionality of other services that use EC2, such as App Mesh, Cloud9, ElasticSearch, EMR, Managed Blockchain, SageMaker, Transfer for SFTP, WorkMail, and Glue.
Jul 28, 10:07 UTC
Investigating - The following information is published by AWS:
We are investigating an increase in DNS lookup failures from EC2 instances in a single Availability Zone in the US-EAST-1 Region.
More information here:
https://status.aws.amazon.com/
Jul 28, 10:04 UTC
Jul 27, 2020

No incidents reported.