Pelcro Outage History

Open API and Core API recovered.

Resolved — We detected elevated latency and slowness on the platform caused by an unusual spike in traffic. The incident occurred between 07:34 AM and 08:00 AM UTC and was quickly mitigated. All services are operating normally, and we continue to monitor platform performance.

The issue affecting export operations has been fully resolved. Export processing is now operating normally, and all delayed operations have been cleared. We will continue monitoring the platform to ensure continued stability. Thank you for your patience while our team investigated and resolved the issue.

Our proactive measures have successfully restored stable access to our services. All systems are currently operational. We continue to monitor our platform closely and are in contact with the vendor for confirmation of their full restoration. We will provide a final update once the vendor confirms their service is completely stable. Thank you for your patience.

The earlier outage affecting one of our third-party vendors has been resolved, and our messaging services are now fully operational. All SMS notifications and message-based communications are functioning normally. We will continue to monitor performance to ensure stability. Thank you for your patience and understanding while the issue was addressed.

Postmortem Incident: On October 15th, 2025, we experienced an unexpected surge in traffic that placed increased load on our storage systems, resulting in temporary slowdowns and connection issues. Impact: During this period, some users encountered delays or temporary errors. The issue was promptly identified, and normal operations were restored. Moving forward: We are taking steps to optimize affected components to prevent similar incidents in the future. Our focus remains on delivering a seamless and reliable experience for our users.

A fix has been deployed, and we are actively monitoring the platform to ensure normal operations have resumed. We appreciate your patience and apologize for any inconvenience this may have caused. If you experience any further issues, please contact our support team at [email protected].

Postmortem Incident: On March 17th, 2025, during the release of version 1.92.0, a bug was introduced in a task aimed at enhancing the security of certain platform flows. Impact: This bug directly impacted users who rely on the platform's invoicing feature, preventing them from marking invoices as paid. No data was lost, and other platform functionalities remained unaffected. Moving forward: We are taking steps to improve our internal processes and testing protocols to prevent similar incidents in the future. Our focus remains on delivering a seamless and reliable experience for our users.

Postmortem Incident On March 15th, 2025, some users encountered a 500 error when attempting to log in to the platform. This issue specifically affected collaborators who were associated with multiple accounts and whose session had previously expired. Impact The incident resulted in affected users being unable to access their dashboards, disrupting their workflow and limiting their ability to manage their accounts. Only a subset of collaborators experienced this issue. Other collaborators were able to access the platform without interruption. Moving Forward We have identified the root cause of the issue and implemented a fix to prevent similar errors in the future.

Resolved - We have noticed a high latency as a result of an unusual spike in traffic that caused a slowness on the platform. This incident occurred for 5 minutes between 16:26 UTC and 16:31 UTC and was quickly mitigated. The issue has now been fully resolved.

Monitoring Update - The platform remains stable, and we have not observed any further issues. Our team is actively investigating the root cause to ensure long-term stability and prevent recurrence.

Resolved - Due to a hardware issue on the caching system by our vendor which affected a portion of our infrastructure, we have experienced a high latency accompanied with a server timeout for 14 minutes between 17:53:00 and 16:07:00 UTC. This was mitigated and the incident has been resolved.