Freshdesk: Performance Degradation in Freshdesk
Affected components: Agent PortalAgent PortalAgent PortalAgent PortalIntegrations: Freshcaller, Freshservice, Slack & OthersIntegrations: Freshcaller, Freshservice, Slack & OthersIntegrations: Freshcaller, Freshservice, Slack & OthersIntegrations: Freshcaller, Freshservice, Slack & OthersAPITicketing CoreTicketing CoreTicketing CoreTicketing CoreAPIAPIAPICustomer PortalCustomer PortalCustomer PortalCustomer PortalAgent PortalCustomer PortalTicketing CoreIntegrations: Freshcaller, Freshservice, Slack & OthersAPI
Timeline of updates
- update
Between 1:15 PM IST and 1:40 PM IST, some customers may have experienced failures when while accessing the impacted modules in Freshdesk, with requests returning 403 errors. Our engineering teams identified the issue and fixed it by 1:40 PM IST. Services are now operating normally.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.freshworks.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Freshdesk, started 2026-11-20 07:45 UTC, resolved after 25 min, 1 update(s).
- Title
- Performance Degradation in Freshdesk
- Vendor
- Freshdesk
- Date
- URL
- https://rewindex.com/company/freshdesk/incidents/1610227
Freshdesk profileRecent Freshdesk incidentsAll outages on November 20, 2026Freshdesk in November 2026MarkdownJSON