I was a network person before i changed disciplines.
A direct answer is no, that is not a lot of connections, in fact, it is trivial. What we don't know is any level of meaningful detail. If there were thousands of endpoints each making thousands of connections all at once, that changes the scale of the problem. Furthermore, most of the time, we assume that one host is trying to connect to another host. However, if those connection attempts were network broadcasts, that's a much bigger problem. A network broadcast is sent from one host to ALL hosts on a given network, and then they ALL respond. If all hosts on a network are sending broadcast frames endlessly, that will flood a network. It's the same concept as a denial of service attack; one host can initiate traffic that will exhaust resources, but takes very little resource to do it. Thusly it can cripple a network with very little need for power or bandwidth.
My guess is that they fucked up the config on the router and was passing traffic that it should not have or initiated traffic that it couldn't handle the responses from. It started using up all resources on itself and probably other network equipment and the whole thing shits the bed. Techs go around trying to reboot network gear, not sure where the problem is, the gear is overwhelmed and won't respond. They have to dick around with out-of-band management (does not use the clogged network for management, there is a separate network for management), try to reboot or do some diagnostics, but as soon as the network device comes back up, it's saturated again making diagnosis slow and painful. People panic, bosses start freaking out, more and more people are called in adding to confusion and now the first people to respond are not working, they're answering endless questions about what's going on, even though they don't really know yet. Vendors are called, contractors are called, calls spiral and fracture, bosses demand updates while people are guessing at what to do next because they aren't allowed to say "I don't know" when planes are in the air. Someone eventually looks at the change management records (you have to document any configuration changes before you do them) and finds the last thing that was touched before everything shit the bed. They go look at the config, see the fuckup, back it out to the last known good config and the shitstorm dies.
this is 100% speculation treat is as such.