Skip to main content
Close logo

Is Close Down?

No — Close is up

Reachable from all 8 checked regions

Average response time: 643ms

Last checked · checks run every 6 hours

Official status page: https://status.close.com

Close uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
608ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

12-day clean streak
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: 100.00% uptime, 16 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 32 checks
Sep 3: 100.00% uptime, 28 checks
Sep 4: 100.00% uptime, 28 checks
Sep 5: 100.00% uptime, 24 checks
Sep 6: 100.00% uptime, 24 checks
Sep 7: 100.00% uptime, 30 checks
Sep 8: 100.00% uptime, 35 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 8 checks
Aug 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
696ms
DNS 0ms TCP 138ms TLS 140ms TTFB 558ms
arn
886ms
DNS 0ms TCP 178ms TLS 178ms TTFB 710ms
bom
1290ms
DNS 0ms TCP 255ms TLS 258ms TTFB 1027ms
cdg
678ms
DNS 0ms TCP 134ms TLS 137ms TTFB 543ms
dfw
257ms
DNS 0ms TCP 50ms TLS 53ms TTFB 207ms
ewr
332ms
DNS 0ms TCP 65ms TLS 68ms TTFB 267ms
fra
712ms
DNS 0ms TCP 141ms TLS 144ms TTFB 440ms
yyz
299ms
DNS 0ms TCP 59ms TLS 62ms TTFB 240ms

What Close does

Close is a sales CRM built around outbound calling and email. It combines contact and pipeline management with a built-in dialer, call recording, SMS and two-way email sync, so a representative works a list without leaving the app. Small sales teams run an entire day inside it, which makes it a dependency for calling and for pipeline data at the same time.

What an outage looks like

Close reports calling separately from the app itself, so the interface can load and save records normally while Incoming Calls, Outgoing Calls, the Dialer or Call Recording fail. Representatives then see the pipeline but cannot reach anyone. Email Syncing failing leaves inboxes stale with no error, and Search has its own Indexing and Querying rows, so lookups return nothing while the data is intact.

What to do about it

Check status.close.com and read the component tree rather than the headline. Close separates Application UI, API, Public Website, Search, Email and Phone, and splits Phone further into Telephony Provider Connectivity, Downstream Telephony Carriers and three Twilio infrastructure rows. If a Twilio row is red, the fault sits upstream of Close and no change on your side will fix it.

Is it down for everyone, or just you?

If this page says Close is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Pipedrive
Pipedrive
HubSpot
HubSpot
SalesLoft
SalesLoft
Attio
Attio

Close outage FAQ

Close loads fine but my calls will not connect. Is Close down?
Partly, most likely. Close reports Phone as a group of components distinct from Application UI, covering Phone Service, Incoming Calls, Outgoing Calls, the Dialer, Call Recording and SMS. Calling can fail completely while the CRM records, pipeline and search behave normally, so check the Phone rows rather than judging by whether the app opens.
Does a Twilio outage take Close calling down with it?
It can, and Close makes that visible. The status page lists Outgoing Calls infrastructure rows for the Twilio Conference Calling API, the Twilio REST API and Twilio TwiML, plus Telephony Provider Connectivity and Downstream Telephony Carriers. When one of those is the failing component, the problem is upstream of Close, and waiting is the only real option.
Why is my email not syncing when Close otherwise looks fine?
Email is tracked separately, and split into Syncing and Sending. Syncing can fail while the rest of Close works, which leaves conversations looking stale rather than throwing an error, so it is easy to miss. If replies seem to have stopped arriving against contacts, check the Email components before re-connecting your mailbox.
Search returns nothing. Has my data been lost?
Almost certainly not. Close reports Search as its own component with separate Indexing and Querying rows, which means lookups can fail while the underlying records are untouched. Open a contact or opportunity directly by link to confirm the data is present. Records created while indexing is degraded may not appear in results until it recovers.
Does a Close outage affect the integrations built on its API?
Check the API row, which Close reports apart from Application UI. An incident can affect programmatic access while the web app serves normally, or the reverse, so integrations and users do not always fail together. Match the failing component to the endpoints your integration calls before assuming all automation has stopped.

How we measure this

  • We request Close's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Close publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Close goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required