Cairn
NousResearch/hermes-agent

Telegram connectivity fallbacks and proxy handling

Cluster 47146 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

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.

Open issues1

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

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · duplicate 1

  • #60737 fix(gateway): expand Telegram fallback IP pool and DoH providers · closed without comment
  • #60776 fix(gateway): expand Telegram fallback IPs, fix TimeoutStopSec detection, log connection success · duplicate → #31981, #32021
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/47146.json
cluster/47146.md