Contact us
  • AS Relation Model

    Our portal represents various analytical data regarding the relation types between autonomous systems (AS). For each AS we openly display its current links as well as the dynamics of their changes. This information is updated daily.

  • Radar Monitor

    Our monitoring system allows detection of a wide range of network anomalies which may have a significant impact on the end-point network resource availability. Currently we provide the information about detected static and dynamic routing cycles, Route Leaks, DDoS amplifiers and bots. The details on the detected incidents are available for technical representatives of the given AS.

  • Reverse LG

    Reverse LG is an exclusive network tool for determining the route which will be used by any other AS in order to reach your AS depending on the given routing policy. This tool is implemented using the modeling of inter-AS relations and priorities on all levels of BGP decision-making.

  • AS Rating

    In order to simplify the process of comparing different AS our portal provides a set of ratings which let the user perform comparisons by various parameters. For user convenience we have added the search function which makes evaluation of a certain AS in the list a lot easier.

Blog

December 13th, 2017

Born to Hijack

New ISPs emerge every day, and 12 December was not an exception. A new interdomain routing ecosystem actor, AS39523 (DV-LINK-AS) started announcing its address space (one prefix), while at the same time this new network hijacked 80 high profile prefixes. The hijacked prefixes belonged to both Russian and International content providers such as Google, Facebook, Microsoft, Mail.ru, Vkontakte and many more.

READ MORE →
November 17th, 2017

No-no-no-export!

On November 7, 2017, a bunch of blogs wrote about a route leak created by Level3 that affected a significant amount of users. Route leaks happen all the time, and we persistently monitor them all around the world. Except for the mentioned one, which was not detected by our system. So, for Qrator.Radar team it was vital to get into details of this particular incident and understand why our detectors missed this one. We decided to look into it, but this incident analysis took us some time. However, here's the result.

READ MORE →
LOGIN
×
Contact us
×
Type:
Email:
Subject:
Message:

Thank you for feedback!

We will contact you by provided email address.