Hello Aspose Cloud team,
Since around 2026-10-04 13:45 UTC (22:45 JST), all Aspose.Slides Cloud API requests from our production service have stopped working. Our PowerPoint features (PPTX to PNG, PPTX/PPT to PDF, PPT to PPTX) are currently unavailable to our customers.
Symptoms
Every request to https://api.aspose.cloud/v3.0/slides/* hangs: the TCP/TLS connection is established, but the server never returns a response (no HTTP status, timed out after 60 seconds). Other products on the same host respond normally.
Even unauthenticated requests reproduce it, so this does not depend on our credentials:
| Request (no auth header) |
Result |
GET /v3.0/slides/storage/exist/x.pptx |
no response, timed out after 60 s |
GET /v3.0/slides/info |
no response, timed out after 60 s |
PUT /v3.0/slides/convert/pdf |
no response, timed out after 60 s |
POST /v3.0/slides/x.pptx/png |
no response, timed out after 60 s |
GET /v3.0/pdf/storage/exist/x.pdf |
HTTP 400 “ClientId is undefined” in 0.46 s (expected) |
GET /v4.0/words/storage/exist/x.docx |
HTTP 400 “ClientId is undefined” in 0.46 s (expected) |
GET /v3.0/cells/storage/exist/x.xlsx |
HTTP 400 “ClientId is undefined” in 0.47 s (expected) |
POST /connect/token |
responds normally |
Reproduction:
curl -s -o /dev/null -w "%{http_code} %{time_total}s\n" -m 60 https://api.aspose.cloud/v3.0/slides/storage/exist/x.pptx
# -> 000 60.005s (timeout, no response)
curl -s -o /dev/null -w "%{http_code} %{time_total}s\n" -m 60 https://api.aspose.cloud/v3.0/cells/storage/exist/x.xlsx
# -> 400 0.429s
Checked at 2026-10-05 01:38 UTC and again at 01:43 UTC; the issue is still ongoing. api.aspose.cloud resolves to cloud.lb.k8s.dynabic.com (74.113.210.20).
Endpoints we use in production:
PUT /v3.0/slides/storage/file/{name}
POST /v3.0/slides/{name}/png
POST /v3.0/slides/{name}/pptx
PUT /v3.0/slides/convert/pdf
DELETE /v3.0/slides/storage/file/{name}
Questions
- Is there a known outage of the Slides Cloud API? Could you please investigate and restore the service?
- Is there an estimated time to recovery?
- Is there a status page or channel where we can follow Slides Cloud incidents?
Thank you for your help.
@VideoStep,
Thank you for reporting the issue. I have reproduced some problems when using Aspose.Slides Cloud API. We apologize for any inconvenience caused.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): SLIDESCLOUD-2150
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
1 Like
@VideoStep,
We reproduced the issue and implemented a fix. However, during further testing, we found that the issue can still occur intermittently.
We are continuing to investigate the root cause and working on a complete resolution.
We apologize for the inconvenience and appreciate your patience.
1 Like
@andrey.potapov Thank you for your update.
Has this issue still continued, occured intermittently now?
@VideoStep,
Thank you for following up.
Unfortunately, we don’t have any additional information to share at this time. We will update this thread as soon as we receive further details.
We apologize for the inconvenience and appreciate your patience.
@VideoStep,
We would like to inform you that the issue appears to have been resolved following the completion of our migration to Cloudize.
Please try using the API again and let us know if you encounter any further issues.
1 Like
@andrey.potapov
We would like to share that intermittent failures of the Aspose.Cloud Slides API have started occurring again since yesterday. Our synthetic monitoring (Datadog Synthetics, API test run from the Tokyo (AWS ap-northeast-1) probe) detected repeated failures on the following two endpoints.
Monitored endpoints:
- PPT→PPTX conversion:
PUT https://api.aspose.cloud/v3.0/slides/storage/file/*
- PDF conversion:
PUT https://api.aspose.cloud/v3.0/slides/convert/pdf
All times are JST (UTC+9) with UTC in parentheses. Duration = time from the alert being triggered to it being recovered. Data covers 10/13 00:00 JST through 10/14 12:12 JST.
Status at the time of writing (10/14 12:12 JST / 03:12 UTC): both monitors are currently failing again (alerts triggered at 12:08 JST for PPT→PPTX and 12:11 JST for PDF, not yet recovered).
[1] PPT→PPTX conversion – 14 incidents, total about 4 h 53 min (including the ongoing one)
- 10/14 12:08 JST (03:08 UTC) - ongoing
- 10/14 11:48 - 12:00 JST (02:48 - 03:00 UTC) - 12 min
- 10/14 11:18 - 11:22 JST (02:18 - 02:22 UTC) - 4 min
- 10/14 10:18 - 10:27 JST (01:18 - 01:27 UTC) - 9 min
- 10/14 10:03 - 10:07 JST (01:03 - 01:07 UTC) - 4 min
- 10/14 09:38 - 09:57 JST (00:38 - 00:57 UTC) - 18.5 min
- 10/14 09:18 - 09:18 JST (00:18 - 00:18 UTC) - 0.5 min
- 10/14 06:18 - 09:03 JST (10/13 21:18 - 10/14 00:03 UTC) - 2 h 45 min
- 10/14 05:08 - 06:10 JST (10/13 20:08 - 21:10 UTC) - 1 h 1.5 min
- 10/14 04:04 - 04:04 JST (10/13 19:04 - 19:04 UTC) - 0.5 min
- 10/14 01:13 - 01:14 JST (10/13 16:13 - 16:14 UTC) - 1 min
- 10/14 01:04 - 01:08 JST (10/13 16:04 - 16:08 UTC) - 4.5 min
- 10/14 00:43 - 00:50 JST (10/13 15:43 - 15:50 UTC) - 7 min
- 10/13 21:08 - 21:10 JST (10/13 12:08 - 12:10 UTC) - 1.5 min
[2] PDF conversion – 9 incidents, total about 4 h 57 min (including the ongoing one)
- 10/14 12:11 JST (03:11 UTC) - ongoing
- 10/14 09:56 - 10:00 JST (00:56 - 01:00 UTC) - 4 min
- 10/14 09:41 - 09:50 JST (00:41 - 00:50 UTC) - 9.5 min
- 10/14 05:41 - 09:03 JST (10/13 20:41 - 10/14 00:03 UTC) - 3 h 22 min
- 10/14 05:01 - 05:34 JST (10/13 20:01 - 20:34 UTC) - 33 min
- 10/14 04:11 - 04:25 JST (10/13 19:11 - 19:25 UTC) - 14.5 min
- 10/14 04:01 - 04:02 JST (10/13 19:01 - 19:02 UTC) - 1 min
- 10/14 03:36 - 03:56 JST (10/13 18:36 - 18:56 UTC) - 20 min
- 10/14 01:06 - 01:18 JST (10/13 16:06 - 16:18 UTC) - 11.5 min
The failures are intermittent: the monitors recover and fail again repeatedly. The longest stretches today were about 3 h 22 min (PDF conversion) and about 2 h 45 min (PPT→PPTX conversion), both between roughly 05:41 and 09:03 JST.
Could you please look into this and let us know if there is a known issue or any update on the cause? We are happy to provide additional information (request IDs, logs, timestamps) if needed.
Thank you.
@VideoStep,
Thank you for reporting the issue.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): SLIDESCLOUD-2158
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
1 Like
@VideoStep,
Our development team has confirmed that the Aspose.Slides Cloud API experienced performance issues and intermittent failures over the past several hours.
The service is currently operating normally. However, our infrastructure team plans to add more hosts within the next one or two days to improve stability. Until then, intermittent failures may still occur.
We sincerely apologize for the repeated disruptions and appreciate your patience.