The 3DS Server refreshes its cache of participating card ranges, supported protocol versions and 3DS Method URLs from every DS it is registered with at least every 24 hours and at most hourly, sending the PReq over the mutually authenticated DS link, retrying immediately on a failed connection or handshake and, after a second failure, at 60-second intervals within the 24-hour window; the DS returns in the PRes only ranges participating in 3DS 2.0 or later and registered with it.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.