Aiir had 20 outages in the last 2 years totaling 65h 33m of downtime — averaging 0.8 incidents per month.
There were 20 Aiir outages since October 20, 2025 totaling 65h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're currently investigating an issue affecting Audio.co. We're sorry for the disruption this is causing and aim to resolve it as soon as we can.
We have identified the issue and implemented a fix. We're really sorry for any inconvenience this has caused.
We are currently investing an issue with receiving SMS messages into Studio Inbox. Sorry for any inconvenience this has caused. We'll provide a further update when we have more information.
We are continuing to investigate issues receiving SMS messages into Studio Inbox. Clients using Text Groove's API are unaffected by this and should be able to receive messages as normal. This issue also affects clients using Myriad News to publish news articles to their website. Sorry for the inconvenience caused, our team are continuing to work on resolving this issue and we'll provide further updates as soon as we can.
We have identified the issue receiving SMS messages into Studio Inbox which was related to the earlier essential update work on Aiir's platform (on.aiir.com). New SMS messages should now successfully show in Studio Inbox and any clients using Myriad News will be able to republish news articles to their Aiir website. Sorry for the inconvenience caused by this and thank you for your patience whilst we resolved the issue. We're continuing to monitor this fix.
Thank you for your patience whilst we resolved this issue and sorry for any inconvenience this caused.
Vonage, one of the providers of SMS messaging services used by Studio Inbox customers, is currently experiencing issues delivering messages. Affected customers can follow updates here: https://vonageapi.statuspage.io/
Some customers are reporting SMS messages are now being delivered again as normal. We haven't received an official update from Vonage yet, but we'll update here once it's confirmed resolved. Apologies for any inconvenience this may have caused.
Vonage has confirmed that this issue has now been resolved. Any further updates will be shared on its status page: https://vonageapi.statuspage.io/
WeatherAPI, one of the data providers Audio.co uses, is currently producing inaccurate forecast data for some locations. This primarily affects locations in Europe, while locations in North America already default to AccuWeather, an alternative provider. If you notice inaccurate weather in your sources, you can switch to AccuWeather instead of WeatherAPI. We will provide an update as soon as WeatherAPI resolves this issue.
WeatherAPI has resolved its issues with inaccurate data being produced for some locations.
We're continuing to work on Page Manager and getting everything running smoothly. You can create and edit pages, but we have identified an issue where the contents of some folders may not appear. We aim to have this resolved as quickly as possible. Sorry for any inconvenience this has caused.
Thank you for your patience. Our work on Page Manager is complete, and we're continuing to monitor for any issues.
We're investigating an issue that is causing the Aiir CMS and customer websites to load slowly or, in some cases, fail to load. We're really sorry for any inconvenience this has caused. We will provide further updates as we have them.
We have identified the cause of the issue and rectified it. Affected sites should now be back online. We'll continue monitoring for further issues.
This incident has been resolved.
We are currently investigating reports of the Audio.co app being unable to load. Sorry for any disruption this has caused. We'll post a further update as soon as we have more information.
Access to the Audio.co app has been restored. We're currently investigating the cause and monitoring to make sure the service remains stable. Sorry for any disruption this issue has caused.
This incident has been resolved.
We've identified an issue with uploads to Media Manager, where it looks like files are getting stuck uploaded. Files are still being uploading, but you will need to refresh the page after some time to see it added. We're currently investigating why it isn't updating in real time with confirmation of your files being uploaded.
We're sorry for the issue today. Media Manager has been fixed and will now show the correct status for uploaded files.
We are currently investigating issues generating ads and newscasts. Sorry for any inconvenience this has caused.
Our team have identified the cause of the issue and have implemented a fix which means that generations should as expected.
We are currently investigating an issue which could prevent scheduled newscasts in Audio.co from generating.
Our product development team have investigated the issue and have deployed a fix. Newscasts should now be generating correctly.
We are currently investigating reports of connectivity issues affecting listeners located in the USA. This appears to be related to a specific region server, which may prevent streams from loading. Our initial testing indicates that services in other territories, including the UK, remain fully operational. We are working to restore service as quickly as possible.
This incident has been resolved.
We are currently investigating issues accessing the servers required to route LiveMIC audio to PlayoutONE. Sorry for any inconvenience caused.
We have identified the issue and deployed a fix which requires PlayoutONE's license to be updated via the internet from the Monitor app. You can do this by going to Monitor > Main Settings > License tab. Once your PlayoutONE license is refreshed, LiveMIC will operate as expected.
This has now been resolved. All PlayoutONE PCs will automatically update to the new LiveMIC settings within the next 12 hours (when the machines' PlayoutONE licenses next renew). If you need LiveMIC to be working more urgently, pressing 'Internet License' in Monitor should instantly update the setting. If you have any issues accessing LiveMIC and need assistance, please email [email protected].
Unfortunately, due to a server issue, LiveMIC connections may be temporarily unavailable. Our team has identified the cause and are working on a fix right now.
This incident has been resolved.
We are currently investigating an issue with audio generation on Audio.co
We're really sorry if you've received an email from Audio.co saying something failed to generate. Our team have dug into this, and it's turned out to be a false alarm. We've automatically marked some older newscasts that were labelled as "generating" but stuck in that state, as "failed". Unfortunately that's meant some emails have been sent out that didn't need to be, so we're sorry if we've filled up your inbox. Rest assured nothing is actually broken, and you shouldn't see any more of these now.
We've sent a follow-up email to affected users just to reassure that current newscasts are generating as normal. Sorry again for any inconvenience or undue concern caused.
We are currently investigating delays in processing incoming now playing metadata. Sorry for any inconvenience.
Now playing track data should shortly return to normal. Sorry for any inconvenience caused while it was processing slower than normal.
We are currently investigating an issue which is preventing the 'On-Air Now' information on certain elements of our products from updating. This includes websites and Alexa Skill welcome messages.
Our team are continuing to investigate the issue, and we have manually pushed an on-air information update, so websites should now display the correct show. That said, as the issue is still being looked into, show changes in the immediate future may not be reflected until the issue has been fully rectified.
We apologise for the disruption caused by the lack of on-air now updates on customer websites. We have fixed the problem with processes in the background not running successfully, and updates to the on-air display should now work successfully.
We are currently investigating reports of Audio.co Newscasts failing to generate. As soon as we have further information, we'll update this page with more. Sorry for any inconvenience caused.
We are continuing to investigate and monitor this. Sorry for any inconvenience caused.
We are continuing to work on this issue and monitor any failed generations. Thank you for bearing with us, and sorry for any inconvenience caused.
We've identified an earlier issue with a 3rd party service that handles importing RSS feeds for Audio.co. We're continuing to monitor this for further issues.
There have been no further reports of generation issues in the last few hours. We're continuing to monitor the situation and will update this post if any further issues occur. Thank you for bearing with us, and sorry for any inconvenience this has caused.
We've been monitoring this issue with no further newscast generation failures relating to this incident in the past few hours. Thank you for your patience, and sorry for any issues this has caused.
Some users may be unable to access Audio.co due to a wider issue with the infrastructure provider Cloudflare, with other sites also affected. The issues appear to be intermittent, with Cloudflare's team working to resolve them. Users who were using Audio.co before the outage should be able to continue unaffected, and scheduled newscasts should still be generated.
Cloudflare say they believe the issues have now been resolved. You can check for further information at https://www.cloudflarestatus.com/incidents/8gmgl950y3h7.
We’ve identified an issue in Scheduler where, if a log template is manually adjusted from its assigned scheduled clock, or if items are manually added to a log template, the resulting scheduled hour may become misordered. Our development team has reproduced the behaviour and is working on a fix. In the meantime, we recommend avoiding manual changes to log templates after clocks have been assigned, where possible.
Thank you for your patience regarding this issue. We have now pushed a fix for this to Scheduler. If you experienced misordered hours after manually adjusting a log template or adding items, you’ll need to revert the affected hours back to their scheduled clocks and reschedule to restore the correct order. Unfortunatley, unscheduling without reverting the customised hours to their scheduled clock will not correct the issue, as this retains the previously misordered data. We’ll continue monitoring this.
This incident has been resolved.
We're currently unable to respond to customer emails as quickly as we would like due to an upstream issue with our email communication service, which is affected by wide-ranging Amazon Web Services outages. We will endeavour to respond as soon as possible. Other services, including our off-air emergency line is unaffected.
This incident has been resolved.