Vendor-reported status observed by INTERNETMON
Twilio Segment status
Twilio Segment · 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
34
Retained
34
Affected retained
0
Projection scope: complete · 34 retained of 34 reported components across 16 source groups.
Data Ingestion (Tracking) API (US)
Group: Data Ingestion (Tracking) API
Operational
Web Interface (US)
Group: Web Interface
Operational
Analytics.js CDN (US)
Group: Analytics.js CDN
Operational
Streaming Destinations (US)
Group: Streaming Destinations
Operational
Cloud Sources (US)
Group: Cloud Sources
Operational
Warehouse Destinations (US)
Group: Warehouses
Operational
Libraries (US)
Group: Libraries
Operational
Engage (US)
Group: Engage
Operational
Data Processing Pipeline (US)
Group: Data Processing Pipeline
Operational
Public API (US)
Group: Public API
Operational
Blobstore Destinations (US)
Group: Blobstore Destinations
Operational
Data Lakes (US)
Group: Data Lakes
Operational
Data Deletions (US)
Group: Data Deletions
Operational
Reverse ETL (EU)
Group: Reverse ETL
Operational
Linked Events (EU)
Group: Linked Events
Operational
Linked Audiences (US)
Group: Linked Audiences
Operational
Data Ingestion (Tracking) API (EU)
Group: Data Ingestion (Tracking) API
Operational
Data Processing Pipeline (EU)
Group: Data Processing Pipeline
Operational
Web Interface (EU)
Group: Web Interface
Operational
Analytics.js CDN (EU)
Group: Analytics.js CDN
Operational
Showing 20 of 34 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 · 125.09 ms feed latency
Operational
HTTP 200 · 259.1 ms feed latency
Operational
HTTP 200 · 199.25 ms feed latency
Operational
HTTP 200 · 237.82 ms feed latency
Operational
HTTP 200 · 220.91 ms feed latency
Operational
HTTP 200 · 167.47 ms feed latency
Operational
HTTP 200 · 101.68 ms feed latency
Operational
HTTP 200 · 388.47 ms feed latency
Operational
HTTP 200 · 328.75 ms feed latency
Operational
HTTP 200 · 265.47 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
275.3 ms
JSON source