You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@mishmosh@darobin@aschmahmann I've looked into some prior art (@ns4plabs shared access with me) and to reduce setup overhead, we could reuse existing Pingdom and Status Page accounts (owned by PL, hosting https://drand.statuspage.io and https://ipfsgateway.statuspage.io already) for this, and create a new, all-in-one status page at https://ipfs-public-utilities.statuspage.io. We could also have a dedicated account owned by Shipyard or Foundation, if that is preferred, but kicking-off with existing one will be easier.
Setting this up would enable us to not have at glance status page, but also have a public, unified audit log of scheduled maintenance and operational incidents related to Public Infrastructure, similar to https://status.digitalocean.com/history (screenshot).
Lmk if this sound like a good deliverable, or we should aim at something different.
We want something similar to https://status.digitalocean.com where
The status page should be linked from https://docs.ipfs.tech/concepts/public-utilities/
We could revive https://ipfsgateway.statuspage.io and repurpose it to be about "IPFS Public Utilities" and include
List of utilities to track
ipfs.io
dweb.link
trustless-gateway.link
inbrowser.link
(future)delegated-ipfs.dev/routing/v1
delegated-ipfs.dev/dns-query
/dnsaddr/bootstrap.libp2p.io
ipfs.tech
,docs.ipfs.tech
,blog.ipfs.tech
,dist.ipfs.tech
,discuss.ipfs.tech
etcInspiration / Prior art
The text was updated successfully, but these errors were encountered: