{ "meta": { "version": "v1", "pricing": { "public": { "label": "Public", "description": "Read-only API access for lightweight status checks and public integrations." }, "premium": { "label": "Premium", "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack." } }, "generatedAt": "2026-11-14T06:02:12.331Z" }, "data": { "id": "incident_statuspage_bitrise_7055z4g9nbck", "slug": "bitrise-security-incident-2026-11-13", "title": "Security Incident", "summary": "Security Incident", "status": "investigating", "stale": false, "severity": "critical", "startedAt": "2026-11-13T20:44:26.194+00:00", "updatedAt": "2026-11-14T05:50:42.616+00:00", "resolvedAt": null, "provider": { "slug": "bitrise", "name": "Bitrise" }, "affectedServices": [ { "slug": "bitrise-account", "name": "Account, insights & releases" }, { "slug": "bitrise-builds", "name": "Builds" }, { "slug": "bitrise-cache", "name": "Cache & remote execution" } ], "links": { "html": "/incidents/bitrise-security-incident-2026-11-13", "api": "/api/v1/incidents/bitrise-security-incident-2026-11-13", "providerHtml": "/providers/bitrise", "alerts": "https://outagedeck.com/account?stack=bitrise&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident" }, "impactSummary": "Bitrise reported a critical event for the affected tracked services.", "source": { "id": "source_bitrise_status", "kind": "official_api", "name": "Bitrise Status", "checkedAt": "2026-11-14T06:00:14.025+00:00", "stale": false, "officialUrl": "https://status.bitrise.io", "statusPageUrl": "https://status.bitrise.io" }, "updates": [ { "id": "update_statuspage_bitrise_7055z4g9nbck_3mjl1wbbwtsn", "status": "investigating", "body": "We are responding to a security incident affecting some of Bitrise’s internal secrets, detected within the last hour. As a precaution we have temporarily taken Bitrise offline. We have no confirmation that any customer data or source code was accessed and are investigating urgently. Out of an abundance of caution, we recommend rotating any Git and source-code access credentials connected to Bitrise. We will share updates as soon as we know more.\n\nScope:\nAll Users\n\nSeverity:\nSEV 1\n\nWhen will the next update be available?\n\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-13T20:44:26.618+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_pzg6n4whbr2n", "status": "investigating", "body": "We are continuing to investigate the security incident causing Bitrise to be unavailable.\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-13T21:45:34.846+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_k408r0yznsz7", "status": "investigating", "body": "We are continuing to investigate the security incident causing Bitrise to be unavailable.\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-13T23:01:04.519+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_6z3yx3vmnp75", "status": "investigating", "body": "We are continuing to investigate the security incident causing Bitrise to be unavailable.\nIf you need to reach out to us please e-mail us at support@bitrise.io\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-14T00:03:25.863+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_y0qlvt439cbh", "status": "investigating", "body": "What happened?\nOn November 13, 2026 at 11:32 EST (16:32 UTC), we detected suspicious activity in one of our internal cloud environments. Our initial investigation confirmed unauthorized access to an internal system. This system does not store or process customer data.\nFollowing our incident response procedures, we immediately took all of our services offline as a precaution while we investigated.\nAt this stage, we have found no evidence that customer data, secrets, or source code were exposed. We are working all hands on the deck to determine the full scope and to restore our services as soon as possible.\n\n\nWhat we recommend\nAs a precaution, once our services are restored, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.\n\nWhat’s next\nOur teams are working on completing the investigation and to restore all services safely.\nWe understand the impact this has on your work and appreciate your patience.\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-14T01:26:42.205+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_yd6j6d75j80w", "status": "investigating", "body": "\nAfter ongoing investigations we have still found no evidence that customer data, secrets, or source code were exposed. We are now beginning to restore services in a controlled, phased manner. We do not yet have an estimated time for full restoration.\n\n\nWhat we recommend\nAs a precaution, once our services are restored, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-14T02:29:04.214+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_hzlcz2mq563l", "status": "investigating", "body": "\nWe are making progress restoring the service, we expect the logins to app.bitrise.io to be restored by 01:00 EST (06:00 UTC), we are still working on a timeline for full restoration.\n\nWhat we recommend\nAs a precaution, once you are able to sign in, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-14T03:36:59.47+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_568sdt6t8lhf", "status": "investigating", "body": "\nWe are still making progress restoring the service, we expect the logins to app.bitrise.io to be restored soon, we are still working on a timeline for full restoration.\n\nWhat we recommend\nAs a precaution, once you are able to sign in, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-14T04:31:15.927+00:00" }, { "id": "update_statuspage_bitrise_7055z4g9nbck_xv0039n0gz4f", "status": "investigating", "body": "\nWe are still making progress restoring the service, we expect the logins to app.bitrise.io to be restored soon, we are still working on a timeline for full restoration.\n\nWhat we recommend\nAs a precaution, once you are able to sign in, we recommend that you rotate all secrets, access tokens, and certificates stored in Bitrise.\n\nServices:\nAll Services\n\nScope:\nAll Users\n\nSeverity:\nSEV-1\n\nWhen will the next update be available?\nYou can expect a status update approximately 1 hour from now.", "createdAt": "2026-11-14T05:50:42.615+00:00" } ], "access": { "plan": "public", "keyed": false } } }