User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Close down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → close.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 16 min ago. Last stored result reached it in 162 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 149 ms | 0 |
| Nov 7 | 0 | 0.0 | 191 ms | 0 |
| Nov 7 | 0 | 0.0 | 75 ms | 0 |
| Nov 7 | 0 | 0.0 | 53 ms | 0 |
| Nov 7 | 0 | 0.0 | 138 ms | 0 |
| Nov 8 | 0 | 0.0 | 70 ms | 0 |
| Nov 8 | 0 | 0.0 | 152 ms | 0 |
| Nov 8 | 0 | 0.0 | 181 ms | 0 |
| Nov 8 | 0 | 0.0 | 235 ms | 0 |
| Nov 9 | 0 | 0.0 | 96 ms | 0 |
| Nov 9 | 0 | 0.0 | 171 ms | 0 |
| Nov 9 | 0 | 0.0 | 136 ms | 0 |
| Nov 9 | 0 | 0.0 | 163 ms | 0 |
| Nov 10 | 0 | 0.0 | 186 ms | 0 |
| Nov 10 | 0 | 0.0 | 86 ms | 0 |
| Nov 10 | 0 | 0.0 | 142 ms | 0 |
| Nov 10 | 0 | 0.0 | 68 ms | 0 |
| Nov 11 | 0 | 0.0 | 128 ms | 0 |
| Nov 11 | 0 | 0.0 | 123 ms | 0 |
| Nov 11 | 0 | 0.0 | 167 ms | 0 |
| Nov 11 | 0 | 0.0 | 127 ms | 0 |
| Nov 12 | 0 | 0.0 | 192 ms | 0 |
| Nov 12 | 0 | 0.0 | 179 ms | 0 |
| Nov 12 | 0 | 0.0 | 196 ms | 0 |
| Nov 12 | 0 | 0.0 | 148 ms | 0 |
| Nov 13 | 0 | 0.0 | 109 ms | 0 |
| Nov 13 | 0 | 0.0 | 65 ms | 0 |
| Nov 13 | 0 | 0.0 | 166 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Close badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
Email - Syncing
We will be performing maintenance on our back-end email sync service Thursday, November 19 at 7:00 PM PST (Friday, November 20 at 03:00 AM UTC). The maintenance may take up to 4 hours and is expected to be complete no later than 11:00 PM PST (07:00 AMUTC). The Close application and API will remain available while we perform maintenance on our back-end email sync service. Email syncing may be…
Announced by Close · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for Close yet. Outages of 10 minutes or more get their own page here.
Having trouble with Close?
One report per service every 10 minutes from this network. No account.
Follow Close
Get an email when Close goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Close alerts to Slack, Discord or a webhook — free.
About Close
Close is listed in our AI category and checked at close.com. Close is the CRM with a built-in AI teammate that works with your team to call leads, qualify prospects, book meetings, and keep your CRM up to date automatically, so you can focus on selling.
Close publishes an official status page at status.close.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 128 ms average, 25–235 ms range across 16 successful checks.
Questions
Is Close down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Close last down?
We have not recorded a public Close incident since monitoring began 8 days ago.
What is Close's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Close respond?
128 ms on average over the last 24 hours (25–235 ms).
Does Close have an official status page?
Yes, at https://status.close.com.
Close not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Close here at once, the problem is on Close's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Close. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.