Status

Service status

Collectivus is in Founding Members beta, Uptime is best-effort during this period - we'll be transparent about incidents in real time and document them here.

Live status board (coming soon)

We'll publish a public Statuspage at GA with subscribed incident emails, RSS, and historical uptime, Until then, beta participants get incident emails directly to the address on file.

Incident communication during beta

P0 incidents (service down): we email all Founding Members within 15 minutes of detection.
P1 incidents (degraded): we update affected customers within 1 hour.
Planned maintenance: at least 24 hours of email notice for any change that affects login or workflows.
Post-mortems: we publish a written summary for any P0/P1 within 5 business days.

Reach a human

During the beta, the fastest channel is email to admin@collectivus.ai. You can also open a support thread and we'll route it.

Status

Service status

Collectivus is in Founding Members beta, Uptime is best-effort during this period - we'll be transparent about incidents in real time and document them here.

Live status board (coming soon)

We'll publish a public Statuspage at GA with subscribed incident emails, RSS, and historical uptime, Until then, beta participants get incident emails directly to the address on file.

Incident communication during beta

P0 incidents (service down): we email all Founding Members within 15 minutes of detection.
P1 incidents (degraded): we update affected customers within 1 hour.
Planned maintenance: at least 24 hours of email notice for any change that affects login or workflows.
Post-mortems: we publish a written summary for any P0/P1 within 5 business days.

Reach a human

During the beta, the fastest channel is email to admin@collectivus.ai. You can also open a support thread and we'll route it.