Close logo

Is Close Down?

MarketingLive status, outages, and incident history

No. Close is up right now.

Every monitored Close system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment Close breaks

Close is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Close status page
How we know: the official Close status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Close Status Summary

As of 22:50 UTC on 9 November 2026, Close is operational. PulsAPI checked Close's official status page and found 20 of 20 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Close, counting degraded performance as up. The latest incident, "App is unavailable for some customers", was on Oct 28, 2026 and lasted 28 min.

Cite as: PulsAPI, “Close status”, checked 9 November 2026, 22:50 UTC. https://www.pulsapi.com/services/close

Close Component Status

The main Close systems on this page. All 20 are operational right now.

20operational
API
Operational
Application UI
Operational
Calendar - Syncing
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Email » Sending, Email » Syncing, Phone » Call Recording, Phone » Dialer, Phone » Downstream Telephony Carriers, Phone » Incoming Calls, Phone » Outgoing Calls, Phone » Outgoing Calls - Infrastructure, Phone » Phone Service, Phone » SMS, Phone » Telephony Provider Connectivity, Public Website, and 3 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Close Outages & Incidents

Incident history from the official Close status page, including resolution updates.

App is unavailable for some customersResolved Oct 28, 2026 · 28 minResolved

This incident has been resolved. --- [2026-10-28T10:54:35.168-07:00] (monitoring) The issue has been identified and reverted. Monitoring to ensure everything goes back to normal. --- [2026-10-28T10:41:47.066-07:00] (investigating) Part of our search infrastructure is degraded and is affecting app availability for customers on the affected cluster

Application impairmentResolved Sep 29, 2026 · 26 minResolved

Close sincerely apologizes for the interruption of our service. We take the stability of our platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact Close systems were unavailable for 30 minutes from Sep 29, 17:40 UTC to Sep 29, 18:10 UTC. ## Root Cause and Resolution During deployment of a new application version, we ran a multi-phased migration that added a permission to user roles and assigned it to existing custom roles. The timing of the phased migration wasn’t fully thought out; many application servers were still running the previous version which didn’t recognize the new permission in the database. As a result, error rates increased. We restored service by removing the permission from existing roles. To prevent similar incidents, we’re updating our testing and deployment pipeline to identify migrations that require a phased rollout. ## Timeline * 17:40 UTC - Migration was run and PR was merged. * 17:41 UTC - Engineering team alerted of API failures and application unresponsiveness * 17:43 UTC - Engineering team begins incident response, status page updated * 17:44 UTC - Potential root cause identified \(backfill migration was run before code finished deploying\). * 17:44 UTC - We thought we could fall forward, but realized that was going to take longer so we then decided to revert the migration. This added to the outage time. * 18:10 UTC - Engineering team runs a script to drop the new permission from existing custom roles * 18:10 UTC - Application loading again, error rates dropped. Customer impact ends. --- [2026-09-29T11:15:06.734-07:00] (resolved) This incident has been resolved. --- [2026-09-29T11:11:35.334-07:00] (monitoring) The issue was identified and reverted. We continue to monitor the application to ensure everything is back to normal. --- [2026-09-29T10:48:37.127-07:00] (investigating) We are currently investigating issues with parts of the Close application not loading.

Close Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Close incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 1 day with incidentsNov 9

Going further back: Close uptime by month and every recorded Close outage.

Live Close Outage Reports

Problems reported by engineers using Close. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Close problems reported yet.

Something wrong with Close on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Close

Close publishes a public status page at status.close.com covering 23 components, including Phone Service, Application UI and Indexing. PulsAPI tracks Close outages, degraded performance and incident history in real time, alongside the rest of your marketing stack.

Over the past 30 days, PulsAPI has measured Close uptime at 100.00%. Response times, incident history, and SLA tracking for Close are available on the PulsAPI dashboard.

Close Status FAQ

Is Close down right now?

The verdict at the top of this page comes from the latest poll of the official Close status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Close is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Close recovers.

How do I check Close uptime history?

PulsAPI tracks Close uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Close changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Close outages?

PulsAPI reads the official Close status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Close components?

Yes. PulsAPI monitors 20 individual Close components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Close goes down?

Yes. Create a free account and subscribe to Close: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Close to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Close problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Close?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Close plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Close with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services