International Duck Incorporated says it moved active development to GitLab after GitHub access disruptions affected its organization and member accounts. Public checks confirm that the GitHub organization, its repository pages, and the affected member profiles remain unavailable, while the GitLab group is public and active. This page separates team-reported support details from independently visible platform records.
Public checks return 404 for IDI’s GitHub organization, all four direct repository pages, and the @0xFFshell and @3spress0 profiles. GitHub’s aggregate organization API still lists limited metadata, but direct repository API requests and Git clone checks fail. GitLab’s group, six projects, and @0xFFshell profile are public. According to the team’s support records, tickets #4776851 and #4788849 still await a response.
Times below use Central European Summer Time, UTC+2.
According to the team’s support record, ticket #4776851 requested restoration of the @3spress0 profile after it reportedly stopped appearing publicly. A public check on September 29 still returns 404 for that profile; the ticket itself and GitHub’s reason are not public.
Team-reported ticket · profile currently unavailableThe team reported losing dependable access to its shared GitHub organization. GitHub’s public status history lists no platform-wide incident on September 21, so the cause is not independently established. As of September 29 at 11:14 CEST, the organization page, all four direct repository pages, and the former GitHub Pages site still return 404, while Git clone checks fail. GitHub’s aggregate organization endpoints continue to expose limited metadata, but direct access remains unavailable.
Organization and repositories still unavailableAccording to the team’s support record, ticket #4788849 was opened after GitHub banned the @0xFFshell account. Public checks confirm that the GitHub profile returns 404, but cannot confirm the reason. GitHub account-ID chronology places its creation on September 23, 2026; the active GitLab profile publicly states “Member since September 24, 2026.”
Ban is team-reported · public status: GitHub 404, GitLab activeGitLab’s public API timestamps the group at 14:20:34 CEST and Venomous one second later. The website followed at 14:54, NullTrace at 15:29, and ChampionsCode at 15:35. All four projects remain public and non-archived.
Verified through GitLab’s public APIGitLab’s public profile for @Xx-superIvar-xX states “Member since September 28, 2026,” one day before this update. No GitHub disruption or appeal has been reported for this member; the join appears to be a direct GitLab signup rather than a migration case.
Verified through GitLab’s public profileAccording to the team’s support records, no response has been received for either appeal. At this update, ticket #4776851 had been pending for 8 days and 1 hour, and ticket #4788849 for 5 days and 1 hour. Ticket contents and response status are private and cannot be independently verified.
Team-reported · 2 appeals pendingThe team says the move allowed development, releases, issue tracking, and collaboration to continue while the appeals remained open. Public GitLab records confirm continued project activity after the move; public records do not reveal GitHub’s internal rationale or review status.
GitHub’s aggregate organization API still lists four repositories and five public members, but the organization page, direct repository pages, individual repository API endpoints, and unauthenticated Git access are unavailable. GitLab publicly hosts all six current, non-archived group projects and should be treated as IDI’s source of record.
GitLab’s public API lists six non-archived group projects and records project activity through September 29, 2026. With direct GitHub access still returning 404, GitLab is the currently verifiable source for code, releases, issues, and project history.
Fact-check completed September 29, 2026 at 11:17 CEST using GitHub web pages, public aggregate and direct REST API endpoints, unauthenticated HTTPS Git checks, and GitLab web/API records. Ticket numbers, ticket contents, response status, and the reported ban reason come from the team and are not independently public. Because the GitHub profile is unavailable, its September 23 join date is reconstructed from GitHub account-ID chronology; the September 24 GitLab date is displayed publicly on the active profile.
