Api seems to be down

Aspose.Words Cloud Product Family
1

2026-06-24 17:09:20.064 ERROR main - main: Traceback (most recent call last):
File “/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py”, line 449, in _make_request
six.raise_from(e, None)
File “”, line 3, in raise_from
File “/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py”, line 444, in _make_request
httplib_response = conn.getresponse()
^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/http/client.py”, line 1375, in getresponse
response.begin()
File “/usr/local/lib/python3.11/http/client.py”, line 318, in begin
version, status, reason = self._read_status()
^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/http/client.py”, line 279, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), “iso-8859-1”)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/socket.py”, line 706, in readinto
return self._sock.recv_into(b)
^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/ssl.py”, line 1278, in recv_into
return self.read(nbytes, buffer)
^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/ssl.py”, line 1134, in read
return self._sslobj.read(len, buffer)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TimeoutError: The read operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py”, line 703, in urlopen
httplib_response = self._make_request(
^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py”, line 451, in _make_request
self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
File “/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py”, line 340, in _raise_timeout
raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host=‘api.aspose.cloud’, port=443): Read timed out. (read timeout=98.89225356397219)

2

Is this issue still persist?

3

I had to migrate from Aspose to Mammoth library because I wasn’t getting any reply here. Frankly, an unacceptable situation. We were relying on this for years for a mission-critical part of our system. Mostly it was for docx to HTML conversion, for which Mammoth seems to be a good alternative. We might still use Aspose for tasks that require better formatting precision.

4

And I was able to do the migration rather quickly using Claude. There might be some truth to the Saaspocalypse meme after all.

5

I’m sorry you faced that issue, some of our services are migrating to the other cluster that’s why you faced that issue at first place.
The other thing you may do in the future to avoid that situation is to increase the timeout in the SDK just set the higher value for timeout while initializing the WordsApi