status.vims.com
UnknownChecking status…
VIMS runs peer-to-peer: most traffic goes directly between peers over Hyperswarm rather than through a server. These figures describe the relay and the public entry points, and refresh every 30 seconds.
Overall status: Unknown.
Desktop downloads
Counted at the edge as release artifacts are served.
Completed artifact downloads. Update probes and partial range requests are excluded.
Network
Live Hyperswarm overlay as seen from the relay node.
Relay unreachable — peer count unavailable, not zero
Hyperswarm topics the relay currently holds
Since the swarm sidecar last started
— published services
Peer counts are one node’s view of the swarm. Hyperswarm has no central registry, so a global total is not a knowable number — this is the relay’s live connection count.
Subsystems
Reported by the daemon about itself — functional health, not just reachability.
Public endpoints
Probed from your browser, so this reflects the network path you actually have.
- Unknownapi.vims.com
Daemon HTTP API
- Unknownswarm.vims.com
Hyperswarm WebSocket relay
- Unknownupdates.vims.com
Release artifacts + download counts
- Unknownmeeting.vims.com
WebRTC meetings
- Unknownschedule.vims.com
P2P scheduling
- Unknownchat.vims.com
Nostr chat
- Unknownagent.vims.com
Agent marketplace
- Unknowndrive.vims.com
P2P file drive
- Unknownkeys.vims.com
Key manager
- Unknownteam.vims.com
Team surface
- Unknown
api.vims.com/api/mcp/builtin/docs/rpc
MCP endpoint for docs tools
These checks confirm DNS, TLS and that the edge answered. Cross-origin responses are opaque by design, so they cannot distinguish a reachable host returning errors — the subsystem panel above is what reports functional health.
Agent NFT chains
Networks the agent protocol is deployed to, with every contract address.