# NousResearch/hermes-agent · Telegram connectivity fallbacks and proxy handling

## Open now

- 1 issue, 0 PRs open on GitHub.
- #47146: Telegram: full ISP block of api.telegram.org defeats fallback-IP transport — document/automate the TELEGRAM_PROXY remedy

These items address expanding fallback IP pools, adding DNS-over-HTTPS providers, passing proxy URLs explicitly, and handling ISP-level blocks of api.telegram.org. Work spans both automated fixes and documentation of proxy remedies.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Open related issues

- #47146: Telegram: full ISP block of api.telegram.org defeats fallback-IP transport — document/automate the TELEGRAM_PROXY remedy

## Prior & competing PRs

- **#60737: fix(gateway): expand Telegram fallback IP pool and DoH providers**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#60776: fix(gateway): expand Telegram fallback IPs, fix TimeoutStopSec detection, log connection success**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#31981`, `#32021`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`