Temporary service disruption

Hi All,

This issue has been communicated to our product team and you will be updated as soon as it is fixed.

Regards,

Hi,

The issue has been fixed. Please try it at your end and confirm. We apologise for any inconvenience this may have caused.

If you continue facing this or any other issue, please feel free to get in touch.

Regards,
---------------
Muhammad Sohail
Aspose - File Format APIs

For now, two things from our side:

* How is it possible that a problem is marked as resolved, it then starts occurring again, and it then again takes >8 hours to resolve that same problem.

* Please let all of us know what steps will be taken on restructuring the Aspose Cloud organization so service disruption problems like this will properly be mitigated next time. We were in the dark the whole weekend, and we were not able to contact anyone.

Hi Richard, All,

We understand your concern.

If the issue was caused due to the service downtime we would have gotten the alerts already, but as the service itself was not down, rather only the storage API broke and it was caused due to a cache conflict because of the recent changes in the API versioning scheme. It’s not like that we were not working on the matter during the weekend, however, it’s just that it took longer to get it fixed.

However, we’re now taking measures from all aspects to make sure that (1) this situation does not occur again and we could avoid such situations including long down times/broken APIs (2) just in case something bad happens we could mitigate the issue quickly.

I’m very much hopeful that you’ll not have to face such kind of trouble in the future.

Regards,