pds.socialweb.computer

Up

First seen about 18 hours ago. History fills in as we watch.

Relay status: active (fast tier)
Accounts: 2 as reported by the relays
DID: did:key:zQ3shaCU5MHmdRj38xh2m7fhankpbZVqSvz5V5sKcFfYNpfde
Sample repo: —
TLS expires: 2027-01-01 (87 days, warns at 14)
Last checked: 1 minute ago
Last reached: 1 minute ago
First seen: about 18 hours ago

Relay sync

Is each Bluesky relay keeping up with this host?

us-east: Receiving seq moved 4 minutes ago host listRepos HTTP 404
us-west: Not checked yet host listRepos HTTP 404

This measures the relay, not the host. We compare the newest commit we can find among the host's accounts, so a quiet host can't show lag.

Checks

Success is the share of checks that passed in the last 30 days, not time-weighted availability.

Check	Last result	Latency	Detail	When	30-day check success
describe_server	passed	193 ms	—	1 minute ago	100% of 206 checks
latest_commit	skipped	—	skipped: no sample did (listRepos HTTP 404)	1 minute ago	no data
tls	passed	—	expires in 87 days	about 3 hours ago	100% of 1 checks

Run one of these?

Join the claiming waitlist. When claiming opens, operators get alerts when a service goes quiet, an embeddable status badge, and error tracking for their indexer.