I know that you have stated that "this will be fixed in the next update", but I just wanted to make sure that you are completely aware of the entire issue. (I'm not saying that you aren't, but if what I am about to discuss is NOT what you fixed, then you will obviously have something else to fix with this the next time around.) If it is what you have already fixed, then simply disregard this message.
The SM-3 (RIM-161) comes in two variants The C-version which has a range of 200 miles, and the E version which has a range of 1275 miles.
Since the US doesn't have many ships that carry these missiles, and because they would likely be guarding a carrier or other HVU, it is safe to say that they would likely be very close by to any carrier group, if one was operating within close proximity to the enemy.
Regardless of which version you have, within 200 miles the ballistic missile has already begun its descent toward the targets and is already beneath the floor of the weapon's altitude. The RIM-161C (of which the US Navy has a lot more of than the E-version) only has a 200 mile range (as I stated), and with the descent already in progress, the RIM-161C can NEVER fire at the ballistic missile (a DF-21 or 26) because it is NEVER within the firing envelope within the game's programming. I have tested this for several days. Occasionally, you might get a spurious 1 or 2 second gap, but it is never long enough to fire. While the new method is probably much more realistic due to the accurate altitude range, it essentially renders the RIM-161C useless, unless it's on severe picket duty. This is a dramatic change from version 1147.16
The RIM-161E can shoot at targets greater than 200 miles, if another means is able to detect the ballistic missile from farther away. But, if it doesn't get a detection before the incoming missile gets within 200 miles, then the RIM-161E is no better off than the RIM-161C.
So, hopefully, when you said that it is "fixed for the next update" you are talking about this issue as being part of the fix. If so, then just disregard this message.
If not, please have a look at this aspect of the problem as well.