Self-hosted PDS peers.social not being picked up by relay after requestCrawl and #commit

[grigb]

Hi,

I run a self-hosted AT Protocol PDS at peers.social. We are trying to get an account indexed by the Bluesky public relay/AppView, but the public relay still returns RepoNotFound even though our PDS and DID state are live and requestCrawl has been accepted.

Host: peers.social
PDS service DID: did:web:peers.social
Example account DID: did:plc:wocwiah2pe7ivzqygj2gniuf
Example handle: wo1781776040987.at.peers.social

Current state on our side:

• The did:plc cutover is applied and live.
• plc.directory resolves the account DID.
• peers.social serves com.atproto.sync.getLatestCommit for the account DID with HTTP 200.
• peers.social exposes the firehose at wss://peers.social/xrpc/com.atproto.sync.subscribeRepos.
• We issued com.atproto.sync.requestCrawl to bsky.network and the new relay hosts, and those calls returned HTTP 200.
• We emitted fresh firehose #commit nudges after requestCrawl.

The remaining failure:

• relay1.us-west.bsky.network getLatestCommit for did:plc:wocwiah2pe7ivzqygj2gniuf still returns HTTP 404 RepoNotFound.
• bsky.network getLatestCommit for the same DID still returns HTTP 404 RepoNotFound.
• public.api.bsky.app app.bsky.actor.getProfile for the same DID still returns HTTP 400 Profile not found.

Could someone help confirm whether peers.social is being crawled, whether it is blocked or failing validation, or whether there is a relay allowlist/rate-limit/config issue we need to address?

The key thing we need is for the public Bluesky relay/AppView path to ingest peers.social so this DID becomes visible through public.api.bsky.app.

Thank you.

Grig Bilham
Peers.Social