Is DevRev down?

We're currently investigating elevated latency and intermittent timeouts affecting some API requests and in-app experiences for customers hosted in the India (Mumbai) region. You may notice slower page loads, delayed API responses, or occasional timeouts in chat and support workflows. Our engineering team has identified the likely cause and is actively working on mitigation. We apologize for the inconvenience and will post an update as soon as we have more information.

We're currently investigating elevated latency and intermittent timeouts affecting some API requests and in-app experiences for customers hosted in the India (Mumbai) region. You may notice slower page loads, delayed API responses, or occasional timeouts in chat and support workflows. Our engineering team has identified the likely cause and is actively working on mitigation. We apologize for the inconvenience and will post an update as soon as we have more information.

We have resolved the incident affecting API performance in the India (Mumbai) region. Our engineering team identified and mitigated the root cause, and all systems are now operating normally. We apologize for the disruption and appreciate your patience.

We're currently investigating elevated latency and intermittent timeouts affecting some API requests and in-app experiences for customers hosted in the India (Mumbai) region. You may notice slower page loads, delayed API responses, or occasional timeouts in chat and support workflows. Our engineering team has identified the likely cause and is actively working on mitigation. We apologize for the inconvenience and will post an update as soon as we have more information.

We have resolved the incident affecting API performance in the India (Mumbai) region. Our engineering team identified and mitigated the root cause, and all systems are now operating normally. We apologize for the disruption and appreciate your patience.

We're aware of an issue where questions about certain datasets in Computer may not return an answer for some users. If you're affected, some of your questions may fail or come back empty. Questions about other datasets continue to work normally. No data has been lost — this only affects the ability to get answers from these datasets right now, and it will be restored once the issue is resolved. Our team is working on a fix and will post updates here. We apologize for the inconvenience and appreciate your patience while we resolve this.

We have resolved the issue affecting dataset queries within Computer. Our engineering team has deployed a fix to restore complete answer availability, and all affected datasets are now functioning normally. We apologize for the inconvenience and appreciate your patience while we resolved this.

We're currently investigating an issue where recently created or updated records may not appear in search results promptly. This affects search and retrieval of latest objects in our US region. Existing data and other functionality are unaffected. We sincerely apologize for the inconvenience this may be causing. Our team has identified the cause and is actively deploying a fix. We will keep this page updated as the backlog clears and normal indexing resumes.

We are pleased to inform you that the recent issue involving search indexing delays for newly created or updated records in the US region has been successfully resolved. The underlying cause was identified and addressed promptly, ensuring that search functionality is now operating normally and all recent records are appearing in search results as expected. We apologize for any inconvenience this may have caused and appreciate your patience and understanding during this time. Rest assured, our services are stable and operating normally. If you experience any further issues or have questions, please do not hesitate to contact us.

We are currently investigating processing delays in the AP-South-1 region. As a result, some workflows may not execute on time, webhooks may not be delivered on time, and ticket SLA timers may be impacted. Our team is actively working to resolve this, and we will share updates as they become available. We apologize for any inconvenience.

We're pleased to confirm that the processing delays affecting the AP-South-1 region have been fully resolved.\ Earlier, some workflows may not have executed on time, webhook deliveries may have been delayed, and ticket SLA timers may have been impacted. Our team has identified and addressed the underlying cause, and all affected services have been restored to normal performance. The service is now stable and operating as expected.