Pinecone Outage History

Pinecone is up right now

Pinecone had 42 outages in the last 2 years totaling 184h 54m of downtime — averaging 1.7 incidents per month.

There were 42 Pinecone outages since June 17, 2025 totaling 184h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pinecone.io

Major October 23, 2025

[Serverless][GCP][us-central1] 5xx errors on some read and write operations

Detected by Pingoru
Oct 23, 2025, 05:32 PM UTC
Resolved
Oct 23, 2025, 06:23 PM UTC
Duration
51m
Affected: GCP us-central1
Timeline · 4 updates
  1. investigating Oct 23, 2025, 05:44 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 23, 2025, 05:44 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Oct 23, 2025, 05:45 PM UTC

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

  4. resolved Oct 23, 2025, 06:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 21, 2025

[Serverless][Azure][eastus2] 5xx errors on some read and write operations

Detected by Pingoru
Oct 21, 2025, 05:57 PM UTC
Resolved
Oct 21, 2025, 07:24 PM UTC
Duration
1h 26m
Affected: Azure eastus2
Timeline · 4 updates
  1. investigating Oct 21, 2025, 06:09 PM UTC

    We are currently investigating this issue.

  2. identified Oct 21, 2025, 06:50 PM UTC

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

  3. monitoring Oct 21, 2025, 07:06 PM UTC

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

  4. resolved Oct 21, 2025, 07:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 21, 2025

Some users may be unable to access the Pinecone web console. All API services remain fully operational.

Detected by Pingoru
Oct 21, 2025, 01:27 AM UTC
Resolved
Oct 21, 2025, 03:30 AM UTC
Duration
2h 3m
Affected: Console
Timeline · 3 updates
  1. investigating Oct 21, 2025, 01:46 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 21, 2025, 03:07 AM UTC

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

  3. resolved Oct 21, 2025, 01:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 10, 2025

[Serverless][AWS][us-east-1] 5xx errors on some read and write operations

Detected by Pingoru
Sep 10, 2025, 01:16 PM UTC
Resolved
Sep 10, 2025, 04:38 PM UTC
Duration
3h 21m
Affected: AWS us-east-1
Timeline · 3 updates
  1. investigating Sep 10, 2025, 01:32 PM UTC

    We are currently investigating this issue.

  2. monitoring Sep 10, 2025, 02:54 PM UTC

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

  3. resolved Sep 10, 2025, 04:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 10, 2025

[Serverless][AWS][us-west-2] 5xx errors on some read operations

Detected by Pingoru
Sep 10, 2025, 12:52 PM UTC
Resolved
Sep 10, 2025, 05:22 PM UTC
Duration
4h 30m
Affected: AWS us-west-2
Timeline · 3 updates
  1. investigating Sep 10, 2025, 01:30 PM UTC

    We are currently investigating this issue.

  2. monitoring Sep 10, 2025, 02:55 PM UTC

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

  3. resolved Sep 10, 2025, 06:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 9, 2025

[Serverless][AWS][us-east-1] 5xx errors on write operations for some indexes

Detected by Pingoru
Sep 09, 2025, 12:55 PM UTC
Resolved
Sep 09, 2025, 02:40 PM UTC
Duration
1h 44m
Affected: AWS us-east-1
Timeline · 3 updates
  1. investigating Sep 09, 2025, 01:31 PM UTC

    We are currently investigating this issue.

  2. monitoring Sep 09, 2025, 01:57 PM UTC

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

  3. resolved Sep 09, 2025, 02:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 29, 2025

Console stuck loading after login for some users

Detected by Pingoru
Aug 29, 2025, 08:28 PM UTC
Resolved
Aug 29, 2025, 10:42 PM UTC
Duration
2h 13m
Affected: Console
Timeline · 3 updates
  1. investigating Aug 29, 2025, 08:28 PM UTC

    We are investigating an issue where some users are unable to access the console after logging in. Affected users may see the console stuck in a loading state. The issue is related to elevated errors from our authentication provider.

  2. monitoring Aug 29, 2025, 09:13 PM UTC

    The loading issue has recovered, and we are continuing to monitor.

  3. resolved Aug 29, 2025, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 28, 2025

[Serverless][AWS][us-west-2] Unavailability for some read path operations for some indexes

Detected by Pingoru
Aug 28, 2025, 06:30 PM UTC
Resolved
Aug 28, 2025, 08:25 PM UTC
Duration
1h 54m
Affected: AWS us-west-2
Timeline · 3 updates
  1. investigating Aug 28, 2025, 08:57 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 28, 2025, 08:58 PM UTC

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

  3. resolved Aug 28, 2025, 09:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 26, 2025

