Is Bitrise down?
Last checked 6m agoNo incidents right now.
Bitrise is operational right now. Last checked 6m ago; the most recent incident resolved 13d ago.
Real-time Bitrise status, recent outages, and incident history — pulled directly from Bitrise's official status page at https://status.bitrise.io every 5 minutes. Pingoru tracks 28 Bitrise services and has captured 19 incidents in the last 90 days (99.26% uptime). Get email, Slack, Discord, or webhook alerts the moment Bitrise reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- GitHub API Requests
Timeline · 4 updates
- investigating · Jul 16, 2026, 11:04 PM UTC
We are currently investigating reports of an elevated error rate on the Bitrise website. We will provide a further update as soon as more information is available.
- identified · Jul 16, 2026, 11:24 PM UTC
We're experiencing elevated error rates across the Bitrise website. This is caused by an ongoing GitHub incident that is disrupting a critical part of our platform: https://www.githubstatus.com/incidents/gxycch3076xk We're actively working to restore service stability.
- monitoring · Jul 17, 2026, 12:04 AM UTC
Error rates are decreasing. We're continuing to monitor closely to confirm full recovery before resolving this incident.
- resolved · Jul 17, 2026, 12:13 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Jul 16, 2026, 02:51 PM UTC
We experienced a brief period of high error rates on our website. The issue was caused by a database migration timing issue and was resolved after a rollback.
Latest: We experienced a brief period of high error rates on our website. The issue was caused by a database migration timing issue and was resolved after a rollback.
-
- ⚙️ Builds (CI)
Timeline · 3 updates
- investigating · Jul 14, 2026, 04:40 PM UTC
We are currently investigating a network outage affecting our ORD data center. Builds running in this data center may have failed or been delayed during the outage. Our team identified an issue with Proxmox storage in the affected data center and is working on a fix. We will provide a further update as soon as more information is available.
- monitoring · Jul 14, 2026, 06:18 PM UTC
The network outage affecting our ORD data center has been mitigated. Builds running in this data center may have failed or been delayed during the outage window. Our team identified and addressed an issue with Proxmox storage in the affected data center, and job scheduling has resumed. We are continuing to monitor stability as we investigate the underlying root cause. We will provide a further update as soon as more information is available.
- resolved · Jul 15, 2026, 06:13 PM UTC
This incident has been resolved. We experienced a network outage in our ORD data center caused by dropped packets between nodes, which led to failed health checks and a cluster-wide disruption. The outage was mitigated on July 14, and we've since applied network configuration changes across all our data centers to address the underlying cause and prevent recurrence. We apologize for the disruption it caused.
Latest: This incident has been resolved. We experienced a network outage in our ORD data center caused by dropped packets between nodes, which led to failed health checks and a cluster-wid…
-
- ⚙️ Builds (CI)GitHub Git Operations
Timeline · 4 updates
- investigating · Jul 14, 2026, 03:35 PM UTC
We are currently investigating reports of slow or hanging builds. Affected builds may stall or take significantly longer than usual during early phases such as cloning repositories or resolving Swift Package Manager dependencies. We will provide a further update as soon as more information is available.
- investigating · Jul 14, 2026, 03:36 PM UTC
We are continuing to investigate this issue.
- investigating · Jul 14, 2026, 04:30 PM UTC
We are continuing to investigate this issue.
- resolved · Jul 15, 2026, 06:10 PM UTC
This incident has been resolved. Some builds may still experience slower clone operations from GitHub due to performance degradation affecting Git operations in some of our datacenters. As a workaround, use Bitrise key-based caching for SPM dependencies so builds do not re-resolve them over the slow path. Add Restore SPM Cache (restore-spm-cache@3) before your dependency-resolution/build step and Save SPM Cache (save-spm-cache@1) after your dependency resolution and build steps — no extra configuration needed. Please note that Bitrise does not cache your source code; your repository must still be cloned to fetch the latest changes. If a build fails or hangs during code fetch, retry the build to attempt the clone operation again.
Latest: This incident has been resolved. Some builds may still experience slower clone operations from GitHub due to performance degradation affecting Git operations in some of our datacen…
-
- Build Cache
Timeline · 2 updates
- investigating · Jul 13, 2026, 09:08 AM UTC
We are investigating degraded performance affecting Build Cache in our IAD datacenter. Builds relying on cache may experience slower performance or cache misses.
- resolved · Jul 13, 2026, 10:49 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Bitrise outage history
12 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Bitrise outage history →Or sign up free to get alerts when Bitrise breaks · 10 free monitors · No credit card
- Started Jul 16, 2026, 11:04 PM UTC · Resolved Jul 17, 2026, 12:13 AM UTC · 1h 9m
- Started Jul 16, 2026, 02:51 PM UTC · Resolved Jul 16, 2026, 02:51 PM UTC · —
- ORD data center network outage ResolvedStarted Jul 14, 2026, 04:40 PM UTC · Resolved Jul 15, 2026, 06:13 PM UTC · 1d 1h
- Started Jul 14, 2026, 03:35 PM UTC · Resolved Jul 15, 2026, 06:10 PM UTC · 1d 2h
- Started Jul 13, 2026, 09:08 AM UTC · Resolved Jul 13, 2026, 10:49 AM UTC · 1h 41m
- Started Jul 10, 2026, 05:49 PM UTC · Resolved Jul 10, 2026, 07:50 PM UTC · 2h 1m
- Started Jul 09, 2026, 09:05 AM UTC · Resolved Jul 09, 2026, 12:12 PM UTC · 3h 6m
- Intermittent DNS failures ResolvedStarted Jul 08, 2026, 08:19 PM UTC · Resolved Jul 08, 2026, 09:30 PM UTC · 1h 10m