(Grieves might be a bit heavy of a word to use, so saddened works too—the concept is the same.)
Obviously this doesn't imply guilt.
If your most recent code breaks the company website, the correct response is probably "I'm on it - ETA of <x> mins/hours."
You could argue that an apology is redundant, although a post-mortem may be useful.
It's a difficult cultural issue, because it depends how avoidable show-stopper problems are.
The law doesn't fully distinguish between negligence caused by personal error; negligence caused by stress, distraction, or overwork; trivial error which may be magnified because of circumstances or other contributory factors; basic incompetence of one individual; basic incompetence of one or more other individuals which ends up being the problem of someone who isn't directly responsible (e.g. a site crashes because of an ancient bug buried in ancient code); and a series of extremely unlikely but unfortunate events.
Being explicit about it could help, but I agree my default inclination is also to assume it's an apology.