Is Close Down?

No — Close is up

Close's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 666 ms

Right now

The verdict is the worse of these two. How we decide

Close's status page

status.close.com · read 4 minutes ago · checked every 3 minutes

Operational

Close's components, as its status page reports them
Component	Status
Phone Service	Operational
Incoming Calls	Operational
Outgoing Calls	Operational
Dialer	Operational
Call Recording	Operational
SMS	Operational
Telephony Provider Connectivity	Operational
Downstream Telephony Carriers	Operational
Outgoing Calls - Infrastructure (Twilio Conference Calling API)	Operational
Outgoing Calls - Infrastructure (Twilio REST API)	Operational
Outgoing Calls - Infrastructure (Twilio TwiML)	Operational
Application UI	Operational

8 more, all operational · show all 20

All of Close's components
Component	Status
Phone
Phone Service	Operational
Incoming Calls	Operational
Outgoing Calls	Operational
Dialer	Operational
Call Recording	Operational
SMS	Operational
Telephony Provider Connectivity	Operational
Downstream Telephony Carriers	Operational
Outgoing Calls - Infrastructure (Twilio Conference Calling API)	Operational
Outgoing Calls - Infrastructure (Twilio REST API)	Operational
Outgoing Calls - Infrastructure (Twilio TwiML)	Operational
Application UI	Operational
API	Operational
Public Website	Operational
Support Center	Operational
Calendar - Syncing	Operational
Search
Indexing	Operational
Querying	Operational
Email
Syncing	Operational
Sending	Operational

Open their status page

FlareWarden checks

app.close.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 666 ms
Checked: 1 hour ago

By region

Ashburn reachable, 464 ms
Dallas reachable, 303 ms
Frankfurt reachable, 756 ms
Johannesburg reachable, 1375 ms
London reachable, 768 ms
Los Angeles reachable, 300 ms
Newark reachable, 381 ms
São Paulo reachable, 981 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	42 ms	94 ms	96 ms	423 ms
Dallas	71 ms	51 ms	53 ms	281 ms
Frankfurt	57 ms	156 ms	158 ms	687 ms
Johannesburg	86 ms	286 ms	288 ms	1235 ms
London	40 ms	162 ms	166 ms	696 ms
Los Angeles	154 ms	31 ms	33 ms	286 ms
Newark	19 ms	82 ms	82 ms	345 ms
São Paulo	140 ms	188 ms	191 ms	898 ms

We check that app.close.com loads, not every feature behind it. Test it yourself

History

Incidents Close reported

Since Oct 22, 15 days · from status.close.com

Incidents: 1
Major or critical: 1
Median to resolve: 28m

App is unavailable for some customers
critical · Oct 28
lasted 28m

Close website availability

Measured by FlareWarden · app.close.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 645ms

Last 30 days

68-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of app.close.com from multiple regions every 6 hours. Close's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 68 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Close itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Close goes down

We check Close every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required