Simwood experienced a notice incident on June 19, 2020 affecting Voice, lasting 45m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 19, 2020, 12:17 PM UTC
We're seeing traffic on our bilateral interconnects with Vodafone operating at about 10% of normal levels and hearing widespread reports of issues on the Vodafone network. This is not a Simwood issue and is off-net, but will be affecting a large proportion of calls. We have mitigated on-net as far as possible and will update with any resolution by Vodafone.
- identified Jun 19, 2020, 12:37 PM UTC
We're now seeing 0% of normal traffic to and from Vodafone destinations. This issue appears to have started at 13.07BST and is ongoing.
- identified Jun 19, 2020, 12:51 PM UTC
Vodafone operated services such as 101 are not available as part of this incident. 101 is the non-emergency contact number for any police force in England and Wales and it is available 24 hours a day, 7 days a week
- identified Jun 19, 2020, 01:01 PM UTC
We're now seeing a low level of calls to/from Vodafone completing.
- identified Jun 19, 2020, 01:06 PM UTC
Our interconnects with Vodafone in London and Manchester are back passing calls, but we see those in Leeds still down. Traffic is running at about 40% now.
- identified Jun 19, 2020, 01:13 PM UTC
Our Leeds interconnects are now passing traffic and they are restoring to normal levels.
- identified Jun 19, 2020, 01:30 PM UTC
Our outbound traffic directly to Vodafone is now at elevated levels (suggesting issues elsewhere still) but we're only seeing about 15% of the usual levels of inbound traffic from the Vodafone network.
- identified Jun 19, 2020, 01:43 PM UTC
Inbound volumes have now normalised and things look much better from here across all our Vodafone interconnects. We are still seeing elevated volumes of outbound traffic directly to Vodafone, which could illustrate issues elsewhere still.
- monitoring Jun 19, 2020, 01:44 PM UTC
We are continuing to monitor this.
- resolved Jun 19, 2020, 02:29 PM UTC
This incident has been resolved.