Vendor-reported status observed by INTERNETMON
Pinecone status
Pinecone · Atlassian Statuspage
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.
Active incidents
No active incidents were included in this vendor report.
Maintenance
No active or upcoming maintenance was included in this vendor report.
Component health
Reported
26
Retained
26
Affected retained
0
Projection scope: complete · 26 retained of 26 reported components across 2 source groups.
us-west1-gcp
Group: Pod Indexes
Operational
Console
Operational
AWS us-west-2
Group: Serverless Indexes
Operational
us-east1-gcp
Group: Pod Indexes
Operational
AWS us-east-1
Group: Serverless Indexes
Operational
us-central1-gcp
Group: Pod Indexes
Operational
AWS eu-west-1
Group: Serverless Indexes
Operational
us-west4-gcp
Group: Pod Indexes
Operational
Azure eastus2
Group: Serverless Indexes
Operational
us-east4-gcp
Group: Pod Indexes
Operational
GCP us-central1
Group: Serverless Indexes
Operational
us-west1-gcp-free
Group: Pod Indexes
Operational
GCP europe-west4
Group: Serverless Indexes
Operational
us-west4-gcp-free
Group: Pod Indexes
Operational
gcp-starter
Group: Pod Indexes
Operational
eu-west1-gcp
Group: Pod Indexes
Operational
eu-west4-gcp
Group: Pod Indexes
Operational
asia-southeast1-gcp
Group: Pod Indexes
Operational
asia-northeast1-gcp
Group: Pod Indexes
Operational
asia-southeast1-gcp-free
Group: Pod Indexes
Operational
Showing 20 of 26 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.
Recent observed status changes and checkpoints
These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.
Operational
HTTP 200 · 377.11 ms feed latency
Operational
HTTP 200 · 351.55 ms feed latency
Operational
HTTP 200 · 183.64 ms feed latency
Operational
HTTP 200 · 282.16 ms feed latency
Operational
HTTP 200 · 404.42 ms feed latency
Operational
HTTP 200 · 242.18 ms feed latency
Operational
HTTP 200 · 273.58 ms feed latency
Operational
HTTP 200 · 435.27 ms feed latency
Operational
HTTP 200 · 217.78 ms feed latency
Operational
HTTP 200 · 333.33 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
230.22 ms
JSON source