As someone who still lives in the suburbs of munich, I want to emphasize on the horrible public transportation situation in munich. It's always under construction, nothing really works and, as soon as there is some Public Event, everything breaks down.
The Players without Internet access are not affected. The system goes into a bootloop after that, even after disconnecting from the net. So something is apparently changed on the device. Maybe a temp/log file is filled with exceptions and the disk is now full.
Here is a more recent post with benchmarks of different GUID algorithms in SQL Server, the author has a different outcome.
In his benchmarks about index fragmentation, COMBGuid is not really much better than normal GUIDs.
http://microsoftprogrammers.jebarson.com/benchmarking-index-...
It does look like the sequencial ids (not the combs) does about 50% better overall, and the comb from nhibernate does about 10% better than just random uuids .. this is in terms of paging and indexes.. total time to run the test isn't bad, but that's just the insert time. If you're generating from your application layer and storing in SQL Server, looks like the best option is UuidCreateSequential.
Yeah, that's my impression too, you need to pat them very very dry, which might take time if you sear them directly from e.g. a sous vide bag. I still use it to sear single steaks, because the fire alarm is a bit overzealous and the searzall creates less smoke than a Cast Iron skillet.