RudderStack · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

RudderStack status

RudderStack · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
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

Scheduled Database Upgrade and Maintenance

We will be undergoing scheduled maintenance on 2026-09-21, 05:30 UTC – 06:30 UTC. During this window, the web application and public API will be briefly unavailable for approximately 2–3 minutes. Customers will not be able to view or update workspace configuration during that time. Event ingestion will continue as normal and will not be impacted. No data loss is expected. We apologize for any inconvenience this may cause and appreciate your understanding as we work to enhance the performance and reliability of our systems. Should you have any questions, please reach out to support.

Status scheduled Starts Ends Updated

Component health

Reported
12
Retained
12
Affected retained
0
Projection scope: complete · 12 retained of 12 reported components across 2 source groups.
Data Ingestion (US) Group: Data Ingestion Operational
Data Processing Pipeline (US) Group: Data Processing Pipeline Operational
Data Ingestion (EU) Group: Data Ingestion Operational
Data Processing Pipeline (EU) Group: Data Processing Pipeline Operational
Warehouses Operational
Data Ingestion (IN) Group: Data Ingestion Operational
Data Processing Pipeline (IN) Group: Data Processing Pipeline Operational
Control Plane / Public API Operational
Web Application Operational
rETL Pipeline Operational
ETL Pipelines Operational
Integrations Operational

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 · 334.67 ms feed latency
Operational
HTTP 200 · 396.64 ms feed latency
Operational
HTTP 200 · 86.11 ms feed latency
Operational
HTTP 200 · 399.68 ms feed latency
Operational
HTTP 200 · 278.9 ms feed latency
Operational
HTTP 200 · 318.85 ms feed latency
Operational
HTTP 200 · 219.58 ms feed latency
Operational
HTTP 200 · 380.17 ms feed latency
Operational
HTTP 200 · 456.25 ms feed latency
Operational
HTTP 200 · 352.98 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
427.76 ms