SharePoint Online outage on
March 6, 2026

Read more >

Improved SSO setup and
logging

Read more >

StatusGator logo
Schedule a Demo
StatusGator logo
Use cases

IT Teams

Stay informed of outages and reduce tickets

DevOps

One status page for all your providers

Education

Features designed specifically for K12

Enterprise

Advanced features designed for enterprise

Managed service providers

Impress clients with proactive monitoring

Competitive intelligence

Analyze and compare peer performance

Monitor dependencies to prevent revenue loss

Create and manage custom status pages for your product

Features

Status page

A status page with service, website, and custom monitors built-in

Status aggregation

Aggregate the status of all vendors to a single page

Cloud monitoring

Monitor all your cloud services from a single dashboard

Website monitoring

Monitor your website with uptime monitoring built-in

Monitor network connectivity

Control the status of custom monitors manually with incidents

Get notified of disruptions before they become public

Pricing

Business

From startup to enterprise and everything in between

Education

Special plans and discounts for K12 and higher ed

Integrations

Incident Management

Better Uptime
FireHydrant
Opsgenie
PagerDuty

Notifications

Private Status

AT&T status
AWS status
Azure status
Microsoft 365 status
Zendesk status

Status Pages

Atlassian Statuspage
StatusHub

Advanced

Sign In Sign Up

SentinelOne outage: July 10 incident went unacknowledged

Published:

by Andy Libby

On July 10, 2025, SentinelOne, a leading cybersecurity platform, experienced a widespread outage that disrupted access to its admin consoles across multiple regions.

The incident impacted users in Europe, North America, and beyond, preventing security teams from accessing critical management features. Despite the scale of the disruption, no official public acknowledgment or status update was issued by SentinelOne. According to some users on Reddit, the outage was eventually mentioned privately via support channels, but most organizations were left without clear information.

Fortunately, services like StatusGator helped fill the information gap by detecting the outage early and providing real-time updates to customers and the wider community.

Timeline of the July 10 SentinelOne outage

  • 9:29 AM ET – Early reports emerge from Europe: users cannot access SentinelOne’s management console, with repeated 504 Gateway errors and timeouts.
  • 9:33 AM – Multiple reports trigger early alerts through StatusGator’s monitoring platform, notifying customers and updating dashboards automatically.
  • 9:37 AM – An unofficial SentinelOne status page maintained by StatusGator is updated to reflect the outage, becoming one of the few public resources documenting the incident.
  • 9:42 AM – Reports flood in from across Europe. A post on Reddit is made to gather additional feedback and understand the scale of the problem.
  • 10:02 AM – A frustrated user in Berlin clicks “Report Outage” 91 times, highlighting the level of disruption.
  • 10:30 AM – A live video update is posted to LinkedIn and YouTube to share real-time information and help affected organizations respond faster.
  • 11:33 AM – Outage reports begin appearing from North America, confirming that the incident is not limited to Europe. Partial recovery signs start to emerge.
  • 12:11 PM – StatusGator’s automated monitoring marks the incident resolved based on the decline in reports and confirmation from users.
  • 12:39 PM – The unofficial status page is updated to confirm full resolution.
  • Later that day – Reddit users mention that SentinelOne acknowledged the outage privately, but no public statement or post-mortem was issued.

What user reports revealed

  • The outage began at 9:29 AM ET and lasted roughly three hours.
  • Reports came from Europe, North America, and parts of Asia, showing a global impact.
  • Users experienced “server not responding,” “console inaccessible,” and “504 Gateway Time-out” errors.
  • Report spikes between 9:30–10:00 AM indicated a near-global service disruption.

No status page and no post-mortem

This was not SentinelOne’s first outage this year. A similar incident on May 29 disrupted services for hours. SentinelOne published an official update explaining that event and detailing corrective actions.

However, as of the July 10 outage:

  • There is still no public status page, leaving customers without a direct way to check service health.
  • No post-mortem report has been released for this latest incident.
  • Acknowledgment of the July 10 outage appears to have been limited to private support channels, not a public announcement.

How independent monitoring helped

With no official updates available, many organizations relied on independent monitoring platforms like StatusGator to stay informed:

  • Early detection: Alerts were triggered within minutes of the first reports.
  • Public visibility: An unofficial status page provided free, real-time information for everyone.
  • Community-driven insights: User submissions and Reddit discussions helped quickly map the outage’s impact.

Takeaway

The July 10 outage highlights a gap in transparency during SentinelOne service disruptions. Without a public status page or timely incident reporting, customers lacked clear information when they needed it most.

Independent monitoring services, such as StatusGator, played a critical role by detecting the outage early and sharing real-time updates, helping organizations respond faster and with better situational awareness.

Ready to see how StatusGator can keep your team informed and protected?
Get started with StatusGator today and never get left in the dark by another cloud outage.

Share this

Photo of author

Andy Libby

Andrew Libby is a veteran Ruby developer and technologist with over 25 years of experience; Andy is co-founder of StatusGator and leads engineering at Nimble Industries.