anchor.diff:  $ nats-server -d
   
   # Start gorouter
  -$ ./bin/router
  +$ ./bin/gorouter
   </pre>
   
   ## <a id='use'></a>Usage ##
   
  -The Gorouter receives route updates through [NATS](./messaging-nats.html). 
  -By default, routes that have not been updated in two minutes are pruned. Therefore, to maintain an active route, you must ensure that the route is updated at least every two minutes. 
  +Gorouter receives route updates through [NATS](./messaging-nats.html).
  +By default, routes that have not been updated in two minutes are pruned. Therefore, to maintain an active route, you must ensure that the route is updated at least every two minutes.
   The format of these route updates is as follows:
   
   ~~~json
  
positive.code: 
  ## <a id='instrumentation'></a>Instrumentation ##
  
  The Gorouter provides `/varz` and `/healthz` http endpoints for monitoring.
  
  The `/routes` endpoint returns the entire routing table as JSON. Each route has an associated array of `host:port` entries.
  
  All of the endpoints require http basic authentication, credentials for which you can acquire through NATS. You can explicitly set the `port`, `user` and password (`pass` is the config attribute) in the gorouter.yml config file `status` section.
  
  ~~~yaml
  status:
  
negative.code: 
  <strong><%= modified_date %></strong>
  
  Gorouter routes traffic coming into Cloud Foundry to the appropriate component,
  whether it is an operator addressing the [Cloud Controller](./cloud-controller.html)
  or an application user accessing an app running on a Diego Cell. Gorouter is
  implemented in Go.
  Implementing a custom Gorouter in Go gives Gorouter full control over every
  connection, which simplifies support for WebSockets and other types of traffic
  (for example, through HTTP CONNECT). A single process contains all routing logic,
  removing unnecessary latency.
  
  Refer to the following instructions for help getting started with Gorouter
  in a standalone environment.
  
  ## <a id='setup'></a>Setup ##
  