
Why was GitHub blocked in Indonesia? On Friday 6 November 2026, users in Indonesia could not reach GitHub, the code hosting platform used by software teams worldwide, for about four hours. In a statement dated Sunday 8 November, the Ministry of Communication and Digital Affairs (Komdigi) said the platform was not the target. It had blocked an IP address at the request of another government agency, and that address turned out to be used by GitHub as well. For any organisation whose software is stored, reviewed or built on GitHub, the episode shows how a security measure aimed at one threat can cut off a service a whole industry depends on.
What happened on 6 November
According to the Komdigi statement, as reported by RRI, JawaPos, Majalah ICT and Selaras, GitHub access in Indonesia was disrupted for about four hours on Friday 6 November. None of the reports we read gives the exact start and end times, and none names a Komdigi official; the statement is attributed to the ministry as a whole. RRI and Majalah ICT say the press release was dated 8 November, and the outlets we read published it on Monday 9 November.
Majalah ICT wrote that developers at first did not know whether they were facing a global GitHub outage, a network problem or a block. The reports we read do not include any statement from GitHub.
What Komdigi says caused it
Komdigi said an internal review found the following sequence:
- A government agency asked Komdigi to block an IP address it suspected was being used to launch malware-based cyber attacks against its network infrastructure.
- Komdigi entered that address into its blocking system.
- A further review found that the same address was also used by GitHub services, so blocking it disrupted access for users in Indonesia.
- Once the cause was identified, Komdigi's technical team removed the address from the blocking system and access returned to normal.
Komdigi said it would evaluate its IP verification and blocking process so that the handling of cyber threats stays targeted and does not disrupt legitimate access. Selaras reported that Komdigi has not disclosed which agency made the request, which IP address was blocked, when the evaluation will take place or what technical changes will follow.
Coverage differs on one point. CNBC Indonesia described the block as a measure intended to close access to certain content that ended up affecting the whole platform. The other outlets we read describe a block on the address itself for security reasons, and Majalah ICT stated that GitHub was not specifically targeted. We report Komdigi's account as given.
Why one blocked address can take down a whole platform
CNBC Indonesia explained that large sites, GitHub among them, serve many services and pages from the same addresses, and that cloud infrastructure can place legitimate and harmful projects in the same address range. Blocking at the level of an IP address therefore reaches everything behind it.
GitHub's own documentation supports the general point. It says GitHub-hosted runners, the machines that run automated builds, use dynamically assigned addresses from shared infrastructure, and that third-party threat intelligence and firewall vendors may flag those addresses as suspicious because of what other users of the same infrastructure do. GitHub says it does not control such lists, that its addresses change from time to time, and that it does not recommend allowing traffic by IP address. Selaras noted that Komdigi has not confirmed whether shared infrastructure of this kind explains the Indonesian incident, so the link remains unconfirmed.
What it means for organisations that build software
This section is our analysis. As Selaras pointed out, GitHub is not only where code is stored: teams use it to review each other's work and, through GitHub Actions, to test and deploy software automatically. A four-hour loss of access can stop releases, hold up urgent fixes and leave automated jobs failing without an obvious cause. Banks, retailers and public bodies that rely on suppliers working on GitHub are exposed too, even if they never log in themselves.
Practical steps for engineering and IT teams
This section is our analysis, not legal advice.
- List the external platforms your delivery depends on. Code hosting, package registries and build services belong on the same risk register as payment gateways and cloud providers.
- Keep a working copy of critical code and dependencies. Selaras suggested internal repository mirrors as one continuity option; cached package registries serve the same purpose for third-party libraries.
- Make sure you can still ship an urgent fix. Decide in advance how a security patch would be built and deployed if the usual pipeline cannot be reached for several hours.
- Monitor from more than one network. Being able to tell quickly whether a failure is a global outage, a local block or your own problem saves hours of guesswork, which is what developers lacked on 6 November.
- Avoid hard-coding a platform's IP addresses into firewalls. GitHub publishes its ranges through its meta API but warns they change; if you must allow by address, monitor that list rather than copying it once.
- Know the escalation path. If a service you depend on is blocked in error, know who in your organisation contacts the provider and the authorities, and what evidence they will need.
What to watch next
Watch whether Komdigi publishes the outcome of its review of IP verification and blocking, and whether it moves towards narrower methods. Majalah ICT has called for checks on shared services before an address is blocked, for blocking by domain, address or account where possible, and for clear routes to report errors and restore access. Watch too whether the requesting agency is named, and whether GitHub comments on the incident.
Sources
- Akses GitHub Kembali Normal, Komdigi Jelaskan Penyebab Gangguan Pemblokiran · RRI(opens in a new tab)
- Akses GitHub Sempat Lumpuh 4 Jam, Komdigi: IP Terblokir · JawaPos(opens in a new tab)
- Komdigi Pastikan Akses GitHub Kembali Normal Setelah Penyesuaian Pemblokiran IP · Majalah ICT(opens in a new tab)
- Komdigi Sebut Pemblokiran IP Malware Sebabkan GitHub Down 4 Jam · Selaras(opens in a new tab)
- Komdigi Beberkan Alasan GitHub Sempat Diblokir Selama 4 Jam · CNBC Indonesia(opens in a new tab)
- About GitHub's IP addresses · GitHub Docs(opens in a new tab)
This briefing was prepared by the Indotek editorial desk with AI assistance, from the public sources listed above. It is general information, not legal or professional advice.
Cloud & Data
How Indotek can help
On 6 November, many teams could neither ship code nor tell why their tools had stopped. Designing delivery platforms that keep working, and show clearly what has failed, when an outside service disappears is part of the cloud and data work Indotek does.
- Platform engineering: we put build and deployment environments into infrastructure as code, so a pipeline can be recreated and run from alternative infrastructure rather than depending on a single external service.
- Observability built in: we add monitoring that distinguishes an upstream outage or block from a fault in your own systems, so a team can see where a failure lies.
- Network and identity design: our cloud architecture work sets out how platforms reach external services securely, without brittle rules tied to addresses that providers change.



