opensanctions / opensanctions/opensanctions
kg_fiu_national: source host unreachable since 2026-09-17, origin down during site relaunch
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 810
- Forks
- 187
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 133
Description
kg_fiu_national fails with ConnectTimeout on https://fiu.gov.kg/sked/9.
- Failing since 2026-09-17 09:57, first failed run
20260917095701-kkh - Last good run
20260916095701-klr(2026-09-16), 2496 entities / 1244 targets
The origin is down, not blocking us:
- TCP 80/443 time out locally, from the runner, and from all 57 check-host.net nodes.
- The domain is on Cloudflare nameservers, and Cloudflare's own proxy returns 522
(origin connection timed out), so this is not geo-blocking or bot protection and
geolocation=would not help. - Every subdomain (
www,analytics,reports,mail, ...) resolves to the same
146.120.212.37and is equally dark.
The agency announced a new official website from 2026-09-16 (news item fiu.gov.kg/news/2036),
the day of our last good run. It looks like a relaunch on the same domain rather than a
move: Sectigo certificates for fiu.gov.kg, www.fiu.gov.kg and a new
privateoffice.fiu.gov.kg were issued 2026-08-05, and every guessed alternative domain is
NXDOMAIN.
Nothing to land. When the host answers again, check whether /sked/9 and the XML link
survived the new platform.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No code change is identified while fiu.gov.kg is unreachable. When the host responds again, check https://fiu.gov.kg/sked/9 and confirm that its XML link and the expected entities and targets are still available; completion means verifying whether the existing source can run successfully or documenting the required follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100