OV - Notice history

VFNL have resolved their incident, and we are not seeing any disruption.

VFNL have performed a failover and reboot of the Schiphol node and moved to Eindhoven as the primary. Alarms have cleared and root cause investigation is underway.

This incident has been resolved. We identified the root cause was a service had failed, however our automatic systems identified this and restarted the service, leading to the recovery. There was a brief period of intermittent access with a small surge in traffic following the restart. All services are operating as expected.

The services have recovered and we are monitoring. Root cause investigation is still ongoing

VodafoneNL have advised that this was a false alarm and there was no service impact. They experienced an issue with their test devices and this resulted in false alerts being generated.

Service has remained stable.

This incident has been resolved.

The development team has taken steps to resolve the issue and are now monitoring the queue.

The service has remained stable and we have observed no further issues. If you need an RFO, please raise a ticket through our support portal as normal.

We have completed lifting the throttling now and have confirmed with our upstream carriers that the limits are not being hit. We have seen a recovery in signalling, authentication and device connections. We will continue to monitor during the evening. If you are still seeing issues, please raise a ticket via our support portal as normal.

We observed a signalling storm causing congestion on certain parts of the network. We have applied throttling to reduce the impact and are seeing improvements on devices. We will continue to gradually lift the throttle to allow more traffic on.

We have released an upgrade to OVOne today to improve the latency of statistics and we do not expect to see a recurrence of the previous issues.

The statistics are now reporting correctly. The team is investigating if a retrospective fix is possible for the missing statistics. There is still the potential for this issue to reoccur in the coming days until a more permanent fix is implemented. We will continue to keep this issue updated.

We are continuing to investigate the lag with OVOne reporting on data sessions. We have confirmed this is an OVOne specific data reporting issue, the actual sessions and network performance is as expected.