FareHarbor incident

Fareharbor is experiencing errors with loading certain functionalities

Major Resolved View vendor source →

FareHarbor experienced a major incident on January 29, 2025, lasting 1h 7m. The incident has been resolved; the full update timeline is below.

Started
Jan 29, 2025, 05:31 PM UTC
Resolved
Jan 29, 2025, 06:38 PM UTC
Duration
1h 7m
Detected by Pingoru
Jan 29, 2025, 05:31 PM UTC

Update timeline

  1. investigating Jan 29, 2025, 05:31 PM UTC

    We are aware that some users may be experiencing errors with loading certain functionalities. Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide updates here as more information becomes available. We apologize for any inconvenience and appreciate your patience.

  2. investigating Jan 29, 2025, 05:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jan 29, 2025, 06:05 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Jan 29, 2025, 06:11 PM UTC

    We've implemented a solution and are seeing performance return to normal. We're continuing to closely watch and make sure this issue is fully resolved.

  5. resolved Jan 29, 2025, 06:38 PM UTC

    This incident has been resolved and we're seeing normal performance across the site. Our apologies for the disruption!