Pax8 Outage History

Pax8 is up right now

Pax8 had 35 outages in the last 2 years totaling 82h 52m of downtime — averaging 1.4 incidents per month.

There were 35 Pax8 outages since June 15, 2024 totaling 82h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pax8.com

Major October 23, 2024

Partial Outage - Platform Search Records

Detected by Pingoru
Oct 23, 2024, 07:32 PM UTC
Resolved
Oct 24, 2024, 03:50 AM UTC
Duration
8h 18m
Affected: Pax8 Platform
Timeline · 3 updates
  1. identified Oct 23, 2024, 07:32 PM UTC

    We have identified a partial outage in search in the Marketplace impacting all users. Search records are streaming in. We will continue to post updates here.

  2. monitoring Oct 23, 2024, 11:12 PM UTC

    Pax8 Marketplace search results continue to stream back in. We'll notify when search is operating normally.

  3. resolved Oct 24, 2024, 03:50 AM UTC

    Pax8 Marketplace search is operating normally. This incident has been resolved.

Read the full incident report →

Minor October 23, 2024

Application Slowness

Detected by Pingoru
Oct 23, 2024, 02:45 PM UTC
Resolved
Oct 23, 2024, 04:41 PM UTC
Duration
1h 56m
Affected: Pax8 Platform
Timeline · 2 updates
  1. identified Oct 23, 2024, 02:45 PM UTC

    We are currently investigating degraded features in the platform impacting all users. We are also aware of a brief disruption in service due to an infrastructure configuration change. We are monitoring the Marketplace performance and will continue to post updates here.

  2. resolved Oct 23, 2024, 04:41 PM UTC

    A fix has been implemented. This incident has been resolved.

Read the full incident report →

Critical October 22, 2024

Inc-264

Detected by Pingoru
Oct 22, 2024, 08:03 PM UTC
Resolved
Oct 22, 2024, 10:13 PM UTC
Duration
2h 9m
Affected: Catalog
Timeline · 5 updates
  1. investigating Oct 22, 2024, 08:03 PM UTC

    The Marketplace Catalog is currently down. We have identified the issue and are testing and deploying the solution. We will continue to post updates here.

  2. identified Oct 22, 2024, 08:04 PM UTC

    We have identified the issue as related to pricing and are testing and deploying the solution.

  3. monitoring Oct 22, 2024, 08:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Oct 22, 2024, 08:37 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 22, 2024, 10:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 9, 2024

Partial Service Disruption

Detected by Pingoru
Oct 09, 2024, 10:16 PM UTC
Resolved
Oct 10, 2024, 03:26 PM UTC
Duration
17h 10m
Affected: Pax8 PlatformCatalogSubscriptions
Timeline · 3 updates
  1. identified Oct 09, 2024, 10:16 PM UTC

    We are experiencing an issue that affects several services, including the catalog search functionality, sign-up, quoting, and the subscription page. Our Engineering team is actively investigating the problem and working to restore full functionality as soon as possible.

  2. monitoring Oct 09, 2024, 10:35 PM UTC

    The Catalog Search, Sign-up, Quoting, and Subscription Page issue has been resolved, and services are now online. We are currently monitoring the system to ensure stability and continued functionality.

  3. resolved Oct 10, 2024, 03:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 14, 2024

SentinelOne Outage

Detected by Pingoru
Sep 14, 2024, 08:22 PM UTC
Resolved
Sep 14, 2024, 11:37 PM UTC
Duration
3h 15m
Affected: Subscriptions
Timeline · 2 updates
  1. investigating Sep 14, 2024, 08:22 PM UTC

    Pax8 is aware of an ongoing SentinelOne outage that is impacting all global users. Pax8 has an open support incident with SentinelOne and will update partners via open Pax8 support cases and additional service alerts as new information becomes available.

  2. resolved Sep 14, 2024, 11:37 PM UTC

    The SentinelOne outage has been resolved. Partners with SentinelOne subscriptions can find more details and instructions in their Pax8 Marketplace Inbox.

