Below is a list of the possible ROUTE_STATUS properties along with an explanation of the terms:
The net is fully placed and routed.
All pins and/or ports for the net are placed and some of the net is routed, but portions of the net are unrouted and route_design should be run.
The route has some unplaced pins or ports, and place_design should be run to complete the placement.
All pins and/or ports for the net are placed, but no route data exists on the net, and route_design should be run to complete the route.
The entire route is completed within the same Site on the target device, and no routing resources were required to complete the connection. This is not an error.
The route either has no logical loads, or has no routable load pins, and so needs no routing. This is not an error.
The route either has no logical driver, or has no routable driver, and so needs no routing. This is a design error.
The route is connected to a top-level hierarchical port that either has no routable loads or no routable drivers. This is not an error.
The route has at least one antenna (a branch leaf that connects to a site pin, but that site pin does not show that it is connected to this logical net) or the route has at least one island (a section of routing that is not connected to any of the site pins associated with the logical net). This is a routing error.
The router has one or more routing conflicts. Please see (Xilinx Answer 56423) for a list of possible routing conflicts:
There was an internal error in determining the route status.
The net object specified for route status does not exist, or could not be found as entered.
No routing object could be retrieved for the specified net due to an error.
No route storage object is available for this device due to an error.
The state of the route cannot be calculated due to an error.