NTA - Notice history

RFO 29.07.22

Due to an inordinate amount of BGP traffic we took emergency action to force a reboot of one of the routers. This had a very little detrimental effect on service because of the re-route capabilities we instigated ahead of this maintenance window. All services were resumed without any major outage.

The issue identified on 29.07.22 is now resolved a full RFO will be issued on Monday 01.08.22

The network is now operational and stable with all services returning to normal. However, we will continue to monitor before issuing an RFO following a thorough investigation,

We have restarted the router and currently monitoring the result. Services have returned to normal

Maintenance will begin in 15 minutes

Emergency Maintenance

We have scheduled a reboot of our systems to clear any excess load on them. This has been planned for 18:30 tonight. We are expecting this to take our service offline temporarily as the system reboots and comes back up. Please be aware of this if you are making calls during this time. We are advising that the maintenance will take 30 minutes. Service will be resumed by 19:00. We will send another update 30 minutes before maintenance begins.

Emergency Maintenance The issue has been identified within our network, we are currently working to resolve the issue. If you notice your device registration dropping, please reboot the device.

RFO: 16/07/22

At 00:40 on the 16th of July, we were alerted to the network having issues which lead to a total loss of service. At this time our team began investigating the issue. We identified the issue to be an equipment failure based at our THN data center. The equipment was brought back into service and service was fully restored at 06:30. We have scheduled further maintenance to upgrade existing equipment at THN, to enhance network resilience.

The issue was fixed by 6:30 and our monitoring systems confirms that everything is working fine. An RFO will be released ASAP.

We implemented a fix and currently monitoring the result.

RFO 27/06/22

Whilst investigating the root cause of last week's faulty flapping link, the link was accidentally brought into service by our upstream suppliers and caused the issues to re-occur.

This was identified and quickly removed from service again and service restored.

However, as a result of restoring everything to a normal operating situation, a further shutdown was implemented to enable full functionality services to resume.

We are working closely with our suppliers to make sure changes are never implemented, or any attempts to do so happen during an investigation, that may interfere with the normal operation of our services during normal working hours unless specifically instructed.

This will only be in the case where it would be operationally critical.

Any network changes will continue to be scheduled and notifications sent as per our normal procedure

We just resolved the issue!

We implemented a fix and currently monitoring the result.

Whilst investigating the cause of last week's faulty flapping link, the link was accidentally brought into service by our upstream suppliers and caused the issues to re-occur. This was removed from service again and service restored. We are still seeing some issues with calls made during the outage being "Stuck" we are working on this issue.

We are seeing more instances of service affecting issues with inbound and outbound calls, we are continuing to investigate this situation and work to bring service back.

Whilst investigating the cause of last week's faulty flapping link, the link was accidentally brought into service by our upstream suppliers and caused the issues to re-occur. This was removed from service again and service restored. We are still seeing some issues with calls made during the outage being "Stuck" we are working on this issue.

RFO 16/06/22

We became aware of a number of issues affecting us and many other providers too. This had an impact on our service and therefore we took emergency action to mitigate the ongoing issues. We engaged our Disaster Recovery system and rerouted in excess of 8500 inbound calls each with a duration greater than 10 seconds. To alleviate the issues we disabled our hosted platform and BLF notifications temporarily, which enabled outbound and internal calls to be made. Once we were confident the issues were resolved we fully restored our services.

An example of a couple of issues from suppliers:- DWS:- Dear partner, Hi To advise many services were affected today by an issue with a peering company lumin/lvl3. This is a peering partner who deals with hand-off traffic to the wider net for many suppliers. Between 13:15 and 13:45 there was a period of no traffic passing over their network. This was resolved by passing peering traffic to a different peer partner. This is not a DWS specific issue and likely affected multiple suppliers within the UK.

June 16: Problems at BT (British Telecom) BT (British Telecom) is having issues since 09:00 AM GMT. Are you also affected? Leave a message in the comments section! We apologise for any inconvenience caused.

All services have now returned to normal and an RFO will be issued tomorrow after further in-depth investigation.

We have now restored service to the portal and BLFs. We are continuing to monitor and investigate the issues that led to today's outage.

We have re-established inbound calls, some services such as the portal and BLF's are still disabled as we continue to monitor the issue. We will continue to provide updates as these services are re-established.

To advise many services were affected today by an issue with a peering company lumin/lvl3.

This is a peering partner who deals with hand-off traffic to the wider net for many suppliers. We cannot confirm this is the reason for our outage, but we are led to believe it has had an effect.

We are continuing to monitor this issue, outbound and internal calls should be fine. Inbound calls are still being routed via disaster recovery to help reduce load. We have also temporarily disabled BLFs.

We are continuing to slowly restore services and keeping the load on our servers low in order to ensure a stable recovery. You may notice some service restoring slowly, with the exception of the portal.

We are currently investigating this incident. You may experience calls intermittently working as we try to bring our service back.

The Web interface/portal has been temporarily disabled to reduce the load on our servers to enable calls to be re-established. Please note we went into full disaster recovery mode 25 minutes ago. We hope to have this issue resolved shortly.

We are pleased to announce that as of 20:30 on 19.05.22 that the issue that was affecting some of our broadband suppliers Global Switch location has been fully resolved. We again apologise for any inconvenience caused.

At 1pm

STREAM: Troubleshooting

• Isolate G52 Switch 2 from the Network - Completed

• G52 Switch 1 to be configured for core routing - Completed

• Bring up all LAN interfaces on G52 Switch 1 individually to return service - In Progress

Next Status:

• Bring up all the services/connections

• Pending vendor and KCOM investigation on the 2 CAS devices

Current Status: Most servers are now back online but we will keep monitoring until we get a FRO

An update from our supplier.

A major service outage has been detected at Global Switch affecting connectivity, internal systems and portals. Engineers are on route now to investigate

MobeX services are now back up and running and we will continue to look into the calls. We apologise for any inconvenience.

The broadband issue has now stabilised, however we will keep on monitoring the services and will update you with an RFO once we receive one