It kind of is. Well, the public dinging probably isn't. But at a few companies I've seen, teams are tracked on how many tickets span multiple sprints. If it exceeds some threshold, then theoretically it means that either:
1. The team is not breaking down tasks granularly enough, or
2. They're not estimating tasks correctly
The scrum guide [1] says team gives a forecast and not a commitment. I have yet to know any other scrum practitioners aware of that update.
Unless a person has no shame, failing a commitment I certainly believe is intrinsically shameful. Some cultures would commit seppuku if you don't deliver on a commitment.
The words, "you failed on your commitments" seems very much like shaming. Thus the move to "forecast" over "commitment"
*edit (addendum): Invoking 'seppuku' might be a bit sensationalist, my apologies. The southerner in me is coming out - saying someone does not live up to their word is a very big deal.
Practically, it means nothing of course.