Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Silverfort Outage History

Every past Silverfort outage tracked by IsDown, with detection times, duration, and resolution details.

There were 8 Silverfort outages since April 2023. The 4 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Maintenance May 17, 2026

May 2026: SaaS Application Maintenance

Detected May 17, 2026 7:36 AM EDT · Resolved May 17, 2026 10:41 AM EDT · Duration about 3 hours

Silverfort performed planned maintenance on their SaaS application that lasted 3.1 hours. SaaS-hosted customers experienced brief interruptions to application access during the maintenance window. Security protection services remained unaffected throughout the maintenance period.

Maintenance April 27, 2026

April 2026: Maintenance

Detected Apr 27, 2026 7:56 AM EDT · Resolved Apr 27, 2026 8:09 AM EDT · Duration 13 minutes

Silverfort experienced degraded performance in their EU secondary region during a 13-minute maintenance window. The performance issues have been resolved and the service is being monitored for stability. No specific services or user impacts were detailed beyond the regional performance degradation.

Maintenance April 12, 2026

April 2026: SaaS Application Maintenance

Detected Apr 12, 2026 4:24 AM EDT · Resolved Apr 12, 2026 7:25 AM EDT · Duration about 3 hours

Silverfort performed planned maintenance on their SaaS application that lasted 3 hours. SaaS-hosted customers experienced brief interruptions to application access during the maintenance window. Security protection services remained unaffected throughout the maintenance period.

Minor March 24, 2026

March 2026: Microsoft Teams integration issues

Detected Mar 24, 2026 1:37 PM EDT · Resolved Mar 24, 2026 5:32 PM EDT · Duration about 4 hours

Silverfort experienced issues with its Microsoft Teams integration due to errors from the Microsoft service. The integration functionality was affected during the incident. The issue was resolved after 3.9 hours of investigation and remediation efforts.