We run Word→PDF conversion through Aspose.Words Cloud (.NET SDK Aspose.Words.Cloud.Sdk) from our production CRM. On two days this week the API failed or hung for ~1.5–2 hours each time while status.aspose.cloud showed all components Operational.
Client Id / App SID:
Region / API host: api.aspose.cloud, storage: storage.aspose.cloud (default cloud storage), folder “Font”
Timeline (UTC), grouped by exception text:
2026-09-01 17:23–18:07 x11 ApiException: Service Unavailable
2026-09-01 18:14–18:21 x6 ApiException: Unable to connect to the storage. No such host is known. (storage.aspose.cloud:443)
2026-09-01 18:16–18:37 x12 ApiException: not found fonts in Font
2026-09-04 13:50–14:42 x34 ApiException: Error while get files in folder ‘Font’ from storage: AmazonS3 Storage exception: The SSL connection could not be established
2026-09-04 14:54–15:19 x15 ApiException: Service Temporarily Unavailable
2026-09-04 15:23 → 7 conversion calls never returned (still pending after >1 h, no exception)
Questions:
- Was there an incident on the Words API / cloud storage in these windows? Please add it to the status page.
- The hanging calls after 15:23 UTC: is there a server-side timeout we should expect, or is a client-side timeout the only protection?
- Any recommended mitigation (alternate endpoint/region, retry policy)?
Full stack traces and request timestamps available on request.