Read the full incident report →

Major August 26, 2024

Partial Support System Degradation

Detected by Pingoru
Aug 26, 2024, 08:18 PM UTC
Resolved
Aug 26, 2024, 11:08 PM UTC
Duration
2h 50m
Affected: Support
Timeline · 3 updates
  1. monitoring Aug 26, 2024, 08:18 PM UTC

    We are experiencing partial degradation of our support system, affecting ticket responses. You may encounter some delays as we work to resolve the issue and fully restore normal operations. We apologize for any inconvenience and appreciate your patience during this time.

  2. identified Aug 26, 2024, 08:19 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Aug 26, 2024, 11:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 6, 2024

Degraded Feature [Catalog Search]

Detected by Pingoru
Aug 06, 2024, 07:54 PM UTC
Resolved
Aug 07, 2024, 01:26 PM UTC
Duration
17h 31m
Affected: Catalog
Timeline · 3 updates
  1. investigating Aug 06, 2024, 07:54 PM UTC

    We are aware that the fix for the previous Catalog incident did not fully resolve the issue for all users. We are once again investigating how to resolve this issue for all users. We will continue to update our status page here with any progress. Thank you again for your patience.

  2. monitoring Aug 06, 2024, 10:00 PM UTC

    We have implemented a fix for this incident. The majority of active cases should now be resolved with few cases of this issue resolving over time. We should see all cases of this issue resolved overnight. Thank you again for your patience during this outage. We will continue to monitor for open cases after an overnight process has completed.

  3. resolved Aug 07, 2024, 01:26 PM UTC

    After monitoring this issue for some time, this issue appears to be fully resolved. If you are a user continuing to experience issues with the Pax8 catalog, please contact our support team. This issue is being resolved and closed. Thank you once again for your patience during this outage.

Read the full incident report →

Minor June 28, 2024

P3 - Degraded Feature [Client Creation]

Detected by Pingoru
Jun 28, 2024, 01:06 PM UTC
Resolved
Jun 28, 2024, 02:42 PM UTC
Duration
1h 35m
Affected: Pax8 Platform
Timeline · 3 updates
  1. investigating Jun 28, 2024, 01:06 PM UTC

    We are currently investigating a degraded feature preventing some users from creating new clients in the platform. We will continue to post updates here.

  2. identified Jun 28, 2024, 01:37 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jun 28, 2024, 02:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 25, 2024

Pax8 Email Communication Impacted

Detected by Pingoru
Jun 25, 2024, 10:33 PM UTC
Resolved
Jun 27, 2024, 02:07 AM UTC
Duration
1d 3h
Affected: Pax8 Platform
Timeline · 4 updates
  1. monitoring Jun 25, 2024, 10:33 PM UTC

    There was an issue preventing certain email communications from Pax8 being sent. Email communication has been restored as of 3:45 MT and the team is actively working on resending affected communications.

  2. monitoring Jun 26, 2024, 12:53 PM UTC

    We are continuing to work on resending affected communications.

  3. monitoring Jun 26, 2024, 05:39 PM UTC

    Affected email communications are in the process of being resent. A further update will be posted once the process is complete.

  4. resolved Jun 27, 2024, 02:07 AM UTC

    This incident has been resolved. Any remaining affected emails will be resolved within the coming days.

Read the full incident report →

Minor June 15, 2024

P2 - Application Slowness

Detected by Pingoru
Jun 15, 2024, 03:21 PM UTC
Resolved
Jun 15, 2024, 03:53 PM UTC
Duration
32m
Affected: Pax8 Platform
Timeline · 2 updates
  1. investigating Jun 15, 2024, 03:21 PM UTC

    We are currently investigating application slowness impacting all users. We will continue to post updates here.

  2. resolved Jun 15, 2024, 03:53 PM UTC

    This incident has been resolved.

Read the full incident report →