Long waiting times on M4 Pro Machines
This incident has been resolved.
Home
/
Status
/
Service
Mobile DevOps platform for streamlined app development and deployment.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 5m ago
31
Components
0
Active incidents
1
Maintenance
10%
90d uptime
Long waiting times on M4 Pro Machines
Jun 17, 3:34 PM
Normalized official status-page data for incidents, maintenance, components, and history.
10%
Known uptime
10 known history days
31
Components tracked
0 outage, 0 degraded
51
Incidents indexed
0 active right now
41
Maintenance windows
1 active or scheduled
Components with the most recent status-page events.
⚙️ Builds (CI)
Operational
GitHub Webhooks
Operational
🤝 3rd Party Integrations
Operational
AWS s3-us-standard
Operational
AWS s3-us-west-1
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
1
degraded days
8
outage days
0
maintenance days
80
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident is now resolved, and impacted services are now operating. Our teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future. Thank you for your patience and understanding. If you encounter any issues, please reach out to our Support team: https://support.bitrise.io/en/
On April 28, 2026, rate limiting by Maven Central began causing 429 errors for Bitrise-hosted CI jobs attempting to download dependencies. We responded by enabling a proxy layer to mirror Maven packages within Bitrise in order to reduce load on Maven Central. The proxy service is working as intended, and the vast majority of dependency downloads over the previous 1.5 days have been served by Bitrise. There was, however, a subset of Bitrise CI jobs that were in the long tail and still experiencing 429 errors, even when following our recommended steps for using the mirror. Over the past several hours, we have evenly distributed traffic flow and have addressed the edge cases in customer Gradle configurations that bypassed the mirror. If you are still experiencing 429 rate-limiting errors when installing dependencies, and you have already followed the recommended steps for using the mirror, please reach out to us at support@bitrise.io.
This incident is now resolved and impacted services are now operating without issues. Our teams identified the root cause, released a fix and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future. Thank you for your patience and understanding. If you encounter any issues, please reach out to our Support team: https://support.bitrise.io/en/
This incident has been resolved.
This incident has been resolved.
This incident is now resolved, and impacted services are now operating without issues. Our teams identified the root cause, released a fix, and were monitoring our systems continuously to ensure the mitigation is safe. We'll conduct an internal post-mortem to understand what happened and learn how to avoid a similar outage in the future. Thank you for your patience and understanding. If you encounter any issues, please reach out to our Support team: https://support.bitrise.io/en/
Scheduled and completed maintenance windows are separated from incidents.
From 23:45 UTC Friday, 10 July, until 04:00 UTC Monday, 13 July, Bitrise will perform general maintenance on our infrastructure. This will reduce the M4 Pro, M2 Pro and Linux capacity, with a small chance of causing wait times during the weekend. We apologize for any inconvenience.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Bitrise status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.bitrise.io
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 25 of 31 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
🥫 Cache Any outages related to remote build caching, Bazel, Gradle, and Xcode build tools on Bitrise. | Operational | Group | Not recorded |
🛟 Bitrise Support | Operational | Group | Not recorded |
🤝 3rd Party Integrations Integrations that are not managed by Bitrise, but any outages might impact Bitrise features and services. | Operational | Group | 6/15/2026 |
Bitrise Community https://discuss.bitrise.io/ | Operational | Component | Not recorded |
Key Value Dependency Cache Service | Operational | Component | Not recorded |
Bitrise Support Center https://support.bitrise.io/ | Operational | Component | Not recorded |
Build Cache | Operational | Component | Not recorded |
⚙️ Builds (CI) Any outages related to running builds on Bitrise. Some examples: build queues, builds fail to start, issues with scheduled builds, Steps, the Workflow Editor, and failures on app.bitrise.io. | Operational | Component | 6/17/2026 |
Bazel Remote Execution | Operational | Component | Not recorded |
DigitalOcean | Operational | Component | Not recorded |
📊 Insights | Operational | Component | Not recorded |
📦 Release Management Any outages related to app distribution, device testing, install pages, and other features and services for Release Management. | Operational | Component | Not recorded |
👥 Account Management Any outages related sign-in, sign-up, permissions, payments, billing and other features or services for managing teams and users. | Operational | Component | Not recorded |
DNSimple Name Servers | Operational | Component | Not recorded |
Atlassian Bitbucket API | Operational | Component | Not recorded |
Atlassian Bitbucket Git via HTTPS | Operational | Component | Not recorded |
Atlassian Bitbucket SSH | Operational | Component | Not recorded |
Atlassian Bitbucket Webhooks | Operational | Component | Not recorded |
Atlassian Bitbucket Website | Operational | Component | Not recorded |
AWS s3-us-standard | Operational | Component | Not recorded |
AWS s3-us-west-1 | Operational | Component | Not recorded |
AWS s3-us-west-2 | Operational | Component | Not recorded |
Bintray REST API | Operational | Component | Not recorded |
Cocoapods | Operational | Component | Not recorded |
GitHub API Requests | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Bitrise is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.