Pinecone Outage History

Pinecone is up right now

Pinecone had 45 outages in the last 2 years totaling 68h 7m of downtime — averaging 1.8 incidents per month.

There were 45 Pinecone outages since July 16, 2025 totaling 68h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pinecone.io

Critical July 21, 2026

[SERVERLESS][Azure][eastus2] 5xx errors for some namespaces

Detected by Pingoru
Jul 21, 2026, 07:10 PM UTC
Resolved
Jul 21, 2026, 07:40 PM UTC
Duration
29m
Affected: Azure eastus2
Timeline · 3 updates
  1. investigating Jul 21, 2026, 07:38 PM UTC

    We are currently investigating this issue.

  2. identified Jul 21, 2026, 07:39 PM UTC

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

  3. resolved Jul 21, 2026, 08:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 20, 2026

[SERVERLESS][AWS][us-east-1] Increased latency and 5xx errors for some indexes

Detected by Pingoru
Jul 20, 2026, 04:44 PM UTC
Resolved
Jul 20, 2026, 06:00 PM UTC
Duration
1h 15m
Affected: AWS us-east-1
Timeline · 3 updates
  1. investigating Jul 20, 2026, 05:44 PM UTC

    We are currently investigating this issue.

  2. identified Jul 20, 2026, 05:46 PM UTC

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

  3. resolved Jul 20, 2026, 06:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 12, 2026

[Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces

Detected by Pingoru
Jul 12, 2026, 11:21 PM UTC
Resolved
Jul 13, 2026, 04:15 AM UTC
Duration
4h 54m
Affected: AWS us-east-1
Timeline · 3 updates
  1. investigating Jul 12, 2026, 11:21 PM UTC

    We are observing freshness lag affecting a small number of namespaces in AWS us-east-1, resulting in some queries not serving fresh data. We are actively investigating.

  2. identified Jul 12, 2026, 11:46 PM UTC

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

  3. resolved Jul 13, 2026, 01:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 9, 2026

[Serverless][Azure][eastus2] 5xx errors on some requests for some indexes

Detected by Pingoru
Jul 09, 2026, 09:50 AM UTC
Resolved
Jul 09, 2026, 02:37 PM UTC
Duration
4h 47m
Affected: Azure eastus2
Timeline · 3 updates
  1. investigating Jul 09, 2026, 02:36 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 09, 2026, 02:36 PM UTC

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

  3. resolved Jul 09, 2026, 02:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 16, 2026

[Serverless][AWS][us-east-1] Metrics tab in the console not showing graphs

Detected by Pingoru
Jun 16, 2026, 01:05 PM UTC
Resolved
Jun 16, 2026, 05:05 PM UTC
Duration
3h 59m
Affected: AWS us-east-1
Timeline · 3 updates
  1. investigating Jun 16, 2026, 03:37 PM UTC

    We are currently investigating this issue.

  2. identified Jun 16, 2026, 03:42 PM UTC

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

  3. resolved Jun 16, 2026, 05:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 6, 2026

[AWS][us-east-1] 5xx errors for some requests on some indexes

Detected by Pingoru
Jun 06, 2026, 12:48 AM UTC
Resolved
Jun 06, 2026, 01:15 AM UTC
Duration
26m
Affected: AWS us-east-1
Timeline · 5 updates
  1. investigating Jun 06, 2026, 04:48 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 06, 2026, 04:51 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 06, 2026, 04:52 AM UTC

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

  4. monitoring Jun 06, 2026, 04:54 AM UTC

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

  5. resolved Jun 06, 2026, 04:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 25, 2026

[Serverless][AWS][us-west-2] 5xx errors and longer response times on upsert requests for some indexes.

Detected by Pingoru
May 25, 2026, 01:41 PM UTC
Resolved
May 25, 2026, 03:00 PM UTC
Duration
1h 18m
Affected: AWS us-west-2
Timeline · 4 updates
  1. investigating May 25, 2026, 06:00 PM UTC

    We are currently investigating this issue.

  2. identified May 25, 2026, 06:02 PM UTC

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

  3. monitoring May 25, 2026, 06:02 PM UTC

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

  4. resolved May 25, 2026, 06:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 13, 2026

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

Detected by Pingoru
May 13, 2026, 08:14 PM UTC
Resolved
May 13, 2026, 09:15 PM UTC
Duration
1h 1m
Affected: AWS us-east-1
Timeline · 3 updates
  1. investigating May 13, 2026, 09:19 PM UTC

    We are currently investigating this issue.

  2. identified May 13, 2026, 09:22 PM UTC

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

  3. resolved May 14, 2026, 12:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2026

Pinecone Console loading slowly for some users

Detected by Pingoru
May 06, 2026, 03:00 PM UTC
Resolved
May 06, 2026, 03:20 PM UTC
Duration
19m
Affected: Console
Timeline · 3 updates
  1. investigating May 06, 2026, 06:18 PM UTC

    We are currently investigating this issue.

  2. monitoring May 06, 2026, 06:20 PM UTC

    The hosting provider for app.pinecone.io experienced increased errors and latency starting at 15:00 UTC. At 15:15 UTC, they implemented a fix and are continuing to monitor the impact. This incident did not impact Pinecone APIs or services.

  3. resolved May 06, 2026, 06:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 13, 2026

[GCP][europe-west4] Errors for upsert operations on some indexes

Detected by Pingoru
Mar 13, 2026, 08:50 AM UTC
Resolved
Mar 13, 2026, 09:53 AM UTC
Duration
1h 3m
Affected: GCP europe-west4
Timeline · 3 updates
  1. investigating Mar 13, 2026, 02:06 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 13, 2026, 02:08 PM UTC

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

  3. resolved Mar 13, 2026, 02:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 5, 2026

[AWS][us-east-1] Prometheus metrics are unavailable through the Pinecone console or the metric proxy

Detected by Pingoru
Mar 05, 2026, 09:57 PM UTC
Resolved
Mar 05, 2026, 11:02 PM UTC
Duration
1h 4m
Affected: AWS us-east-1
Timeline · 3 updates
  1. investigating Mar 05, 2026, 11:00 PM UTC

    We are currently investigating this issue.

  2. identified Mar 05, 2026, 11:01 PM UTC

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

  3. resolved Mar 05, 2026, 11:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 4, 2026

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

Detected by Pingoru
Mar 04, 2026, 09:06 PM UTC
Resolved
Mar 04, 2026, 10:16 PM UTC
Duration
1h 10m
Affected: GCP us-central1
Timeline · 3 updates
  1. investigating Mar 04, 2026, 10:05 PM UTC

    We are currently investigating this issue.

  2. monitoring Mar 04, 2026, 10:22 PM UTC

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

  3. resolved Mar 04, 2026, 10:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 23, 2026

[GCP][us-central1][europe-west4] Errors on some read operations

Detected by Pingoru
Feb 23, 2026, 11:14 PM UTC
Resolved
Feb 24, 2026, 01:52 AM UTC
Duration
2h 38m
Affected: GCP us-central1GCP europe-west4
Timeline · 4 updates
  1. investigating Feb 24, 2026, 01:01 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 24, 2026, 01:08 AM UTC

    The impact was related to a Google Cloud Storage incident (Event ID: WDVVRMB).

  3. identified Feb 24, 2026, 01:39 AM UTC

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

  4. resolved Feb 24, 2026, 02:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 15, 2026

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

Detected by Pingoru
Jan 15, 2026, 12:12 PM UTC
Resolved
Jan 15, 2026, 03:30 PM UTC
Duration
3h 18m
Affected: AWS us-east-1
Timeline · 4 updates
  1. investigating Jan 15, 2026, 02:33 PM UTC

    We are currently investigating this issue.

  2. identified Jan 15, 2026, 03:18 PM UTC

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

  3. monitoring Jan 15, 2026, 03:18 PM UTC

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

  4. resolved Jan 15, 2026, 06:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 2, 2026

Intermittent unavailability across all environments for some indexes

Detected by Pingoru
Jan 02, 2026, 04:31 PM UTC
Resolved
Jan 02, 2026, 05:58 PM UTC
Duration
1h 26m
Affected: us-west1-gcpConsoleAWS us-west-2us-east1-gcpAWS us-east-1us-central1-gcpAWS eu-west-1us-west4-gcpAzure eastus2us-east4-gcpGCP us-central1us-west1-gcp-freeGCP europe-west4us-west4-gcp-freegcp-startereu-west1-gcpeu-west4-gcpasia-southeast1-gcpasia-northeast1-gcpasia-southeast1-gcp-freeIndex Managementnorthamerica-northeast1-gcpInferenceeastus-azureAssistantus-east-1-aws
Timeline · 3 updates
  1. investigating Jan 02, 2026, 04:31 PM UTC

    We are currently investigating this issue.

  2. monitoring Jan 02, 2026, 05:18 PM UTC

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

  3. resolved Jan 02, 2026, 05:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 31, 2025

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

Detected by Pingoru
Dec 31, 2025, 03:13 AM UTC
Resolved
Dec 31, 2025, 03:29 AM UTC
Duration
16m
Affected: AWS us-west-2
Timeline · 4 updates
  1. investigating Dec 31, 2025, 02:27 PM UTC

    We are currently investigating this issue.

  2. identified Dec 31, 2025, 02:29 PM UTC

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

  3. monitoring Dec 31, 2025, 02:30 PM UTC

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

  4. resolved Dec 31, 2025, 02:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 15, 2025

[Serverless][GCP][europe-west4] 5xx errors on read and write operations for some indexes

Detected by Pingoru
Dec 15, 2025, 10:39 AM UTC
Resolved
Dec 15, 2025, 10:02 PM UTC
Duration
11h 22m
Affected: GCP europe-west4
Timeline · 4 updates
  1. investigating Dec 15, 2025, 12:54 PM UTC

    We are currently investigating this issue.

  2. identified Dec 15, 2025, 02:34 PM UTC

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

  3. monitoring Dec 15, 2025, 09:20 PM UTC

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

  4. resolved Dec 15, 2025, 10:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2025

Increased file processing time for Assistant

Detected by Pingoru
Dec 09, 2025, 08:15 PM UTC
Resolved
Dec 10, 2025, 01:50 AM UTC
Duration
5h 35m
Affected: Assistant
Timeline · 4 updates
  1. investigating Dec 10, 2025, 03:37 AM UTC

    Files uploaded to an assistant may take longer than expected to appear in chat and context requests during this time.

  2. identified Dec 10, 2025, 03:38 AM UTC

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

  3. monitoring Dec 10, 2025, 03:38 AM UTC

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

  4. resolved Dec 10, 2025, 03:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 5, 2025

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

Detected by Pingoru
Dec 05, 2025, 06:36 PM UTC
Resolved
Dec 05, 2025, 08:42 PM UTC
Duration
2h 6m
Affected: GCP us-central1
Timeline · 4 updates
  1. investigating Dec 05, 2025, 07:53 PM UTC

    We are currently investigating this issue.

  2. identified Dec 05, 2025, 07:56 PM UTC

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

  3. monitoring Dec 05, 2025, 09:26 PM UTC

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

  4. resolved Dec 05, 2025, 09:26 PM UTC

    This incident has been resolved.

Read the full incident report →