BGP Policy Monitoring – monitoring of specified routing policies at the BGP level. You can describe your routing policies and the system will notify you about their violations.
Step 1
The user describes what he wants to monitor in the routing
Step 2
We add rules to the configuration file
Step 3
The user is notified when the rules are triggered
User can construct desired monitoring policy based on next objects:
Geo
BGP attributes
Prefix Origin Validation Status
AS Relationships
Below are descriptions of the problems, how we can configure them and examples of alerts that will be sent to users.
You have configured presence on local IXs and don't. want to pay a lot for Tier-1 traffic, but routes have started to propagate through Tier-1. You will know about this before the service provider sends you an expensive payment order.
Prefixes with Invalid status began propagates. This means 2 things:
Problems:
Note: Also, you can use the Prefix Origin Validation Monitoring service for more information.
You have certain country resources/services, only for locals. but routes have started to propagate outside your country.
You will know immediately when one of our overseas observation points sees such a route.
Route Leaks caused by incorrect community processing, like global distribution of routes with NO_EXPORT community.
This is like the famous case that led to Pakistan's outage in 2008.
Changes in Routes
Sometimes it is important to know about all route changes between ASes of financial institutions, such as those involved in banking transactions. We can report about all AS paths changes.
Address
Czech Republic, Růžová 1416/17, Nové Město, 110 00 Praha 1
Contacts
Media contacts
2025 © Radar - All rights reserved