validating reachability via an ISP

Wed Apr 4 23:04:58 UTC 2018

Hi Alex,
  Thanks for the link to the qrator API.  The get-all-paths is interesting
and the output does seem to show exactly the type of data I'm looking for.
Is there some place on the site that lists who Qrator peers with to get
your data?  I searched through the site and couldn't find it.  I'm trying
to get an idea of the breadth of data and whether i can comfortably rely on
it giving me a global view.

Also, how do I authorize programmatic requests to the API?  I created a
user and can use it to run the queries from the web page, but I don't see
how to use it directly with the API.

thanks!
 -andy

On Thu, Mar 29, 2018 at 8:23 AM, Alexander Azimov <aa at qrator.net> wrote:

> Hi Andy,
>
> You can use Qrator.Radar API: https://api.radar.qrator.net/.
> The get-all-paths method will return the set of active paths for selected
> prefix.
>
> PS: I'm sorry if you receive this message two times, something funny is
> happening with my emails on NANOG mailing list.
>
> 2018-03-29 18:09 GMT+03:00 Alexander Azimov <aa at qrator.net>:
>
>> Hi Andy,
>>
>> You can use Qrator.Radar API: https://api.radar.qrator.net/.
>> The get-all-paths method will return the set of active paths for selected
>> prefix.
>>
>>
>> 2018-03-29 2:22 GMT+03:00 Andy Litzinger <andy.litzinger.lists at gmail.com>
>> :
>>
>>> Hi all,
>>>   I have an enterprise network and do not provide transit. In one of our
>>> datacenters we have our own prefixes and rely on two ISPs as BGP
>>> neighbors
>>> to provide global reachability for our prefixes.  One is a large regional
>>> provider and the other is a large global provider.
>>>
>>> Recently we took our link to the global provider offline to perform
>>> maintenance on our router.  Nearly immediately we were hit with alerts
>>> that
>>> our prefix was unreachable and BGPMon alerted that nearly 80 AS's noted
>>> our
>>> route had been withdrawn.  We were not unreachable from every AS, but we
>>> certainly were from some of the largest.
>>>
>>> The root cause is that the our prefix is not being adequately
>>> re-distributed globally by the regional ISP.  This is unexpected and we
>>> are
>>> working through this with them now.
>>>
>>> My question is, how can I monitor global reachability for a prefix via
>>> this
>>> or any specific provider I use over time?  Are there various
>>> route-servers
>>> I can programmatically query for my prefix and get results that include
>>> AS
>>> paths? Then I could verify that an "acceptable" number of paths exist
>>> that
>>> include the AS of the all the ISPs I rely upon.  And what would an
>>> "acceptable" number of alternate paths be?
>>>
>>>
>>> thanks in advance,
>>>   -andy
>>>
>>
>>
>>
>> --
>> | Alexander Azimov  | HLL l QRATOR
>> | tel.: +7 499 241 81 92
>> | mob.: +7 915 360 08 86
>> | skype: mitradir
>> | mailto: aa at qrator.net
>> | visit: www.qrator.net
>>
>
>
>
> --
> | Alexander Azimov  | HLL l QRATOR
> | tel.: +7 499 241 81 92
> | mob.: +7 915 360 08 86
> | skype: mitradir
> | mailto: aa at qrator.net
> | visit: www.qrator.net
>