US 11,687,421 B1
Systems and methods for online brand continuity
David M. Niedzielski, San Antonio, TX (US); Christopher S. Trost, San Antonio, TX (US); Roger Pena, Atascosa, TX (US); Tommy Lavelle, San Antonio, TX (US); and Donald E. Clemons, San Antonio, TX (US)
Assigned to United Services Automobile Association (USAA), San Antonio, TX (US)
Filed by United Services Automobile Association (USAA), San Antonio, TX (US)
Filed on May 19, 2022, as Appl. No. 17/748,721.
Application 17/748,721 is a continuation of application No. 17/330,150, filed on May 25, 2021, granted, now 11,347,602.
Application 17/330,150 is a continuation of application No. 16/809,374, filed on Mar. 4, 2020, granted, now 11,042,455, issued on Jun. 22, 2021.
Application 16/809,374 is a continuation of application No. 15/954,394, filed on Apr. 16, 2018, granted, now 10,606,717, issued on Mar. 31, 2020.
Application 15/954,394 is a continuation of application No. 14/474,273, filed on Sep. 1, 2014, granted, now 9,990,259, issued on Jun. 5, 2018.
Application 14/474,273 is a continuation of application No. 12/046,155, filed on Mar. 11, 2008, granted, now 8,825,792, issued on Sep. 2, 2014.
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 15/16 (2006.01); G06F 11/20 (2006.01); H04L 67/1008 (2022.01); H04L 69/40 (2022.01); H04L 67/10 (2022.01); H04L 67/1021 (2022.01); H04L 67/1095 (2022.01); G06Q 30/02 (2023.01); G06F 16/58 (2019.01); H04L 67/104 (2022.01); H04L 67/1001 (2022.01); H04L 61/4511 (2022.01); H04W 88/12 (2009.01); G06F 16/954 (2019.01); G06F 16/958 (2019.01); H04L 67/1097 (2022.01)
CPC G06F 11/2023 (2013.01) [G06Q 30/02 (2013.01); H04L 67/10 (2013.01); H04L 67/1008 (2013.01); H04L 67/1021 (2013.01); H04L 67/1095 (2013.01); H04L 69/40 (2013.01); G06F 16/58 (2019.01); G06F 16/954 (2019.01); G06F 16/958 (2019.01); G06F 2201/805 (2013.01); G06F 2201/855 (2013.01); H04L 61/4511 (2022.05); H04L 67/1001 (2022.05); H04L 67/104 (2013.01); H04L 67/1097 (2013.01); H04W 88/12 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer system, comprising:
a first server hosting a first instance of an application within a first data center, the first server advertised via a single-host network internet protocol (IP) address of the first data center;
a second server hosting a second instance of the application within a second data center, the second server advertised via a multi-host IP address;
a router, configured to, via a border gateway routing protocol:
receive a request to access the application;
fulfill the request to access the application, by:
performing a health check on the first server;
routing the request to the single-host network IP address when the health check succeeds; and
otherwise, routing the request to the multi-host IP address when the health check fails.