Freshservice Outage History

Freshservice carried out scheduled regional maintenance affecting Custom Objects in three regions: Mumbai, Frankfurt, and North Virginia. The maintenance window began at Nov 1, 2025 2:31 AM UTC and ended at Nov 1, 2025 4:01 AM UTC, lasting about 1 hour 30 minutes. During this period, the affected components were intermittently unavailable as regions transitioned in and out of maintenance; four status updates were posted on Freshservice's status page to track progress and the eventual restoration to normal operation.

The Freshservice Web App experienced a partial outage beginning at Oct 20, 2025 8:06 AM UTC, initially tied to a third-party service provider and later to issues with the cloud provider. The incident degraded the Web App across multiple modules, including Automation, Alert Management, Assets, On-Call Management, Self-service portal, Marketplace, Project Management, Solutions, Releases, Changes, Problems, Billing, Analytics, Tickets, and Dashboard, and also impacted US East (North Virginia) Third Party Services. The outage disrupted common workflows and user access for an extended period.

The provider posted four updates during the incident, with notable activity at Oct 20, 2025 6:06 PM UTC and Oct 20, 2025 6:16 PM UTC, and full restoration completed by Oct 20, 2025 11:16 PM UTC. The incident lasted roughly 15 hours from the initial alert to full recovery.

Freshservice Web App / Agent Portal experienced brief slowness, impacting access to the portal for about 10 minutes. The incident began at Oct 7, 2025 10:01 AM UTC and was resolved by Oct 7, 2025 10:11 AM UTC. Users attempting to access the portal may have noticed longer load times or delays during this period.

The Freshservice status page documented Observing slowness while accessing the portal and showed the Web App / Agent Portal moving from up to warn at Oct 7, 2025 10:01 AM UTC and returning to up at Oct 7, 2025 10:11 AM UTC. The incident included two official status updates detailing the degradation and recovery. The affected component was the Web App / Agent Portal.

Freshservice conducted a scheduled maintenance window affecting the US East (NORTH VIRGINIA) Workflow component. The workflow service was temporarily unavailable during the window, with the status transitioning from up to maintenance at Sep 20, 2025 1:31 AM UTC and returning to up at Sep 20, 2025 2:31 AM UTC. The maintenance lasted approximately 1 hour, and service resumed after the updates documented on the Freshservice status page. The provider issued two status updates during the incident.

Freshservice conducted a scheduled maintenance window from Sep 7, 2025 1:31 AM UTC to Sep 7, 2025 2:31 AM UTC. During this period, Web App / Automation and MEA / Workflow components were placed in maintenance and subsequently restored to normal operation after the window. The MEA region components were affected by the maintenance, and two status updates were issued to communicate the window and its completion. The maintenance lasted roughly one hour and did not indicate broader issues beyond the scoped components.

Freshservice experienced degraded performance affecting the Search feature in the US East (NORTH VIRGINIA) region. Users reported slow responses when submitting service desk tickets or editing automated workflows, and some could not open the inventory tab. The outage began at Aug 21, 2025 5:51 PM UTC and was resolved by Aug 21, 2025 7:56 PM UTC. The incident led to disruptions in day-to-day operations relying on search, ticketing, and inventory access. The service published two status updates during the incident, noting the impact and later confirming resolution.

Freshservice experienced a brief degradation of the Search function in the US East (North Virginia) region, causing slower loading and search-related issues for users. The incident began when the Freshservice status page transitioned to a degraded state at 2:21 PM UTC and was resolved by 3:36 PM UTC, lasting about 1 hour 15 minutes. The status page issued 2 updates during the incident, and user reports showed activity beginning around 1:15 PM UTC with higher volume around 1:30 PM UTC to 1:45 PM UTC. The impact was confined to the US East (North Virginia) Search component, with no broader regional effects.

Freshservice experienced a brief outage affecting the US East (NORTH VIRGINIA) Search component, which degraded or prevented loading of the ticketing page and related ticketing features. Users reported issues loading ticket lists and accessing ticketing UI, with limited functionality during the incident. The disruption appears centered on the US East region but caused widespread user reports across different locations before the service recovered.

Freshservice experienced a brief degraded experience due to a mismatch in the Ticket List view filters, which affected how tickets appeared in the main list. The incident began at 12:31 AM UTC and was resolved by 3:11 AM UTC, lasting 2 hours 40 minutes.

Freshservice published two status updates during the event, describing the degraded visibility and confirming restoration after the fix. The service returned to normal after the final update.

Freshservice experienced intermittent login failures affecting multiple regional login services. Users in MEA, Sydney APAC, US East (N. Virginia), Mumbai, and Frankfurt reported difficulties signing in, resulting in degraded access across those regions. The incident began when the status page indicated a degraded login experience and affected five regional components. The problem persisted for about 1 hour and 55 minutes before full recovery.

According to Freshservice status updates, the outage began on 2:26 PM UTC and was resolved by 4:21 PM UTC. The provider issued two updates during the incident as it worked to restore normal sign-in functionality, with regional components returning to normal in sequence as stability was restored.