CourtReserve Outage History
9 incidents recorded over the last 365 days, 5 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 CourtReserve Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 15, 2026 | Scheduled System MaintenanceThe scheduled maintenance has been completed. | 50h 0m | Scheduled |
| May 7, 2026 | Database connectivity errors causing service disruptionEverything remains stable as expected. Marking this issue as resolved. Final readout: CourtReserve experienced a service disruption lasting approximately 26 minutes. The cause was an unexpected database connectivity… | 1h 49m | Resolved |
| Mar 24, 2026 | CourtReserve Scheduled Maintenance: March 24, 3:30–4:30 AM ETThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 17, 2026 | CourtReserve Scheduled Maintenance: March 17, 3:30–4:30 AM ETThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Feb 26, 2026 | Network disruptionsBetween 6:20 PM and 7:00 PM Eastern Time on February 26, we experienced a partial service disruption caused by network instability at our hosting data center. The provider later confirmed that their facility was the… | 2h 17m | Resolved |
| Feb 17, 2026 | Outbound Email Campaign Metrics affected by upstream maintenanceThis incident has been resolved. | 13h 22m | Resolved |
| Feb 10, 2026 | CourtReserve maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 27, 2026 | Slowdown due to a database spikeAll systems have remained stable, and the issue is fully resolved. | 1h 14m | Resolved |
| Nov 18, 2025 | Global Cloudflare Network IssuesCloudflare has marked the issue as resolved. All systems continue to be operational. | 7h 52m | 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 CourtReserve 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 CourtReserve 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 CourtReserve 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 CourtReserve outage in this window ran 2d 2h, against a mean recovery of 8h 54m. If you depend on CourtReserve 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.