As this would be reasonably impactful of performance on busy servers, it would have to be designed for debug situations only. The idea is that we have a log specifically for TCP/IP debugging. In it would be written things like TCP session establishment, connection resets, adapter events, tcp window size change events, offload status, rss events, route changes, and a big one, MTU negotiation/black hole router events.

Get-netipconfiguration throws exception if you have multiple default gateways configured for an interface.

PS C:\Users\Administrator> Get-NetIPConfiguration

Exception setting "NetProfile": "Cannot convert the "System.Object[]" value of type "System.Object[]" to type
"Microsoft.Management.Infrastructure.CimInstance"."
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\NetTCPIP\NetIPConfiguration.psm1:201 char:17
+ ... $IPConfig.NetProfile = Get-NetConnectionProfile -Interfac ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (:) [], SetValueInvocationException

+ FullyQualifiedErrorId : ExceptionWhenSetting

InterfaceAlias : Ethernet0
InterfaceIndex : 4
InterfaceDescription : Intel(R) 82574L Gigabit Network Connection
IPv4Address : 172.16.110.222
IPv6DefaultGateway :
IPv4DefaultGateway : {12.12.12.12, 172.16.110.2}
DNSServer : 172.16.110.100