Update - Overnight monitoring complete. Severity of this issue has been greatly reduced and there has been minimal impact on the platform. Monitoring and root cause analysis will continue today. Thank you for bearing with us, while we attend to this problem.
Mar 26, 07:27 UTC
Monitoring - The cause for this issue has been identified as slowdown in response time when calling an upstream provider. Given API throughput, this problem was magnified and led to the brief exhaustion of available resources. We have enforced a more stringent timeout and will continue to monitor overnight.
Mar 25, 18:55 UTC
Investigating - We are currently investigating the cause of micro-outages on API V4 resulting in the failure of some calls.
Mar 25, 11:04 UTC
Monitoring complete. This issue has now been resolved.
Mar 27, 13:01 UTC
Access to this data source has now resumed. We now begin a short monitoring phase before closing out. We apologise for any interruption to service.
Mar 27, 09:23 UTC
We are currently investigating this issue, with the following impact on the service: - KTB endpoint will return 'fail' for all checks while we are unable to retrieve this information. - Peps and Sanctions endpoints will not be available at this time.
Mar 27, 09:16 UTC
The scheduled maintenance has been completed.
Mar 25, 10:57 UTC
An upstream service provider will be carrying out routine maintenance during this time period. This may impact provision of Financials, Filings, Credit Reports and KYB endpoints. We apologise in advance for any interruption to normal service. Subscribers will be notified at the start and end of this maintenance.
Mar 10, 10:58 UTC
This issue has now been resolved. All services are operating normally.
Mar 18, 12:13 UTC
API clients calling our Peps and Sanctions or KYB endpoints will have seen HTTP 503 responses from 7.45am to 9.30am today. Peps and Sanctions functionality via the Site was also unavailable during this time. Our data provider has resumed normal service and we are now monitoring. Please accept our apologies for this interruption to service.
Mar 18, 10:38 UTC