Conga Status
System status
Incident overview
Total incidents
14
Active now
1
Resolved
13
Avg. resolution
20h 34m
Recent incidents
View all →Investigating Issue Impacting Sign Professional
Investigating Issue Impacting Conga Platform - EU region
Informational Notice – Salesforce Service Disruption
Investigating Issue Impacting Composer in EU
Investigating Issue Impacting Login on Platform NA region
Investigating Issue Impacting email functionality on Conga Platform
Investigating Issue Impacting Conga Contracts
Partial Service Degradation - Conga Platform
Conga Contracts – North America Performance Degradation
Investigating Issue Impacting Conga Contracts
Frequently asked questions
Is Conga down right now?
Conga is currently experiencing issues with 1 active incident. Current status: Operational. Check the incident details above for more information.
What is Conga's current uptime?
Conga has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Conga's official status page data.
How many incidents has Conga had recently?
Conga has experienced 14 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 20h 34m. 1 incident is currently active.
What components does Conga monitor?
DevHelm tracks 130 individual components for Conga, including Conga CLM - AP, Conga Contracts - NA, CPQ Catalog Service - FR, CPQ Catalog Service - NA, Conga Composer - NA, and 125 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Conga outages?
You can subscribe to Conga's incident feed via Atom/RSS at devhelm.io/status/conga/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Conga as a dependency in your DevHelm workspace.
About Conga status monitoring
This page provides real-time operational status for Conga, powered by DevHelm's continuous monitoring infrastructure. We track Conga's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Conga status data is refreshed every 30 seconds. We currently track 130 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Conga in your stack
Get alerted when Conga has issues — before your users notice. Set up in 30 seconds.