Email
Per-component or all-components. Updates for new incidents, transitions, and resolution.
Current status
All systems operational
Last checked · 2 minutes ago
Region
Components · Global
Per-system health, current latency, last incident.
Component
Status
Last incident
Web app
citesvue.com
Operational
12 days ago
API
api.citesvue.com
Operational
23 days ago
Recording ingestion
Multipart upload + assembly
Operational
8 days ago
Speech transcription
Speaker-aware ASR
Operational
34 days ago
Visual intelligence
Frame analysis + OCR
Operational
41 days ago
Artifact extraction
Bug, requirement, decision typing
Operational
17 days ago
Q&A copilot
Cited answers, citation mode
Operational
6 days ago
Integrations — Jira
Push + linkback
Operational
14 days ago
Integrations — Linear
Push + linkback
Operational
47 days ago
Integrations — Notion
Push + database row
Operational
29 days ago
Integrations — Slack
Channel routing + digests
Operational
11 days ago
Integrations — Confluence
Decisions + audit reports
Operational
52 days ago
Authentication / SSO
SAML 2.0 / OIDC / SCIM
Operational
19 days ago
Webhooks (outbound)
Per-tenant fair-share
Operational
8 days ago
Operational — within SLO. Degraded performance — measurable elevation in latency or error rate, no functional loss. Partial outage — subset of users or operations affected. Major outage — service unavailable for the majority of users.
Uptime · Global
90-day component uptime.
Web app
99.99%
API
99.98%
Recording ingestion
99.95%
Speech transcription
99.92%
Visual intelligence
99.94%
Artifact extraction
99.96%
Q&A copilot
99.91%
Integrations (aggregate)
99.93%
Authentication / SSO
99.97%
Webhooks
99.94%
Strip legend: green = operational, yellow = degraded, red = major outage. Hover a cell for the day’s incident summary.
Active incidents · Global
No active incidents.
Last incident closed 6 days ago. Subscribe below to be notified the moment something changes.
Recent history · Global
Last 5 incidents — date, duration, components, summary.
- 12 days agominor·47 minutesElevated latency on Q&A copilot in EU region.Affected: Q&A copilot (EU)
- 17 days agominor·18 minutesJira push retry storm.Affected: Integrations — Jira
- 24 days agomajor·2 hours 11 minutesRecording ingestion delayed for large uploads (> 2 GB).Affected: Recording ingestion
- 31 days agominor·9 minutesWebhook deliveries delayed.Affected: Webhooks (outbound)
- 52 days agomajor·33 minutesSSO logins failing for SAML customers.Affected: Authentication / SSO
Scheduled maintenance
Published in advance. Outside business hours where possible.
Standard window
Sundays 02:00–05:00 UTC. Used selectively. Announced ≥ 7 days in advance via this page, email, and in-product banner.
Emergency maintenance
When required for security or stability. Communicated as soon as the work is scheduled, even if < 7 days out, with the reason explicit.
Customer-impacting changes
Breaking API changes follow the public deprecation policy (≥ 90 days’ notice for any non-additive change to the documented API).
UpcomingNone scheduled.
Stay informed
Get notified the moment status changes.
Pick any combination of channels. Workspace owners on Team+ receive critical incident notifications by default — extend distribution to security and on-call contacts in workspace settings.
RSS / Atom
/status/feed.rss · /status/feed.atom · per-component feeds.
Slack webhook
Drop a Slack incoming webhook URL; we post incident updates to your channel.
Programmatic
GET /status/v1/summary returns the JSON the page renders from.
SLA reference
See tier comparison →This page reports state. SLA commitments live with pricing.
Citesvue publishes operational state on this page for everyone. Contractual uptime SLAs and remedies are tier-specific and apply to Enterprise workspaces with dedicated support.
Communications
A predictable channel ladder, every time.
- 01Status page. First update goes here, every time, regardless of severity.
- 02Email. To workspace owners and on-file security contacts for SEV-1 and SEV-2.
- 03In-product banner. For SEV-1 incidents affecting authenticated sessions.
- 04CS / Enterprise account contacts. For Enterprise SEV-1, on-call CS lead reaches out within the SLA window.
- 05Post-incident report. ≤ 5 business days for SEV-1/SEV-2; ≤ 10 for SEV-3.
We do not use Twitter / X as a primary incident channel. The status page is the source of truth.
Severity & cadence
What “regular updates” actually means.
| Severity | Definition | First public update | Update cadence | Post-mortem |
|---|---|---|---|---|
| SEV-1 | Service unavailable for the majority of users; data integrity at risk | ≤ 15 minutes | Every 30 minutes | ≤ 5 business days |
| SEV-2 | Significant degradation; subset of users or one component degraded | ≤ 30 minutes | Every 60 minutes | ≤ 5 business days |
| SEV-3 | Minor degradation; workaround available; small user impact | ≤ 60 minutes | At state changes | ≤ 10 business days |
| SEV-4 | Cosmetic or low-impact issue; no user-visible effect | Logged when resolved | N/A | N/A |
A confirmed material breach triggers a separate, parallel notification path — see breach notification on /compliance.