Date: Fri, 29 Mar 2024 07:53:06 +0200 (SAST) Message-ID: <995821593.4370.1711691586913@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4369_1529073748.1711691586912" ------=_Part_4369_1529073748.1711691586912 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
INX operates two looking glass services that provide different views of = the INXes to the public. Every INX LAN has a Route Collector that eng= ages in peering with participants on the LAN, and we are able to provide a = view of what peering looks like from the perspective of the INX Route Serve= rs as well. Both these serve useful, and yet separate purposes, and u= sers of the service are encourage to ensure that understand the differences= .
The looking glass service is meant to be used to aid in debugging.  = ;Abuse of the service will not be tolerated.
An integrated web based looking glass which can be used for any of the I= NXes is available at:
This is built on Alice-lg, and provides an unfiltered view of routes tha= t are received by all peers. This is exceptionally useful if you want= to do a quick search across all of the INXes. &= nbsp;You are able to search based on ASN, route prefix, or peer ip address,= in an intuitive way that does need you to interpret syntax from any partic= ular vendor. The looking glass operates a 5min cache, that helps us t= o prevent abuse. Be aware that route queries may be slightly delayed,= but an intuitive timer, on the top right will alert you to when the next r= efresh is meant to happen.
This is a subset of the actual peers that are available at each of the I= NXes; ie. only peers that are actively peering with the route collect= ors in each of the INX locations, will be visible here
We also provide a more detailed (internal) view of what the state of eac= h of the BGP Route Servers looks like. This is available at
and is particularly useful to peers who want to:
Please take note of the essential difference; our route collectors= provide an unfiltered view of what all peers are send us. The route = server view, is a more operational view of the route servers at each IX!
Additionally, Packet Clearing House also provide= a different and historic view into each of the INXes that they connect to.=
The Routeviews Project also runs a route collector at JINXand CI= NX which can be queried in various ways.