49 incidente Cloudbees înregistrate începând din octombrie 2019, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
Am observat o problemă în a unifica unde fluxurile de lucru nu reuşesc să declanşeze. Investigăm problema.
Continuăm să investigăm această problemă.
A fost implementată o soluţie şi monitorizăm rezultatele.
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
Investigăm o anomalie în istoria auditului. Funcția poate fi indisponibilă în acest timp.
Continuăm să investigăm această problemă.
Traducere automată din actualizarea oficială a incidentului.
a se vedea nota de subsol 1
Continuăm să investigăm această problemă.
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
We are currently investigating the issue of Unify AI assistant unavailable to the customers.
The incident has been fixed and the Unify AI assistant available to the customers.
Some components might experience slowness due to issue with upstream Cloud Provider. We are working on mitigations
This incident has been resolved.
Customer(s) could not login to the https://app.rollout.io/cloudbees/login due to an FM outage
We're experiencing an elevated level of API errors related to the timescale database outage. https://status.timescale.com/
We are currently investigating an issue in delivering services on the CloudBees platform
Incident has been migrated to cloudbeesstatus.io status site - https://www.cloudbeesstatus.io/
We are receiving errors affecting logins. We are currently investigating with our provider.
We have identified the root cause of the issue and working towards a fix. Logins are currently working.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
We have verified our fix is working.
We are aware that there are issues logging in to the CloudBees Feature Management web interface. We are investigating.
Logins to the web interface are working again. We are continuing to investigate.
A configuration setting caused specific traffic to be rejected by our firewall, causing issues with authentication. The problem has been corrected and the incident is now resolved.
We are seeing extreme latency and timeouts on our authentication service that is causing login failures. We are currently investigating this with our provider.
Our provider has implemented a fix and we are monitoring.
This incident has been resolved.
Earlier today, for a few hours, we experienced an infrastructure problem which effected flag updates This problem is now fixed, and all flags should be updated with the latest configurations
We are aware of a problem logging into CloudBees Feature Management and are investigating the cause. Flag use by SDK and delivery of your targeting is unaffected.
The CloudBees Feature Management API is operating normally. Whilst the web interface is unavailable, you can continue to make updates to Flags using the API: https://docs.cloudbees.com/docs/cloudbees-feature-management-rest-api/latest/introduction
On further investigation, some API requests are failing. We are continuing to investigate the cause and identify a solution!
We have identified some connectivity (DNS) errors in our infrastructure and are working on a fix for this.
We have found the cause of the connectivity problems and applied a fix. The web interface and API are fully functional again and we will continue to monitor.
This incident has been resolved.
We have noticed sporadic failures in user login to our website app.cloudbees.com and Zendesk. Other apps such as app.rollout.io do not seem affected, but we're determining the extent of this issue.
We are continuing to investigate this issue.
We have identified the source of the issue and resolved it. User login is back to stable behavior, and currently monitoring before closing the incident.
All systems healthy again, and this incident is now resolved.
CloudBees Feature Management functionality is degraded due to an AWS outage. Affected are: - Delivery of flags configuration updates - GitHub Configuration-as-Code - Subscription management We, and Amazon are investigating.
We are continuing to investigate this issue.
This incident has been resolved.
We've found out that re-sending the email via the button in email-verify page is continuously throwing an error, impacting new users signing up who click it. We've identified the root cause and rolling out a fix.
Fix for the root cause has been rolled out to production. Email verification is working for all users again.
Cloudflare is investigating wide-spread issues with their services and/or network. Users may experience errors or timeouts reaching Cloudflare’s network or services.
The issue has been identified and a fix is being implemented.
A fix has been implemented and CloudFlare is monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are in the process of running a short production infrastructure test that may result in flag impression metrics/analytics not updating for a short time period. We do not expect this to last for more than 15 to 30 minutes. During this time all other services will function as normal. We apologize in advance for any inconvenience caused.
We are continuing to investigate this issue.
This incident has been resolved.
New feature flag configuration changes are not being propagated to SDK clients.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
