Pliant API Outage History

On September 5, between approximately 08:30 and 13:30 CEST, some CaaS/Pro API requests intermittently returned HTTP 403 responses across several endpoints, including transaction fetching. The issue was caused by a third-party provider supporting our permission layer. Requests failed closed: no unauthorized access was granted and no data was changed as a result of the incident. The provider deployed a fix on the same day, and the issue has not recurred. We have since added dedicated monitoring for this failure mode and significantly reduced load on the permission layer. Customers who experienced gaps in data retrieval during the affected period can re-fetch the affected data to bring their systems back in sync.

Investigating Between 07:00 and 14:00 UTC (adjust timezone if needed), the Sandbox UI experienced degraded performance and was unavailable for some users. During this period, some Sandbox API endpoints were also impacted, resulting in intermittent request failures. Resolved The issue has been resolved and all Sandbox UI and API services are operating normally. We apologize for the inconvenience and appreciate your patience while we worked to restore service.

The problem was resolved. The API docs are available again.

This incident has been resolved.

The issue affecting API authentication has been resolved. This incident was caused by an outage with Auth0, our authentication provider, which has now been fully mitigated. API consumers are able to generate bearer tokens and access the API as expected. We will continue to monitor to ensure ongoing stability. Thank you for your patience.

The incident is resolved.

The incident on PCI endpoints is resolved and API operation is back to normal.

We experienced approximately 20 minutes of degraded service on the CaaS API due to issues with our permission evaluation layer. During this period, API calls requiring permission validation were incorrectly rejected, resulting in: 1) Entities being temporarily unavailable via the API. 2) Entity update operations failing to apply. Approximately 400 operations were affected in total. The issue has been resolved and all services are operating normally again.

This incident has been resolved.