listRepos on the relay bsky.network is missing about 10M repos

[imax9000]

There's currently over 28M accounts in total, but the relay seems to return in listRepos only about 18M. Thanks to it using a sequentially increasing integer ID as a cursor, it's possible to craft a cursor value and query an arbitrary range of IDs.

Querying https://bsky.network/xrpc/com.atproto.sync.listRepos?cursor=20000000&limit=3 right now returns {"repos":[]}, meaning that there's less than 20M repos it knows about.

As far as I can tell, PDS should send an #account event as soon as a new account is created, and that should result in the relay adding it to its database. So "accounts that have not created a single record" doesn't really explain it.

What could be causing such a discrepancy?

[DavidBuchanan314]

I believe the current relay instance was started on around November 2024, per #3036

So maybe 18M is the number of accounts that have been active since then?

[imax9000]

Hm, yeah, that might explain it

[Nick-Triller]

@DavidBuchanan314 Do you think it makes sense to backfill the data, if that’s possible? If not, I can create a PR to mention this in the docs of listRepos endpoint.