Some customers may have noticed misleading channel counts during this window as forewarned, and as a result channel limits may not have been enforced correctly. We're also aware a small number of customers saw some calls rejected due to channel limits, where they were unable to burst beyond their allocation, we apologise for any inconvenience this caused. Once this was identified, enforcement of limits was temporarily suspended.
Posted about 1 year ago. Jul 14, 2018 - 12:34 UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted about 1 year ago. Jul 14, 2018 - 08:12 UTC
We are planning upgrades to our Redis cluster, and undertaking further resilience testing on the changes deployed in recent maintenance similar to those previously announced in April.
We have scheduled this when the network is quietest, and are confident this is very unlikely to affect production voice traffic but may impact statistics displayed in the portal or retrieved via the API, additionally there is a small chance that channel and rate limits will not work as expected during this time. In the event that our limiting experiences issues we operate on a 'fail safe' basis where our platform will disregard channel limits, ensuring calls complete, rather than limit calls based on out of date information about current use.
As a precaution, services should be considered AT RISK during this maintenance window.
Posted about 1 year ago. Jul 09, 2018 - 11:16 UTC
This scheduled maintenance affected: Availability Zones (London, Slough, Manchester) and API and Portal.