Resolved -
This incident has been resolved.
Jun 17, 16:29 UTC
Investigating -
We are currently investigating elevated build queues on Bitrise. Some users may experience longer-than-usual wait times for builds to start, as queued jobs take longer to be picked up.
Services: Build start times and queue wait times; build execution itself remains normal once a worker is allocated.
Scope: Builds on M4 Pro Stacks
Severity: SEV-2
What we’re doing? Our Engineering teams are actively investigating causes, reviewing worker pool utilization, autoscaling events, recent deploys, and any upstream provider issues. We are analyzing metrics and logs to identify bottlenecks like unusually high build volume, throttling from third-party providers, etc. We are working on immediate actions to remediate this issue. We will perform validated mitigations as soon as they are determined safe.
When will the next update be available? You can expect a status update approximately 1 hour from now.
Jun 17, 15:34 UTC
Resolved -
This incident has been resolved.
Jun 11, 20:39 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 11, 20:38 UTC
Investigating -
Gradle builds in the ORD data center are experiencing failures with dependency resolution. Some users may experience build failures
Services: Gradle Repository Manager
Scope: All builds in the ORD data center
Severity: SEV-2
What we’re doing? Our Engineering teams are actively investigating root cause. We are working on immediate actions to remediate this issue. We will perform validated mitigations as soon as they are determined safe.
When will the next update be available? You can expect a status update approximately 15 minutes from now.
Jun 11, 20:26 UTC
Resolved -
This incident has been resolved.
Jun 11, 18:46 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 11, 16:50 UTC
Investigating -
We are currently investigating an incident causing to be unavailable.
Services: Data Center Connectivity
Severity: SEV-1
What we’re doing? Our Engineering teams are actively investigating this issue. We’re checking recent deploys, logs, CDN, DNS health, and server availability. We are working on immediate actions to remediate this issue. We will perform validated mitigations as soon as they are determined safe.
When will the next update be available? You can expect a status update approximately 1 hour from now.
Jun 11, 16:50 UTC