Vendor Status Watch

← all vendors

Bitrise status history

Current state: operational — “All Systems Operational” per https://status.bitrise.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
17incidents, last 90 days
50incidents on record
Incidents per week, last 12 weeks:

How long do Bitrise incidents last?

118 minmedian incident duration50 measured
22.3 h90th percentile1 in 10 ran longer
2.7 hmedian, major/critical only11 incidents

From 50 incidents with a vendor-posted start and resolve time. Longest on record: Public VNC access is temporarily disabled on remote access builds and RDE sessions — 31.9 days (2026-07-30 15:40 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (50)

StartedIncidentStatusImpactDuration
2026-09-05 12:52 UTCKey Value Dependency Cache Serviceresolvedminor1 h 49 min
2026-08-28 13:01 UTCCI build list is not loading in multiple workspacesresolvedmajor32 min
2026-08-07 13:02 UTCIncreased queues on Linux machinesresolvedminor57 min
2026-07-30 15:40 UTCPublic VNC access is temporarily disabled on remote access builds and RDE sessionsresolvedminor31 d 21 h
2026-07-16 23:04 UTCElevated error rates on Bitrise Websiteresolvedminor1 h 09 min
2026-07-16 14:51 UTCWebsite high error rate due to database migration issueresolvedminor0 min
2026-07-14 16:40 UTCORD data center network outageresolvedmajor25 h 33 min
2026-07-14 15:35 UTCSlow or hanging builds during clone and dependency resolutionresolvedminor26 h 35 min
2026-07-13 09:08 UTCDegraded Build Cache in IAD datacenterresolvedminor1 h 41 min
2026-07-10 17:49 UTCElevated error rates for the Bitrise Workflow Editorresolvedmajor2 h 01 min
2026-07-09 09:05 UTCElevated errors with Bitrise Build Pipelineresolvedminor3 h 06 min
2026-07-08 20:19 UTCIntermittent DNS failuresresolvedmajor1 h 10 min
2026-07-08 13:54 UTCLinux machines on holdresolvedmajor18 h 02 min
2026-07-07 15:06 UTCExperiencing networking connectivity issues in our IAD datacenterresolvedminor3 min
2026-06-26 19:40 UTCPotential issues withGradle init script compileresolvednone12 h 44 min
2026-06-25 10:28 UTC503 error in Firebase Virtual Device Testing for Android stepresolvedminor19 h 46 min
2026-06-23 09:00 UTCBuild logs containing malformed sections instead of the usual structured dataresolvednone0 min
2026-06-17 15:34 UTCLong waiting times on M4 Pro Machinesresolvedminor55 min
2026-06-11 20:26 UTCBuilds Failingresolvedminor12 min
2026-06-11 16:50 UTCIssues with Data Center Connectivityresolvedminor1 h 56 min
2026-05-28 15:00 UTCArtifact upload failures in Store Releasesresolvedminor5 d 17 h
2026-04-30 11:34 UTCElevated error rate with Android buildsresolvedminor34 h 16 min
2026-04-29 10:36 UTCElevated error rates for Android buildsresolvedminor9 h 48 min
2026-04-28 13:38 UTCElevated error rates for Android buildsresolvedminor8 h 36 min
2026-04-28 12:29 UTCElevated error rates on build details pageresolvedminor4 h 58 min
2026-04-20 16:37 UTCExperiencing issues with billing cycle refreshing credits/builds for certain Bitrise plansresolvedminor3 h 08 min
2026-04-15 20:23 UTCElevated Queue Times on Linux Machinesresolvedminor31 min
2026-03-19 16:52 UTCElevated Queue Times on Linux Machinesresolvedminor5 h 50 min
2026-03-09 12:21 UTCBuild Issuesresolvedminor3 h 20 min
2026-03-05 11:43 UTCDeploy to Bitrise step failing due to network issuesresolvedminor30 min
2026-03-02 15:59 UTCIncrease build queues on all Stacksresolvedminor1 h 33 min
2026-03-02 13:27 UTCIncrease build queues on all Stacksresolvedminor2 h 29 min
2026-03-02 11:37 UTCIncreased error rates in build triggering.resolvedminor8 min
2026-02-11 14:59 UTCIssues with Pipelines API Endpointresolvedminor2 h 48 min
2025-12-05 09:00 UTCwww.bitrise.io downresolvednone0 min
2025-12-03 10:18 UTCIssues with passing values to environment variablesresolvedminor41 min
2025-11-26 16:09 UTCUsers might experience issues with Android builds hangingresolvedminor22 h 18 min
2025-11-25 16:55 UTCSlower response times on Bitrise web app and REST APIresolvedminor24 min
2025-11-18 17:20 UTCLong waiting times on M4 Pro machine (queue) buildsresolvedmajor3 h 18 min
2025-11-18 11:53 UTCBitrise web application (app.bitrise.io) unavailableresolvedmajor8 h 43 min
2025-11-10 11:10 UTCLong waiting times on Mac stacks due to degraded VM startupresolvedmajor3 min
2025-10-30 16:18 UTCQueues on M4 Proresolvedmajor1 h 37 min
2025-10-28 16:21 UTCQueues on m4 Proresolvedmajor2 h 42 min
2025-10-24 09:48 UTCGit operations over ssh seeing increased latency on github.comresolvedminor2 h 35 min
2025-10-20 16:27 UTCCustomers May Experience Issues Reaching Support via Intercom due to AWS outageresolvedminor7 h 09 min
2025-10-20 10:10 UTCAWS outageresolvedmajor4 h 13 min
2025-10-14 16:52 UTCUsers might experience issues with the Workflow Editorresolvedminor24 min
2025-10-02 12:31 UTCBuild Cache invocations webpage loading issuesresolvedminor11 min
2025-09-08 17:08 UTCUpdate on Issue with Flagged Accountsresolvedminor1 h 47 min
2025-09-06 14:41 UTCFlagged accountsresolvedminor36 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Bitrise with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "bitrise"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}