Skip to content
Discussion options

You must be logged in to vote

Dear users,

We want to provide an update on the incident that temporarily impacted our services and share some insights into the situation.

Approximately at 23:00 UTC (November 16), our team received an alert signaling potential issues with our service. Unfortunately, due to incomplete actions, the alert was not handled as effectively as it should have been. Regrettably, this led to the escalation of the situation, resulting in a temporary service disruption.

As a result, users with repositories connected via SSH keys were not able to start builds. Repositories using other authentication methods, such as GitHub App or OAuth, were not affected.

The issue was fully resolved around 04:00 UTC…

Replies: 12 comments 13 replies

Comment options

You must be logged in to vote
1 reply
@CaleyD
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@cliffom
Comment options

@cbaradero
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@cliffom
Comment options

@ogoldberg
Comment options

Comment options

You must be logged in to vote
1 reply
@btbishop93
Comment options

Comment options

You must be logged in to vote
5 replies
@dmytro-stepanov-hd
Comment options

@himesh-cm
Comment options

@dmytro-stepanov-hd
Comment options

@himesh-cm
Comment options

@cliffom
Comment options

Comment options

You must be logged in to vote
2 replies
@martynbowis
Comment options

@cliffom
Comment options

Answer selected by helinanever
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
Infrastructure Issue This label indicates that Codemagic has run into issues with the underlying infrastructure.