Freshservice Outage History

Freshservice experienced degraded analytics performance that affected dashboards and reporting tools for users. The issue began at 3:32 PM UTC and was resolved by 6:51 PM UTC, lasting about 3 hours and 19 minutes.

The Freshservice status page documented the incident as 'Performance Degradation with Analytics' and posted two updates during the event before service returned to normal, with the issue affecting the Analytics component and its downstream data visualization and reporting features.

Freshservice experienced degraded analytics performance in the US region, with Analytics Reports loading slowly and causing delays when accessing reporting dashboards. Users attempting to generate or view analytics data were affected, while other Freshservice features remained available.

The incident began at 4:06 PM UTC and was resolved by 9:41 PM UTC, lasting approximately 5 hours and 35 minutes. The Freshservice status page recorded two updates during the event, documenting the degraded analytics in the US region and the subsequent recovery.

Freshservice underwent a brief maintenance window from Mar 15, 2025 3:31 AM UTC to Mar 15, 2025 4:01 AM UTC, lasting 30 minutes. The incident included two official status updates, and there were no user reports of impact. Services returned to normal after the maintenance window and are operating normally.

Freshservice experienced a brief scheduled maintenance window on Mar 15, 2025 2:31 AM UTC to Mar 15, 2025 3:01 AM UTC. The incident lasted about 30 minutes, and Freshservice returned to normal operations after the maintenance. The provider published two status updates to document the transition and resolution.

Freshservice in the Mumbai region underwent a brief maintenance window starting at 1:31 AM UTC and ending at 2:01 AM UTC, lasting about 30 minutes. During this window 15 Mumbai-region components were placed into maintenance, including Activities & Audit log, Login, Freshcaller, Freddy AI Agent, Chat, Ticket - Service Request, Sandbox, Mobile App, API, Authentication, Reporting, Third Party Services, Search, Custom Objects, and Workflow. This resulted in temporary access limitations for affected features in the region while the maintenance was in effect. Freshservice published two status updates confirming the maintenance and the subsequent return to normal, with services restored to up.

Freshservice conducted a scheduled maintenance window in the Asia Pacific (Sydney) region, placing about 15 components into maintenance and potentially causing brief interruptions for users in Sydney. Affected components included Freddy AI Agent, Search, Reporting, Login, Activities & Audit log, Freshcaller, Chat, Third Party Services, Ticket - Service Request, Sandbox, Custom Objects, Workflow, Mobile App, API, and Authentication.

Freshservice conducted a scheduled maintenance window starting at 8:31 AM UTC, placing a broad set of Web App components and the Middle East and Africa (MEA) region services into maintenance. This affected multiple areas including Analytics, Dashboard, Tickets, API, Authentication, Reporting, and related MEA services. Users could have experienced limited access or intermittent functionality across these features during the 30-minute window. The window concluded with affected components returning to normal at 9:01 AM UTC.

Freshservice experienced a brief degraded performance affecting the Workflow Automation executions in US East (North Virginia). The issue began at 5:07 PM UTC and was resolved by 5:31 PM UTC, lasting about 24 minutes. The impact appeared limited to the Workflow component in the North Virginia region, with some users experiencing delays or failures in automated workflows.

The Freshservice status page published two updates during the incident: the initial update at 5:07 PM UTC noting issues with Workflow Automation, and a follow-up at 5:31 PM UTC confirming restoration. No broader disruption to other services was reported.

Freshservice entered a scheduled maintenance window at 3:31 AM UTC, impacting four components: Notifications / In-App Notifications, Email / Outgoing email, Email / Incoming email, and Notifications / Mobile Notifications. The incident included a brief maintenance window for these components around 4:32 AM UTC to 5:01 AM UTC, before full restoration was achieved later in the day at 4:01 PM UTC. The total duration from start to complete recovery was about 12 hours and 30 minutes. The provider issued four status updates during the incident to communicate progress and resolution.

Freshservice briefly entered maintenance starting at 2:31 AM UTC and returned to normal at 3:01 AM UTC. The 30-minute window was reflected on the Freshservice status page, which showed the transition from up to maintenance and back to up. The provider published two status updates documenting the maintenance window and its completion.