Skip to main content
down.guideby Sazabi
Providers
Is Close down? · Workplace

Close is up

OperationalNo known problems: Close's status page says operational

99.99% uptime, 90 days · 99.99% over 12 monthsLast incident Checked Official status pageHistory

Reports count in aggregate against normal levels; one alone never makes a claim.

Now

Open incidents

What Close has posted and not resolved.

Close has no open incidents.

90 days

Daily history

Worst impact each day, from the provider's own incidents.

  1. 2026-08-09: no incidents
  2. 2026-08-10: no incidents
  3. 2026-08-11: 2 incidents, worst partial outage
  4. 2026-08-12: no incidents
  5. 2026-08-13: no incidents
  6. 2026-08-14: no incidents
  7. 2026-08-15: no incidents
  8. 2026-08-16: no incidents
  9. 2026-08-17: no incidents
  10. 2026-08-18: no incidents
  11. 2026-08-19: no incidents
  12. 2026-08-20: no incidents
  13. 2026-08-21: no incidents
  14. 2026-08-22: no incidents
  15. 2026-08-23: no incidents
  16. 2026-08-24: no incidents
  17. 2026-08-25: no incidents
  18. 2026-08-26: no incidents
  19. 2026-08-27: no incidents
  20. 2026-08-28: no incidents
  21. 2026-08-29: no incidents
  22. 2026-08-30: no incidents
  23. 2026-08-31: no incidents
  24. 2026-09-01: no incidents
  25. 2026-09-02: no incidents
  26. 2026-09-03: no incidents
  27. 2026-09-04: no incidents
  28. 2026-09-05: no incidents
  29. 2026-09-06: no incidents
  30. 2026-09-07: no incidents
  31. 2026-09-08: no incidents
  32. 2026-09-09: no incidents
  33. 2026-09-10: no incidents
  34. 2026-09-11: no incidents
  35. 2026-09-12: no incidents
  36. 2026-09-13: no incidents
  37. 2026-09-14: no incidents
  38. 2026-09-15: no incidents
  39. 2026-09-16: no incidents
  40. 2026-09-17: no incidents
  41. 2026-09-18: no incidents
  42. 2026-09-19: no incidents
  43. 2026-09-20: no incidents
  44. 2026-09-21: no incidents
  45. 2026-09-22: no incidents
  46. 2026-09-23: no incidents
  47. 2026-09-24: no incidents
  48. 2026-09-25: no incidents
  49. 2026-09-26: no incidents
  50. 2026-09-27: no incidents
  51. 2026-09-28: no incidents
  52. 2026-09-29: 1 incident, worst partial outage
  53. 2026-09-30: no incidents
  54. 2026-10-01: no incidents
  55. 2026-10-02: no incidents
  56. 2026-10-03: no incidents
  57. 2026-10-04: no incidents
  58. 2026-10-05: no incidents
  59. 2026-10-06: no incidents
  60. 2026-10-07: no incidents
  61. 2026-10-08: no incidents
  62. 2026-10-09: no incidents
  63. 2026-10-10: no incidents
  64. 2026-10-11: no incidents
  65. 2026-10-12: no incidents
  66. 2026-10-13: no incidents
  67. 2026-10-14: no incidents
  68. 2026-10-15: no incidents
  69. 2026-10-16: no incidents
  70. 2026-10-17: no incidents
  71. 2026-10-18: no incidents
  72. 2026-10-19: no incidents
  73. 2026-10-20: no incidents
  74. 2026-10-21: no incidents
  75. 2026-10-22: no incidents
  76. 2026-10-23: no incidents
  77. 2026-10-24: no incidents
  78. 2026-10-25: no incidents
  79. 2026-10-26: no incidents
  80. 2026-10-27: no incidents
  81. 2026-10-28: 1 incident, worst major outage
  82. 2026-10-29: no incidents
  83. 2026-10-30: no incidents
  84. 2026-10-31: no incidents
  85. 2026-11-01: no incidents
  86. 2026-11-02: no incidents
  87. 2026-11-03: no incidents
  88. 2026-11-04: no incidents
  89. 2026-11-05: no incidents
  90. 2026-11-06: no incidents
90 days agoToday
Reliability

Last 90 days in numbers

From the provider's own posts, including history read from its archive.

Uptime
99.99%12 months
Incidents
4on 3 days
Median duration
44m
Longest
2h 3m
Postmortem rate
0%partial and major outages
Reports

People reporting problems

Hourly counts, last 24 hours.

No reports in the last 24 hours.

Follow Close incidents

Following several providers? Check your stack to get one feed for all of them.

https://down.guide/feed?provider=close
Open feed

In Slack, install the RSS app and run /feed subscribe https://down.guide/feed?provider=close in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.

https://down.guide/feed?provider=close&format=atom
Open feed

The same entries as Atom, for readers that prefer it.

https://down.guide/feed?provider=close&format=json
Open feed

The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.

History

Recent incidents

The last 90 days.

All history
  1. CloseMajor outage
    App is unavailable for some customers
    lasted 29mApplication UI, API
  2. ClosePartial outagePostmortem
    Application impairment
    lasted 26mApplication UI
  3. ClosePartial outage
    Database Failures
    lasted 2h 3mus
  4. ClosePartial outage
    Database Failures
    lasted 59mApplication UI, API

Close status: questions

Is Close down right now?

No known problems: Close's status page says operational (checked 2026-11-06 17:58 UTC from Close's official status page).

What is Close's uptime?

99.99% over the last 90 days and 99.99% over 12 months, from the incidents Close posted on its own status page. A major outage counts in full and a partial outage as 30% of its time, per component.

When was Close's last outage?

App is unavailable for some customers, starting 2026-10-28 17:41 UTC and lasting 29m: https://down.guide/close/DWN-4ccda523c3

How do I get alerts when Close goes down?

Subscribe to https://down.guide/feed?provider=close (RSS; add format=atom or format=json). In Slack, install the RSS app and run /feed subscribe with that URL; in Discord, give it to a feed bot such as MonitoRSS. No account needed.

Where does down.guide get Close's status?

From Close's official status page, https://status.close.com, read every minute. Close's words are quoted verbatim and linked.