Is Webroot down?

Last checked 4m ago
Current status
Webroot is down

3 active incidents: C2321562 - Software maintenance, Database Maintenance scheduled for 13 September 2026 · +1 more

Official status page: https://status.webroot.com · Polled every 5 minutes · 267 components tracked

Webroot is reporting a major outage right now (last checked 4m ago). 3 active incidents on the official status page.

Real-time Webroot status, recent outages, and incident history — pulled directly from Webroot's official status page at https://status.webroot.com every 5 minutes. Pingoru tracks 267 Webroot services and has captured 250 incidents in the last 90 days (99.40% uptime). Get email, Slack, Discord, or webhook alerts the moment Webroot reports a new incident — free for 5 monitors, no credit card.

Users who monitor Webroot also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
Webroot uptime 99.40% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 24m
    Started Sep 09, 2026, 07:49 AM UTC · Resolved Sep 09, 2026, 08:13 AM UTC
    Frankfurt EU8
    Timeline · 3 updates
    • investigating · Sep 09, 2026, 07:49 AM UTC

      Frankfurt EU8 is currently experiencing service degradation with UCMDB service on EU8 farm. Clients may experience degradation while loading request entities or using an actual service on the EU8 farm. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3995249

    • resolved · Sep 09, 2026, 08:13 AM UTC

      Frankfurt EU8 experienced service degradation with UCMDB service on EU8 farm. The issue is now resolved. We appreciate your patience. Tracking Number: IM3995249

    • postmortem · Sep 11, 2026, 07:08 PM UTC

      # **Incident Report** **Tracking number:** IM3995249 PM1011727 **Incident window:** September 9, 2026, from 06:56 GMT to 07:53 GMT **Services affected:** OpenText™ Enterprise Service Management \(Frankfurt EU8\) **RCA target completion date:** September 23, 2026 **Overview** On September 9, 2026, at 07:38 GMT, Incident Management was engaged to investigate a service issue affecting the OpenText™ Enterprise Service Management Frankfurt EU8 farm. **Impact** Users experienced service degradation and delays when loading request entities. **Resolution** The investigation determined that gateway processing errors caused performance degradation within the UCMDB infrastructure, leading to the observed delays. To mitigate the issue, technical teams performed targeted service restarts to clear the gateway errors and restore connectivity. Following these actions, service health normalized, and normal functionality was restored at 7:42 GMT. Validations were completed at 07:53 GMT, ending the impact.

    Latest: # **Incident Report** **Tracking number:** IM3995249 PM1011727 **Incident window:** September 9, 2026, from 06:56 GMT to 07:53 GMT **Services affected:** OpenText™ Enterprise Servi…

  2. Resolved 3d 19h
    Started Aug 31, 2026, 04:33 PM UTC · Resolved Sep 04, 2026, 12:22 PM UTC
    Zix Office 365
    Timeline · 11 updates
    • investigating · Aug 31, 2026, 04:33 PM UTC

      Microsoft O365 Exchange - some users are experiencing an issue connecting to Exchange 365. Microsoft is aware of the issue and has provided Issue ID: EX1464935.

    • investigating · Aug 31, 2026, 04:57 PM UTC

      Update from Microsoft: Microsoft isolated a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity. They are analyzing service telemetry to identify the underlying source of impact and validate potential remediation options. Additionally, they are continuing to assess the scope of impact and monitor for additional affected scenarios. More info - Users may experience a variety of symptoms related to this event, including but not limited to: Delays or failures when sending or receiving email messages. Authentication-related errors when accessing Exchange Online services. Difficulties accessing or performing actions within Exchange administration experiences. Intermittent failures affecting mailbox operations and message delivery workflows.

    • investigating · Aug 31, 2026, 05:51 PM UTC

      Update from Microsoft: Microsoft has identified a potential corrective action for the affected infrastructure and are evaluating deployment options. They are monitoring service telemetry and affected Exchange Online transactions to determine whether the action is reducing impact and to better understand the scope of affected scenarios.

    • investigating · Aug 31, 2026, 08:14 PM UTC

      Update from Microsoft: Microsoft is continuing to perform comprehensive tests to ensure their mitigation strategy effectively resolves the issue without introducing additional impact. In parallel, they are exploring alternative remediation avenues to minimize impact in the interim.

    • identified · Sep 01, 2026, 12:26 PM UTC

      Update from Microsoft: A substantial portion of the remediation deployment has been completed, and organizations whose environments remain affected are expected to recover as the deployment reaches the relevant infrastructure. As remediation progresses, Microsoft is focused on validating sustained recovery and monitoring for any remaining pockets of impact before determining whether any additional corrective actions are required.

    • monitoring · Sep 01, 2026, 05:07 PM UTC

      Update from Microsoft: Microsoft observed continued recovery across previously impacted Exchange Online scenarios, with core mail flow functionality remaining healthy. Their focus remains on validating recovery across dependent Microsoft 365 experiences and confirming that remaining impact scenarios are fully addressed. They are maintaining enhanced monitoring while engineering teams complete end-to-end validation before determining whether any further corrective actions are required.

    • monitoring · Sep 01, 2026, 09:57 PM UTC

      Update from Microsoft: Microsoft continues to advance multiple workstreams to restore service and prevent additional impact. Microsoft is prioritizing infrastructure that requires the most immediate attention while carefully expanding corrective actions across additional regions, with continued monitoring throughout this process. In parallel, Microsoft is investigating remaining reports of impact and evaluating additional actions to support full service recovery.

    • monitoring · Sep 02, 2026, 12:18 PM UTC

      Update from Microsoft: Their telemetry indicates service availability remains stable above 99 percent and expect the majority of users should no longer be seeing impact from this issue. The continued focus is on balancing the implementation of their fixes across remaining portions of affected infrastructure to ensure persistent recovery, with added attention on ensuring withstanding recovery of scenarios dependent on REST and Graph API connection methods.

    • monitoring · Sep 03, 2026, 04:45 PM UTC

      Update from Microsoft: Microsoft discovered an issue in less than one percent of their infrastructure, where additional mitigation efforts to resolve impact for Exchange Online did not successfully deploy. The vast majority of impact remains remediated; however, those serviced from the impacted portion of infrastructure may be unable to access previously recovered Outlook connection methods. Microsoft remains committed to restoring all services to all users and will continue to carefully monitor their telemetry to ensure recovery.

    • monitoring · Sep 03, 2026, 06:33 PM UTC

      Update from Microsoft: All user impact scenarios are now resolved as they rectified the additional mitigation efforts for the Outlook impact which occurred in less than one percent of their infrastructure. They will continue to monitor their telemetry to ensure all services remain healthy and plan to close this communication by next update.

    • resolved · Sep 04, 2026, 12:22 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 1h 42m
    Started Aug 28, 2026, 04:15 PM UTC · Resolved Aug 28, 2026, 05:58 PM UTC
    Desktop Messaging BMS
    Timeline · 3 updates
    • investigating · Aug 28, 2026, 04:15 PM UTC

      Desktop Messaging BMS is currently experiencing delays in processing outbound fax delivery. Document backlogs exist and are currently being processed. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3987893

    • investigating · Aug 28, 2026, 05:16 PM UTC

      Desktop Messaging BMS is currently experiencing delays in processing outbound fax delivery. Document backlogs exist and are currently being processed. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3987893

    • resolved · Aug 28, 2026, 05:58 PM UTC

      Desktop Messaging BMS experienced delays in processing outbound fax delivery. Backlogs have been cleared, and the issue is now resolved. We appreciate your patience. Tracking Number: IM3987893

    Latest: Desktop Messaging BMS experienced delays in processing outbound fax delivery. Backlogs have been cleared, and the issue is now resolved. We appreciate your patience. Tracking Numbe…

  4. Resolved 41m
    Started Aug 28, 2026, 02:42 AM UTC · Resolved Aug 28, 2026, 03:24 AM UTC
    Core Communications
    Timeline · 3 updates
    • investigating · Aug 28, 2026, 02:42 AM UTC

      Core Communications Europe is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience. Tracking Number: IM3987509

    • monitoring · Aug 28, 2026, 03:13 AM UTC

      Core Communications Europe was unavailable. Teams are currently assembled and working to resolve the issue. Service has been restored and is being validated. We appreciate your patience. Tracking Number: IM3987509

    • resolved · Aug 28, 2026, 03:24 AM UTC

      Core Communications Europe was unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM3987509

    Latest: Core Communications Europe was unavailable. The issue is now resolved. We appreciate your patience. Tracking Number: IM3987509

  5. Resolved 1h 45m
    Started Aug 26, 2026, 02:12 PM UTC · Resolved Aug 26, 2026, 03:57 PM UTC
    MailStore Cloud
    Timeline · 3 updates
    • investigating · Aug 26, 2026, 02:12 PM UTC

      MailStore Cloud is currently unavailable. Teams are currently assembled and working to resolve the issue. We appreciate your patience.

    • monitoring · Aug 26, 2026, 03:05 PM UTC

      MailStore Cloud was unavailable. Service has been restored and is being validated. We appreciate your patience.

    • resolved · Aug 26, 2026, 03:57 PM UTC

      MailStore Cloud was unavailable. The issue is now resolved. We appreciate your patience.

    Latest: MailStore Cloud was unavailable. The issue is now resolved. We appreciate your patience.

See the full Webroot outage history

49 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Webroot outage history →

Or sign up free to get alerts when Webroot breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 54 incidents View full outage history →