Pathwright Outage History

Pathwright is up right now

Pathwright had 11 outages in the last 2 years totaling 6h 21m of downtime — averaging 0.5 incidents per month.

There were 11 Pathwright outages since November 27, 2024 totaling 6h 21m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pathwright.com

Major September 4, 2026

Backend Server outage

Detected by Pingoru
Sep 04, 2026, 01:58 AM UTC
Resolved
Sep 04, 2026, 01:58 AM UTC
Duration
41s
Affected: Backend Server
Timeline · 2 updates
  1. investigating Sep 04, 2026, 01:58 AM UTC

    Backend Server cannot be accessed at the moment. This incident was created by an automated monitoring service.

  2. resolved Sep 04, 2026, 01:58 AM UTC

    Backend Server is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Major September 4, 2026

API Server (GraphQL) outage

Detected by Pingoru
Sep 04, 2026, 01:55 AM UTC
Resolved
Sep 04, 2026, 01:59 AM UTC
Duration
4m
Affected: API Server (GraphQL)
Timeline · 2 updates
  1. investigating Sep 04, 2026, 01:55 AM UTC

    API Server (GraphQL) cannot be accessed at the moment. This incident was created by an automated monitoring service.

  2. resolved Sep 04, 2026, 01:59 AM UTC

    API Server (GraphQL) is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Minor September 3, 2026

Some learning spaces are reporting server timeouts while loading path content.

Detected by Pingoru
Sep 03, 2026, 01:30 PM UTC
Resolved
Sep 03, 2026, 07:46 PM UTC
Duration
6h 16m
Affected: Primary ServiceAPI Server (GraphQL)Backend ServerPath App (iOS)
Timeline · 6 updates
  1. investigating Sep 03, 2026, 01:30 PM UTC

    We are currently investigating.

  2. investigating Sep 03, 2026, 02:23 PM UTC

    We are currently investigating this incident.

  3. monitoring Sep 03, 2026, 03:47 PM UTC

    We implemented a fix and are currently monitoring the result.

  4. resolved Sep 03, 2026, 04:04 PM UTC

    This incident has been resolved.

  5. monitoring Sep 03, 2026, 06:44 PM UTC

    We're seeing some more reports of slow load time when accessing some path content. We'll keep you updated as we investigate.

  6. resolved Sep 03, 2026, 07:46 PM UTC

    We've narrowed down the cause of the issue to a feature deploy causing performance issues primarily with Blocks. We reverted the relevant update at 2:30pm EDT and no performance regressions have been indicated since. We apologize for any inconvenience.

Read the full incident report →

Minor September 3, 2026

Issues accessing the Pathwright Platform

Detected by Pingoru
Sep 03, 2026, 01:52 AM UTC
Resolved
Sep 03, 2026, 01:52 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 03, 2026, 01:52 AM UTC

    Type: Incident Duration: 28 minutes Affected Components: Backend Server, Primary Service, API Server (GraphQL), Path App (iOS) Sep 3, 01:52:00 GMT+0 - Investigating - We are currently seeing errors being thrown when attempting to access the Pathwright Platform. We'll keep this page up to date as we investigate. Sep 3, 02:09:00 GMT+0 - Identified - We've identified the issue and are continuing to work on a fix for this incident. Sep 3, 02:09:07 GMT+0 - Monitoring - We discovered that our database began having performance issues due to a storage misconfiguration. We've since resolved the issue and are monitoring to ensure that the Pathwright Platform remains stable while the change propagates. Sep 3, 02:20:07 GMT+0 - Resolved - Database and platform performance has returned to normal. We apologize for any inconvenience.

Read the full incident report →

Minor November 18, 2025

Pathwright platform inaccessible

