Vendor-reported status observed by INTERNETMON
SentinelOne status
SentinelOne · 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
54
Retained
54
Affected retained
0
Projection scope: complete · 54 retained of 54 reported components across 6 source groups.
USA (NA1)
Group: Platform Features
Operational
USA (NA1)
Group: AI SIEM (Data)
Operational
USA (NA1)
Group: Singularity Threat Services
Operational
USA (NA1)
Group: Endpoint Security
Operational
USA (NA1)
Group: Cloud Security
Operational
USA (NA1)
Group: Singularity Operations Center and Management Console
Operational
USA (NA4)
Group: Endpoint Security
Operational
USA (NA4)
Group: Singularity Threat Services
Operational
USA (NA4)
Group: Singularity Operations Center and Management Console
Operational
USA (NA4)
Group: AI SIEM (Data)
Operational
USA (NA4)
Group: Platform Features
Operational
USA (NA4)
Group: Cloud Security
Operational
Canada (NA3)
Group: Platform Features
Operational
Canada (NA3)
Group: Singularity Threat Services
Operational
Canada (NA3)
Group: Cloud Security
Operational
Canada (NA3)
Group: Endpoint Security
Operational
Canada (NA3)
Group: AI SIEM (Data)
Operational
Canada (NA3)
Group: Singularity Operations Center and Management Console
Operational
Germany (EU1)
Group: Platform Features
Operational
Germany (EU1)
Group: AI SIEM (Data)
Operational
Showing 20 of 54 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 · 190.2 ms feed latency
Operational
HTTP 200 · 203.12 ms feed latency
Operational
HTTP 200 · 192.22 ms feed latency
Operational
HTTP 200 · 99.19 ms feed latency
Operational
HTTP 200 · 204.17 ms feed latency
Operational
HTTP 200 · 148.79 ms feed latency
Operational
HTTP 200 · 233.97 ms feed latency
Operational
HTTP 200 · 137.14 ms feed latency
Operational
HTTP 200 · 106.5 ms feed latency
Operational
HTTP 200 · 183.38 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
104.61 ms
JSON source