Thoughts On The Vocal Outage: October 2025

Introduction

Just a few observations on the current lack of Vocal

Down

SO AWS has caused Vocal and Blue Sky to go down. Although this stops us from publishing on Vocal, it does not stop us from writing and creating.

I am writing this on Google Docs, which gives me a backup if I need it. Of course, no one can see this until I publish. I could publish on my blog, but then it is likely only robots would actually “see” it.

We should all have alternate editors to Vocal for times like these.

I do like how easy it is to insert multimedia into the Vocal editor, but you don’t have fonts, colour and indentation, but it is generally a robust editor. My main issue with it is the pointless autosave, which has lost me a few sentences which I then have to retype.

Currently, I am trawling Facebook for artwork for my forthcoming stories. Maybe I will use some for this one when AWS (which I think stands for Amazon Web Services) returns. I don’t know if their insurance covers this. but Vocal should give us a small refund based on what we pay per day and the average number of reads we get, so I would get about 66c, but that is very unlikely.

One very good thing is that for the first time, Vocal emailed members with the state of play. See the examples below:

This is a most welcome action from Vocal. We know that these situations happen, and these actions show care for your subscribers.

Thank you for that, Vocal. The Status Site is showing the state of play as well. You should bookmark this, as it was working during the downtime:

Conclusion

Thanks for reading, and I would love to know how you spent your time that you would normally spend Vocalising

I included Los Lobos' cover of Ritchie Valens' "C'mon Let's Go" from the "La Bamba" soundtrack, because we are back up and running.