[Serverless][GCP][europe-west4] Indexing lag on some indexes; recent writes may not appear in reads

Detected by Pingoru
Aug 26, 2025, 01:22 PM UTC
Resolved
Aug 26, 2025, 03:05 PM UTC
Duration
1h 42m
Affected: GCP europe-west4
Timeline · 3 updates
  1. investigating Aug 26, 2025, 02:04 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 26, 2025, 02:26 PM UTC

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

  3. resolved Aug 26, 2025, 05:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 5, 2025

[Serverless][AWS][us-west-2] Unavailability for some read path operations

Detected by Pingoru
Aug 05, 2025, 04:17 PM UTC
Resolved
Aug 05, 2025, 05:23 PM UTC
Duration
1h 5m
Affected: AWS us-west-2
Timeline · 3 updates
  1. investigating Aug 05, 2025, 04:58 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 05, 2025, 05:29 PM UTC

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

  3. resolved Aug 05, 2025, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 1, 2025

[Serverless][AWS][us-east-1] Unavailability for some read path operations

Detected by Pingoru
Aug 01, 2025, 02:22 PM UTC
Resolved
Aug 01, 2025, 07:46 PM UTC
Duration
5h 23m
Affected: AWS us-east-1
Timeline · 5 updates
  1. investigating Aug 01, 2025, 02:48 PM UTC

    We are currently investigating this issue.

  2. identified Aug 01, 2025, 02:49 PM UTC

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

  3. identified Aug 01, 2025, 03:40 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Aug 01, 2025, 07:13 PM UTC

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

  5. resolved Aug 01, 2025, 09:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 31, 2025

[Serverless][GCP][us-central1] 5xx errors on read operations for some indexes

Detected by Pingoru
Jul 31, 2025, 10:16 PM UTC
Resolved
Aug 01, 2025, 02:56 PM UTC
Duration
16h 39m
Affected: GCP us-central1
Timeline · 4 updates
  1. investigating Jul 31, 2025, 11:14 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 31, 2025, 11:15 PM UTC

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

  3. monitoring Aug 01, 2025, 01:40 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Aug 01, 2025, 02:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 31, 2025

[Serverless][AWS][us-east-1][eu-west-1] Unavailability for some read and write path operations

Detected by Pingoru
Jul 31, 2025, 09:42 AM UTC
Resolved
Aug 01, 2025, 02:56 PM UTC
Duration
1d 5h
Affected: AWS us-east-1AWS eu-west-1
Timeline · 3 updates
  1. investigating Jul 31, 2025, 02:48 PM UTC

    We are currently experiencing a service disruption due to what appears to be networking issues in our AWS us-east-1 and eu-west-1 regions. Our database team is working to identify the root cause and implement a solution.

  2. monitoring Jul 31, 2025, 02:50 PM UTC

    The error condition has been resolved. We are still working to identify the root cause. We are currently monitoring the situation and will have further updates available soon.

  3. resolved Aug 01, 2025, 02:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 16, 2025

Read units not included in API response for query, list, and fetch operations on serverless indexes

Detected by Pingoru
Jul 16, 2025, 07:27 PM UTC
Resolved
Jul 21, 2025, 10:58 AM UTC
Duration
4d 15h
Affected: AWS us-west-2AWS us-east-1AWS eu-west-1Azure eastus2GCP us-central1GCP europe-west4
Timeline · 2 updates
  1. investigating Jul 21, 2025, 10:37 PM UTC

    We are currently investigating this issue.

  2. resolved Jul 22, 2025, 12:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 24, 2025

[Serverless][AWS][eu-west-1] 5xx errors on read operations for some indexes

Detected by Pingoru
Jun 24, 2025, 12:26 AM UTC
Resolved
Jun 24, 2025, 12:57 AM UTC
Duration
31m
Affected: AWS eu-west-1
Timeline · 3 updates
  1. investigating Jun 24, 2025, 01:16 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 24, 2025, 01:16 AM UTC

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

  3. resolved Jun 24, 2025, 02:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 17, 2025

[Serverless][Azure][eastus2] 5xx errors on some read path operations

Detected by Pingoru
Jun 17, 2025, 01:22 PM UTC
Resolved
Jun 17, 2025, 01:58 PM UTC
Duration
35m
Affected: Azure eastus2
Timeline · 3 updates
  1. investigating Jun 17, 2025, 01:37 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 17, 2025, 01:38 PM UTC

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

  3. resolved Jun 17, 2025, 03:32 PM UTC

    This incident has been resolved.

Read the full incident report →