Live status & reliability report

Close status, outages & reliability

#6 of 11 CRMsOperational

Close is a sales CRM with built-in calling, email and SMS for small sales teams, run as a remote company founded in the United States.

Data updated Nov 1, 2026 · score recalculated

Over the last 90 days Close had 99.89% effective uptime across 4 status page incidents (4 partial or major outages), resolving them in 59m on average.

88.6/100Reliability scoreVisit Close ↗

Is Close down right now?

No, Close is up and running.

  • Close's status page reports all systems operational. Checked .
  • All 3 Close pages we check are responding. Checked .

Official Close status page ↗

Uptime (90d)99.89%2h 13m weighted downtime
Incidents (90d)41.3 per 30 days
Major / partial outages4
Avg time to resolve59m
Outages we detected0by our independent probes

90-day uptime

Aug 4, 2026 – Aug 10, 2026: no incidentsAug 11, 2026: 93.66% uptime, 2 incidents (Partial outage)Aug 12, 2026 – Sep 28, 2026: no incidentsSep 29, 2026: 99.07% uptime, 1 incident (Partial outage)Sep 30, 2026 – Oct 27, 2026: no incidentsOct 28, 2026: 98.01% uptime, 1 incident (Major outage)Oct 29, 2026 – Nov 1, 2026: no incidents
90 days ago99.897% average daily uptimeToday
  • No incidents
  • Degraded
  • Partial outage
  • Major outage
  • No data

Key facts about Close's reliability

  • Over the past 12 months, Close published 11 incidents on its status page, 6 of them partial or major outages.
  • Its longest outage on record in that time was “Database Failures” on Aug 11, 2026, which lasted 2h 3m.
  • The part of Close most often affected was API (5 of 11 incidents).
  • Close reported 4 incidents in the last 90 days, up from 3 in the 90 days before.
  • Incidents most often began on a Tuesday (4 of 11, UTC).
  • Close's 90-day uptime of 99.89% is above the average for CRMs (99.80%).
  • It resolves incidents faster than the typical CRM: 59m on average, against a median of 1h 55m.

Score breakdown

Uptime · 40% weight
90
99.897% effective uptime
Incident frequency · 20% weight
72
1.33 weighted incidents per 30 days
Time to resolve · 20% weight
92
59m average
Transparency · 20% weight
100
No unreported outages detected

How the score is calculated →

Incidents per month

01234DecJan ’26Feb1 major outage incident1Mar2 degraded performance incidents2Apr1 partial outage incident1May2 degraded performance incidents2JunJul2 partial outage incidents2Aug1 partial outage incident1Sep1 major outage incident1OctNov
  • Major outage
  • Partial outage
  • Degraded
  • Informational

Response time

Daily average response time of Close's public pages, measured by our probes.

Not enough data yet — this chart fills in as our monitoring runs.

Score trend

Daily reliability score (rolling 90-day window).

Not enough data yet — this chart fills in as our monitoring runs.

Close incident history (last 90 days)

Source: Close status page · last checked

Our independent monitoring

We check these public Close pages every 5 minutes. An outage is recorded after two consecutive failed checks.

PageLast checkUptime (30d)Avg response
Sign-in pageUp 100%525 ms
HomepageUp 100%176 ms
Close APIUp 100%535 ms

How Close compares

Most reliable Close alternatives →

Close status FAQ

Is Close down right now?

No, Close is up and running. Close's status page currently reports all systems operational, and all 3 of the Close pages we check every five minutes are responding. This page updates automatically when that changes.

How reliable is Close?

Close has a reliability score of 88.6 out of 100, ranking #6 of 11 CRMs. Over the last 90 days it had 99.89% effective uptime.

How often does Close have outages?

Close published 4 incidents on its status page in the last 90 days (4 partial or major outages) and 11 in the past 12 months.

How long do Close outages last?

Close resolves incidents in 59m on average. Its longest outage in the past year lasted 2h 3m, on Aug 11, 2026.

Does Close have a status page?

Yes. Close's official status page is status.close.com. We read it every five minutes and keep its full incident history.