Close change history

Close reported a major Application UI outage in which parts of the application failed to load. The incident started at 2026-09-29 17:48 UTC and was resolved at 2026-09-29 18:15 UTC, lasting 26 min. Close said the issue was identified and reverted.

Close reported major database failures causing intermittent service unavailability, starting 2026-08-11 13:12 UTC and resolved at 2026-08-11 15:15 UTC (2 h 3 min). Close adjusted its scaling strategy and reported healthy recovery; its partial postmortem separately described about 2.5 hours of intermittent unavailability between 08:00 UTC and 17:03 UTC.

Close reported a major database-failure outage affecting the API and Application UI, starting at 2026-08-11 08:26 UTC and resolved at 2026-08-11 09:26 UTC (reported duration: 59 min). Engineering remediated an issue with the production database; users were told normal app use was restored by 09:04 UTC.

Close reported a major partial outage affecting some users loading the application, making and receiving calls, and accessing the API. It started at 2026-05-12 09:34 UTC and was resolved at 2026-05-12 11:17 UTC, lasting 1 h 42 min. A fix was implemented by 11:07 UTC; no cause was stated.

Close reported a critical database incident affecting the API and Application UI, starting 2026-03-16 16:08 UTC and resolved at 16:55 UTC (47 min). Its postmortem states all users experienced severe disruption from 15:57 to 16:15 UTC, with automated systems restoring functionality by 16:15 UTC; normal performance was confirmed at resolution.

Close reported a major service interruption affecting calling, including Outgoing Calls and Phone Service, from 2025-10-20 14:20 UTC to 2025-10-20 20:27 UTC (6 h 7 min). Close attributed the disruption to an AWS outage in an unspecified region that affected many services, including calling, and confirmed resolution.

Close reported a major service interruption affecting calling, phone service and telephony provider connectivity from 2025-10-20 10:38 UTC to 2025-10-20 13:12 UTC, lasting 2 h 34 min. Close attributed the disruption to an AWS outage in us-east-1 and marked the incident resolved.

Close reported a major partial outage preventing some users from loading the application or retrieving API data. It started at 2025-10-14 15:26 UTC and was resolved at 2025-10-14 16:00 UTC (computed duration: 33 min); Close implemented a fix and monitored the results.

Close reported a critical Application UI outage starting 2025-06-19 04:23 UTC and resolved at 2025-06-19 05:10 UTC (47 min). Users were unable to load the application UI due to an issue with the serving infrastructure; the postmortem described intermittent loading failures in the Web and Desktop applications.

Close reported a major incident affecting API, Application UI, and email/calendar syncing from 2025-02-11 22:31 UTC to 2025-02-11 23:34 UTC, lasting 1 h 2 min. Users experienced degraded performance and elevated errors; Close rolled out a fix, with UI/API performance recovering before delayed syncing was fully resolved.

Close’s critical Application UI incident ran from 2025-01-06 17:49 UTC to 2025-01-06 19:47 UTC (1 h 58 min). The postmortem reports Web UI unavailability from 2025-01-06 17:33 UTC to 2025-01-06 17:48 UTC (15 minutes). Close cited a deployment-process change and said the issue was reverted.

Close reported a major incident affecting calendar event syncing through its Calendly integration, starting at 2024-10-24 20:17 UTC and resolved at 2024-10-24 21:00 UTC. The incident lasted 42 min; no cause or fix was stated.

Close reported a major incident affecting Application UI: intermittent loading issues began at 2024-09-12 19:29 UTC and were resolved at 2024-09-12 21:01 UTC, lasting 1 h 31 min. Its postmortem states that the app and API were severely degraded by a partial outage of its back end MongoDB database.

Close reported a critical calling outage affecting Phone - Phone Service and Phone Service, starting 2024-04-22 14:53 UTC and resolved 2024-04-22 18:33 UTC, lasting 3 h 40 min. Close attributed the disruption to Twilio issues; Twilio implemented a fix, restoring baseline call functionality by 17:36 UTC.

Close reported a major incident affecting API and Application UI, with elevated error rates and possible request timeouts. It started at 2023-09-05 16:08 UTC and was resolved at 2023-09-05 17:04 UTC; the recorded duration was 55 min. A fix was deployed by 16:17 UTC, restoring normal application operation.

Close reported major degradation and elevated errors affecting its application and API between 16:47 UTC and 17:18 UTC on July 26, 2023. The recorded start, 2023-07-28 15:45 UTC, follows the listed resolution, 2023-07-26 16:30 UTC; computed duration is unknown. No cause or fix is shown.

Close reported a major SMS outage affecting Phone - SMS (primary) and SMS, attributed to issues at telephony provider Twilio. It started at 2023-05-04 15:05 UTC and was resolved at 2023-05-04 17:42 UTC, lasting 2 h 36 min.

Close reported a major API degradation delaying webhook events from 2023-03-01 13:24 UTC to 2023-03-01 15:39 UTC, lasting 2 h 15 min. A fix was implemented by 14:13 UTC, and the event backlog was fully processed by resolution.

Some users could not log into or load Close’s Application UI in a major incident from 2022-11-08 13:09 UTC to 2022-11-08 16:51 UTC, lasting 3 h 42 min. Close’s postmortem attributed the loading failures to a bad cached application version; a fix was implemented and the incident resolved.