They are supported in all self-updating browsers, so unless you have to support IE<=10 they are safe to use and extremely convenient. Replacing a classic grid-based layout with flexbox saves an astonishing amount of markup. I've been using it exclusively for the last six months or so.
I found this CSSTricks article helpful when I was building my first flexbox layouts: https://css-tricks.com/snippets/css/a-guide-to-flexbox/
Most browsers are OK these days, but IE/Edge is where I've encountered the most problems with compatability. There are ways to work around it, but that takes a bit of additional effort. CSS tools, e.g., Autoprefix are useful.
My comment with browsers, is more about knowing your audience. Most of the evergreen browsers do support flexbox but...
Well, I maintain a website for a company.
97.3% of visitors, are return visitors.
69.77% of the visitors are using a version of Internet Explorer.
69.03% of the visitors are using Internet Explorer 7.0.
I have no hope of getting to use flexbox to simplify managing the website, which makes me very sad.
(By the way, I'm sympathetic with you. When I deployed a big feature in an intranet web application in 2012, it broke for dozens of users, and it took me days to track down the misplaced comma that broke the neck of the IE 7 JS parser.)
However, that particular site is Australian, where Chrome makes up ~50% of traffic.
However, that said, the majority of components I build are still not in flexbox. It's a useful tool in the toolset, but not sure I'd call it the new default yet.