This incident has been resolved.

The offending deployment has been rolled back. This was only a presentation issue; all affected shipments' trackers were actually created correctly and their IDs can be retrieved by fetching the shipment object from our API.

Engineers have identified another presentation issue causing the tracker ID to be absent on some newly-created shipments and are reverting the problematic deployment.