> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview of MegaIX Features

> This help topic provides an overview of MegaIX features.

export const Gloss = ({term, anchor, langDir = 'en'}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Gloss -';
  if (typeof term !== 'string') {
    term = String(term);
  }
  if (typeof anchor !== 'string') {
    anchor = String(anchor);
  }
  if (!term || term === 'undefined') {
    console.error(`${errorPrefix} the \`term\` property is required — rendering an empty string instead`);
    return <></>;
  }
  if (!anchor || anchor === 'undefined') {
    console.error(`${errorPrefix} the \`anchor\` property is required — rendering an empty string instead`);
    return <></>;
  }
  const lang = langDir === 'en' ? '/' : '/' + langDir + '/';
  const glossaryPage = lang + 'glossary/#' + anchor;
  return <a href={glossaryPage}>{term}</a>;
};

This topic provides an overview of key MegaIX features, including advanced tools for visibility, robust routing enhancements, and support for industry standards.

## MegaIX Looking Glass

The MegaIX Looking Glass provides full-featured visibility into traffic routing and the IX route server environment. This visibility helps you troubleshoot connections by searching for an AS number, a peer, or a particular IP prefix on the IX route server. For more information, see [MegaIX Looking Glass](/ix/megaix-looking-glass).

## Route server filtering

The <Gloss term="Resource Public Key Infrastructure (RPKI)" anchor="rpki" /> invalid routes are  filtered and are easy to identify using the Looking Glass. For more information about RPKI, see any of these helpful references:

* [Resource Public Key Infrastructure (RPKI)](https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/)
* [BGP Origin Validation](https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/bgp-origin-validation/)
* [Read the Docs RPKI Documentation](https://rpki.readthedocs.io/en/latest/)
* [RFC 8210](https://tools.ietf.org/html/rfc8210/)

## Peer AS-SET

The Peer AS-SET option is enabled for all connections. This value defines the AS macro filter for the peer. Megaport uses it to generate a list of prefixes and origin AS values that an AS can originate, and this list filters announcements through the route server.

## Large BGP community support

The upgraded route servers support an [extended range of action communities](/ix/communities) that Megaport IX route servers are able to recognize. As part of this, the [EURO-IX Large BGP Community](https://www.euro-ix.net/en/forixps/large-bgp-communities/) standard is also supported. Megaport recommends migrating to these communities.

<Note>
  MegaIX communities will be supported for 12 months before they are deprecated by Megaport.
</Note>

## BFD support

The route server upgrade passively enables the Bidirectional Forwarding Detection (BFD) protocol on route servers in all Megaport IX locations with a 300 millisecond interval. The BFD protocol detects any path failures between BGP neighbors.

## BGP Add Path

IX supports the BGP add-path feature to enable advertisements of multiple paths to a single address prefix, without the new paths implicitly replacing any previous paths.

Add-path support provides:

* Optimal routing and routing convergence in a network by providing potential alternate or backup paths.
* BGP traffic load balancing across more than one path.

For more information, see [Advertisement of Multiple Paths in BGP](http://tools.ietf.org/html/rfc7911/).

<Note>
  Your network must support BGP add-path functionality to benefit from its features.
</Note>

## IX Telemetry

You can use IX Telemetry page to view and analyze your network traffic flow statistics, check whether a peer is using a lot of network traffic, and diagnose and troubleshoot any configuration or networking issues.

For more information, see [IX Telemetry](/ix/ix-telemetry).