FareHarbor Outage History

15 incidents recorded over the last 365 days, 13 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.

Live FareHarbor status100.00% uptime history

Every Recorded FareHarbor Incident

FareHarbor incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 26, 2026Issue collection Online PaymentsThis incident has been resolved.45 minResolved
Aug 26, 2026Issues collecting payments.This incident has been resolved.10 minResolved
Aug 16, 2026Identified availability creation issueThis incident has been resolved.1h 13mResolved
Jul 16, 2026Due to an outage affecting our upstream provider, AWS, some FareHarbor services are currently impacted.This incident has been resolved.2h 36mResolved
Jul 2, 2026Dashboard Performance IssuesThis incident has been resolved.47 minResolved
Jun 22, 2026Resolved Dashboard SlownessThis incident has been resolved and we're seeing normal performance across the site. Our apologies for the disruption!-80 minResolved
Jun 15, 2026We are currently experiencing delays in processing email notificationsThis incident has been resolved.1h 22mResolved
Jun 9, 2026We are currently experiencing an issue affecting some redirect-based online payment methodsThis incident has been resolved.49 minResolved
Jun 1, 2026Photo Upload IssuesThis incident has been resolved.2h 24mResolved
May 22, 2026Fareharbor is experiencing slowness issues.This incident has been resolved.17 minResolved
Feb 28, 2026Limited FareHarbor FunctionalityThe scheduled maintenance has been completed.30 minScheduled
Feb 28, 2026February 2026 Planned System MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 17, 2026Image Upload IssueThis incident has been resolved and we're seeing normal performance across the site. Our apologies for the disruption!1h 10mResolved
Dec 5, 2025Monitoring potential impact due to Cloudflare outageThis incident has been resolved.3h 22mResolved
Nov 18, 2025Monitoring potential impact due to Cloudflare outageThis incident has been resolved.6h 26mResolved

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 FareHarbor 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 FareHarbor 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 FareHarbor 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 FareHarbor outage in this window ran 6h 26m, against a mean recovery of 1h 38m. If you depend on FareHarbor 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.