Get told when Close CRM breaks
One email when Close CRM reports an incident, one when it is resolved. No account, nothing else.
Used only for Close CRM status alerts. Every email carries an unsubscribe link.
Close CRM components
20 of 20 operational
Show all 20 components
- Phone ServiceOperational
- Application UIOperational
- IndexingOperational
- SyncingOperational
- APIOperational
- Incoming CallsOperational
- SendingOperational
- QueryingOperational
- Public WebsiteOperational
- Outgoing CallsOperational
- DialerOperational
- Call RecordingOperational
- SMSOperational
- Support CenterOperational
- Telephony Provider ConnectivityOperational
- Downstream Telephony CarriersOperational
- Calendar - SyncingOperational
- Outgoing Calls - Infrastructure (Twilio Conference Calling API)Operational
- Outgoing Calls - Infrastructure (Twilio REST API)Operational
- Outgoing Calls - Infrastructure (Twilio TwiML)Operational
Recent Close CRM incidents
The most recent incidents Close CRM has published, newest first.
- major
Database Failures
Resolved in 2h 3m
- major
Database Failures
Resolved in 59m
Close CRM status: common questions
- Is Close CRM down right now?
- Close CRM's status feed has stopped refreshing — the readings below are the last ones we received. All 20 components are operational. No incident is open. This page mirrors the official Close CRM status feed. PingView last read it on August 25, 2026 at 11:09 PM UTC.
- Where does this Close CRM status data come from?
- Directly from the official Close CRM status page at status.close.com. PingView polls that feed, records every incident it publishes and keeps a permanent, dated history that the vendor page itself does not retain.
- How often is this page updated?
- PingView reads the official Close CRM feed and rebuilds this page every 5 minutes. The timestamp of the last successful read is shown next to the status, so you can tell how fresh the answer is.
- Close CRM reports everything as operational, but my integration is failing. What now?
- A vendor status page is a global signal, not a per customer one. Partial failures, regional routing problems and issues that hit a single account often never appear on it. Check the Close CRM endpoints your own product calls, from more than one region, and compare your timeline against the vendor's. That is what PingView does, and the SLA calculator turns the resulting downtime into a number you can put in front of a client.