Detected by Pingoru
Nov 18, 2025, 12:00 PM UTC
Resolved
Nov 18, 2025, 12:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 18, 2025, 12:00 PM UTC

    Type: Incident Duration: 2 hours and 59 minutes Affected Components: Primary Service, API Server (GraphQL), Backend Server, Path App (iOS) Nov 18, 12:00:00 GMT+0 - Identified - One of our providers, Cloudflare, is down: [https://www.cloudflare.com/.](https://www.cloudflare.com/) We are following their status at [https://www.cloudflarestatus.com/.](https://www.cloudflarestatus.com/) Nov 18, 14:36:39 GMT+0 - Monitoring - The Pathwright platform is functional. Nov 18, 14:58:58 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor October 23, 2025

Issue logging into Path App

Detected by Pingoru
Oct 23, 2025, 02:30 PM UTC
Resolved
Oct 23, 2025, 02:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 23, 2025, 02:30 PM UTC

    Type: Incident Duration: 5 hours and 29 minutes Affected Components: Path App (iOS) Oct 23, 19:59:10 GMT+0 - Resolved - This incident has been resolved. We apologize for the down time and will be revisiting the integrations that caused this issue. Oct 23, 14:30:00 GMT+0 - Investigating - We are currently investigating this incident. Current we suspect a 3rd-party change that is preventing Path App users from logging in. We will post more information as we have it. Oct 23, 17:08:38 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.

Read the full incident report →

Minor October 21, 2025

Platform failing to load consistently/correctly.

Detected by Pingoru
Oct 21, 2025, 09:00 PM UTC
Resolved
Oct 21, 2025, 09:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Oct 21, 2025, 09:00 PM UTC

    Type: Incident Duration: 1 hour and 58 minutes Oct 21, 21:00:53 GMT+0 - Investigating - We are currently investigating this incident. Oct 21, 22:31:25 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 21, 22:58:53 GMT+0 - Resolved - This incident has been resolved.

Read the full incident report →

Minor February 1, 2025

API Server (GraphQL) isn't accessible at the moment (automated)

Detected by Pingoru
Feb 01, 2025, 06:54 AM UTC
Resolved
Feb 01, 2025, 06:54 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 01, 2025, 06:54 AM UTC

    Type: Incident Duration: 19 hours and 59 minutes Affected Components: API Server (GraphQL) Feb 1, 07:14:54 GMT+0 - Resolved - API Server (GraphQL) is now operational! This update was created by an automated monitoring service. Feb 1, 06:54:55 GMT+0 - Investigating - API Server (GraphQL) cannot be accessed at the moment. This incident was created by an automated monitoring service.

Read the full incident report →

Minor February 1, 2025

Backend Server isn't accessible at the moment (automated)

Detected by Pingoru
Feb 01, 2025, 06:54 AM UTC
Resolved
Feb 01, 2025, 06:54 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 01, 2025, 06:54 AM UTC

    Type: Incident Duration: 20 hours and 15 minutes Affected Components: Backend Server Feb 1, 06:54:32 GMT+0 - Investigating - Backend Server cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 1, 07:14:46 GMT+0 - Resolved - Backend Server is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Minor November 27, 2024

Elevated load times for discussion posts

Detected by Pingoru
Nov 27, 2024, 12:35 AM UTC
Resolved
Nov 27, 2024, 12:35 AM UTC
Duration
Timeline · 1 update
  1. resolved Nov 27, 2024, 12:35 AM UTC

    Type: Incident Duration: 3 hours and 51 minutes Affected Components: Backend Server, API Server (GraphQL), Primary Service Nov 27, 00:35:28 GMT+0 - Investigating - We're currently experiencing elevated load times across the platform. We'll keep you up to date as we investigate. Nov 27, 01:39:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. We've identified that the main area of the platform affected by this issue appears to be with Discussions which load slowly or fail to load in larger cohorts. We'll update you on this page as we diagnose and fix the issue. Thanks for your patience. Nov 27, 04:26:41 GMT+0 - Resolved - This incident has been resolved. The issue seems to have been caused by a minor fix deployed earlier in the day. Rolling back that deploy resolved the slowdowns with discussion.

Read the full incident report →