{
  "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-09-04T22:17:55.634Z"
  },
  "data": {
    "id": "incident_statuspage_semaphore_256zhdm3l3q4",
    "slug": "semaphore-periodic-authentication-failure-with-github-repositories-2026-09-02-hdm3l3q4",
    "title": "Periodic authentication failure with GitHub repositories",
    "summary": "Periodic authentication failure with GitHub repositories",
    "status": "resolved",
    "severity": "minor",
    "startedAt": "2026-09-02T16:08:41.039+00:00",
    "updatedAt": "2026-09-03T16:41:09.499+00:00",
    "resolvedAt": "2026-09-03T16:41:09.481+00:00",
    "provider": {
      "slug": "semaphore",
      "name": "Semaphore"
    },
    "affectedServices": [
      {
        "slug": "semaphore-platform",
        "name": "Semaphore platform"
      }
    ],
    "links": {
      "html": "/incidents/semaphore-periodic-authentication-failure-with-github-repositories-2026-09-02-hdm3l3q4",
      "api": "/api/v1/incidents/semaphore-periodic-authentication-failure-with-github-repositories-2026-09-02-hdm3l3q4",
      "providerHtml": "/providers/semaphore",
      "alerts": "https://outagedeck.com/account?stack=semaphore&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "Semaphore reported a minor event for the affected tracked services.",
    "source": {
      "id": "source_semaphore_status",
      "kind": "official_api",
      "name": "Semaphore Status",
      "checkedAt": "2026-09-04T22:15:04.796+00:00",
      "officialUrl": "https://status.semaphore.io",
      "statusPageUrl": "https://status.semaphore.io"
    },
    "updates": [
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_26zcdzbzzlqw",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T16:08:41.15+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_dk0bm48yvnx6",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T16:35:57.159+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_tfvty2jls4vj",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T17:04:01.778+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_7tygkwbspfbj",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T17:32:55.297+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_1cs7219m62wg",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T18:02:30.334+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_tkkfv7189s6b",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T18:31:31.696+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_v9jlpl60tgw1",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T19:00:14.501+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_khwf5ts5gcmh",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T19:32:45.418+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_ks6c7w0ny5xt",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T20:00:13.198+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_8g8wwdrswlbs",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T20:30:26.641+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_h8d2w9ct2psm",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T21:00:37.88+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_15wg27y1mnqt",
        "status": "identified",
        "body": "The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:\nhttps://github.com/orgs/community/discussions/206581\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1\n\nWe are continuing to monitor the situation on our end and will share further updates as they become available.",
        "createdAt": "2026-09-02T21:30:52.027+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_0l10tnshfrmq",
        "status": "identified",
        "body": "Our engineers are actively monitoring the ongoing situation affecting HTTPS operations: https://github.com/orgs/community/discussions/206581. We’ll share the next update once we have new information from GitHub.\n\nAs a workaround, you can configure git to use only HTTP/1.1, using the following command:\ngit config --global http.version HTTP/1.1",
        "createdAt": "2026-09-02T22:07:08.283+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_hw2r1rysq9q5",
        "status": "identified",
        "body": "Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available.\n\nTo prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime.\n\nIf the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force Git to use HTTP/1.1:\ngit config --global http.version HTTP/1.1",
        "createdAt": "2026-09-03T12:45:39.753+00:00"
      },
      {
        "id": "update_statuspage_semaphore_256zhdm3l3q4_6jhjvsl0vvrf",
        "status": "resolved",
        "body": "Semaphore is currently operating normally, which is why we’re marking this incident as resolved.\n\nGitHub confirmed that the behavior affecting unauthenticated Git operations is the result of an intentional change on their end rather than a bug. You can read their latest statement here:\nhttps://github.com/orgs/community/discussions/206581#discussioncomment-18269083\n\nFor builds affected by this behavior, the previously shared workaround remains available. Configure Git to use HTTP/1.1 before running the affected Git operation: \ngit config --global http.version HTTP/1.1 \n\nWe will add this instruction and further context to our documentation. Any additional guidance from Semaphore will be shared through in-app notifications. \n\nFor further assistance, contact our support team at support@semaphore.io.",
        "createdAt": "2026-09-03T16:41:09.481+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}