Static Routes No Longer Working Properly

Occasionally I have to set up a lab environment for testing and in the past I used static routes configured on the Comcast supplied Netgear firewall/modem to all access to the various lab subnets. I haven’t had to use the lab environment for several months and discovered that traffic using the static routes is now unreliable where it used to flow as expected.

Was there a firmware update that negatively impacted static routes? I saw another post that the static route functionality on the Comcast Cisco BWG was not working.

If I add a static route on a Windows box sitting on the 10.1.10.0 network to use 10.1.10.200 as the gateway for my lab subnets, traffic flows fine. When I use the Netgear device to route the traffic, traffic flow is unreliable.

My configuration is:
10.1.10.0/24 network hanging off Netgear device => Router (10.1.10.200) => various subnets (ie 10.1.50.0/24, 10.1.60.0/24, 10.1.70.0/24)

Netgear static routes:
Name   Destination IP   Subnet Mask   Gateway IP
10.1.50.0   10.1.50.0   255.255.255.0   10.1.10.200
10.1.60.0   10.1.60.0   255.255.255.0   10.1.10.200
10.1.70.0   10.1.70.0   255.255.255.0   10.1.10.200

This is what I get when using static routes on the Netgear device:
Pinging 10.1.50.10 with 32 bytes of data:
Reply from 10.1.50.10: bytes=32 time=1ms TTL=127
Request timed out.
Request timed out.
Request timed out.
Reply from 10.1.50.10: bytes=32 time=1ms TTL=127
Reply from 10.1.50.10: bytes=32 time=1ms TTL=127
Request timed out.
Reply from 10.1.50.10: bytes=32 time=1ms TTL=127
Request timed out.
Reply from 10.1.50.10: bytes=32 time=1ms TTL=127
Reply from 10.1.50.10: bytes=32 time=1ms TTL=127
Request timed out.

Thanks