Carrot Outage History
8 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Carrot Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 14, 2026 | Maintenance windowScheduled maintenance is currently in progress. We will provide updates as necessary. | 3h 0m | Scheduled |
| Jul 17, 2026 | Maintenance windowThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Apr 17, 2026 | Maintenance windowThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Jan 29, 2026 | User account dasbhoardThis incident has been resolved. | 15 min | Resolved |
| Jan 24, 2026 | Carrot CRM Integration OfflineThis has been validated as resolved for new incoming form submissions | 16 min | Resolved |
| Jan 10, 2026 | Maintenance windowThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jan 9, 2026 | Maintenance windowThe scheduled maintenance has been completed. | 7h 0m | Scheduled |
| Nov 18, 2025 | Sales site outageThis incident has been resolved. | 17 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Carrot incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Carrot Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Carrot acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Carrot outage in this window ran 8h, against a mean recovery of 3h 14m. If you depend on Carrot in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.