Previous incidents
Application is experiencing an issue.
Resolved Apr 25, 2025 at 10:32pm UTC
Our platform is healthy again. Notifications and updates have been re-enabled.
We apologize for the inconvenience, and thank you for your patience.
2 previous updates
Issue with Updating Open Tickets in Production
Resolved Apr 17, 2025 at 5:49pm UTC
We are pleased to inform you that the issue regarding open tickets becoming immutable in production has been successfully resolved. Our team has taken the necessary steps to restore full functionality to your ticketing system and fix the ones that were affected.
2 previous updates
Issues with Chat Messages and Reopening Issue
Resolved Apr 10, 2025 at 8:55am UTC
The issue causing duplicate chat messages and unexpected ticket reopenings has been resolved. We sincerely apologize for the disruption this may have caused.
Our team has implemented a fix and is monitoring to ensure continued stability. Thank you for your patience and understanding.
1 previous update
Issue with Invitation Process
Resolved Apr 3, 2025 at 6:09am UTC
We are pleased to inform you that the issue with the broken invite flow has been successfully resolved. Our team identified the problem and implemented a hotfix to restore the functionality.
1 previous update
Session Recordings Service Disruption
Resolved Mar 15, 2025 at 5:33pm UTC
We are pleased to inform you that the Session Recording service issue has been successfully resolved. All functionalities are now operating as expected.
1 previous update
Disruption in Old Workflow Runs
Resolved Mar 5, 2025 at 8:01am UTC
We are pleased to inform you that all the workflow runs (except for ones with customer facing actions) have been replayed. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding during this time. We are confident that our service is now stable and operating smoothly. If you experience any lingering issues, please do not hesitate to reach out to us for assistance. Thank you for your continued support!
2 previous updates
Slack Service Disruption Affecting Integrations
Resolved Feb 27, 2025 at 2:36pm UTC
We are pleased to inform you that the issue with Slack being down and the Slack to Devrev integration not functioning has been resolved. We appreciate your patience and apologize for any disruption this may have caused.
1 previous update
Delay in Event Processing
Resolved Feb 26, 2025 at 3:25pm UTC
We are happy to report that the event processing lag and automation issues have been successfully resolved. Our team found the root cause of the delays and made the necessary adjustments to restore normal operations. All pending events have been processed successfully, and no data was lost during the incident.
1 previous update
Issues Switching Between Workspaces on Portal
Resolved Feb 14, 2025 at 4:10pm UTC
We are pleased to inform you that the issue regarding the inability to switch between workspaces on the portal has been resolved. Our team identified the problem and implemented the necessary adjustments to restore full functionality.
1 previous update
The DevRev App is down
Resolved Feb 10, 2025 at 6:00pm UTC
We are pleased to inform you that the technical issue affecting our application has been resolved, and the service is now fully operational. Our engineering team has addressed the problem, and we are closely monitoring the system to ensure continued stability. We sincerely apologize for any inconvenience this disruption may have caused and appreciate your patience and understanding during this time.
Thank you for your continued support.
1 previous update
Issue with Sending Messages via WhatsApp Snap-in
Resolved Feb 5, 2025 at 2:05pm UTC
We are pleased to inform you that the issue with the WhatsApp Snap-in failing to send messages in DevRev has been resolved.
2 previous updates
Severity Field Unavailable on Incident Sidepanel
Resolved Feb 5, 2025 at 10:09am UTC
We are pleased to inform you that the issue regarding the unavailability of the Severity Field on the Incident Object has been resolved. Our team identified the problem and implemented the necessary changes to restore this functionality.
1 previous update