Vendor reports: degradedResolved · vendor status “resolved”Official status API

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

Reported by Pinecone · AI & ML · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
Jul 12, 2026, 23:21 UTC
Vendor's clock
Resolved
Jul 13, 2026, 04:15 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
4 h 55 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Pinecone reports degraded: "[Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces".[E1, E2]
  • The vendor marked it resolved at 2026-07-13 04:15 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • Components: AWS us-east-1.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-07-13 04:15 UTC · summary s1, evidence ff31aa418327a5cf

Evidence (7)
  1. E1Pinecone reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "[Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-07-12 23:21 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: AWS us-east-1. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-07-13 04:15 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: AWS us-east-1

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Pinecone is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jul 12, 2026, 23:21 UTCVendor-reported startVendor time
  2. Jul 13, 2026, 04:15 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.

Pinecone: [Serverless][AWS][us-east-1] Increase in freshness lag for some namespaces — statuswall