No credit card required · 30-day, full-feature trial · Free plan available
Overview
BGP (Border Gateway Protocol) is the routing protocol that determines how traffic moves across the internet. Every time a user visits your website, a BGP lookup maps your domain to an IP prefix and routes the request through a sequence of autonomous systems (AS) to reach your servers.
When that routing information is tampered with, misconfigured, or unstable, traffic can be misdirected, intercepted, or dropped — often without your web server signalling any problems.
Site24x7's BGP Route Monitor performs periodic BGP lookups for your configured domain and IP prefix, collects routing data from multiple global vantage points, and alerts your team the moment a hijack, leak, AS path change, or Resource Public Key Infrastructure (RPKI) failure is detected. This gives network administrators, ISPs, cloud providers, and enterprises the routing visibility their infrastructure monitoring alone can't provide.
Every feature you need
Site24x7 BGP monitoring tracks every routing change across your IP prefixes — hijacks, leaks, path changes, and RPKI failures — and delivers alerts with full diagnostic context before users are affected.
Detect when an unauthorized AS announces your IP prefix. This is the earliest signal of a BGP hijacking attack that could redirect your traffic to hostile infrastructures.
Identify when your prefix is propagated beyond its intended scope, catching downstream AS re-advertisements that expose your routing to unintended networks.
Verify that each route announcement has a valid Route Origin Authorization (ROA). RPKI-invalid routes signal that the originating AS is not authorized to announce your prefix.
Track the autonomous system (AS) sequence your route traverses. Unexpected path changes, such as new intermediaries, longer paths, divergent routes, surface network instability before users feel it.
Collect BGP routing data from multiple global internet vantage points simultaneously. A regional routing anomaly invisible from one vantage point will be immediately visible from others.
Enable auto-discovery to automatically find and monitor all IP prefixes associated with your domain. You can also configure specific prefix-to-Origin AS mappings for granular control over validation.
Get started
No probe to install. No complex BGP configuration required. Your first route monitor is live before your coffee gets cold.
Sign up for free. No credit card required. Activate your 30-day, full-feature trial and access BGP monitoring from day one.
Navigate to Admin > Add Monitor > BGP Route. Enter your domain name and set your check frequency (minimum five minutes).
Enable auto-discovery to monitor all prefixes automatically, or configure specific IP prefix Origin AS mappings for validation control.
Add contacts via Slack, PagerDuty, SMS, or email. You'll be the first to know the moment a hijack, leak, or path change is detected.
Use cases
BGP routing failures are invisible to web server monitoring, infrastructure dashboards, and uptime checks. Here's where BGP monitoring makes the difference.
An enterprise's customer portal has its prefix expected to originate from AS64500. Due to an ISP misconfiguration, the prefix is advertised from a different AS that causes slow or intermittent connectivity for some users. Because the web server itself remains healthy, no infrastructure alert fires. Site24x7 detects the Origin AS change and alerts administrators before the issue reaches more users.
A downstream AS re-advertises a prefix it should only be using locally, propagating your route to networks beyond its intended scope. Traffic destined for your infrastructure starts taking unexpected paths, introducing latency and potential interception risk. Standard latency monitoring sees the slowdown. Only BGP monitoring sees why.
A route announced by an AS doesn't have a valid Route Origin Authorization (ROA) for your prefix. RPKI-invalid routes indicate either an unauthorized Origin AS or an expired or misconfigured ROA — both of which can be early indicators of routing manipulation or infrastructure misconfiguration requiring immediate investigation.
Your organization announces prefixes through multiple Autonomous System Numbers (ASNs). These are provider-owned or leased ASNs that differ from your primary registered ASN. Site24x7 reports the configuration mismatch, prompting administrators to acknowledge whether the ASN is legitimate or configure the correct prefix-to-ASN mappings to distinguish valid routing from unauthorized announcements.
Site24x7 vs. alternatives
Site24x7 combines BGP route monitoring with full-stack DEM so routing anomalies are correlated with user experience data, not tracked in isolation.
| Comparison criteria | Site24x7 Best fit | Generic BGP tools | Tools that offer network monitoring only |
|---|---|---|---|
| BGP hijack detection | Included | Included | — |
| Route leak detection | Included | Included | — |
| RPKI validation | Included | Varies | — |
| AS path change tracking | Included | Included | — |
| Auto-prefix discovery | Included | Varies | — |
| Correlated with website uptime | Included | — | Varies |
| Correlated with DNS monitoring | Included | — | Varies |
| Compared with ISP latency | Included | — | — |
| IT automation on threshold breach | Included | — | — |
| Slack, PagerDuty, or Microsoft Teams alerting | Included | Varies | Varies |
| 30-day free trial | Included | — | — |
What customers say
"With Site24x7 monitoring 24/7, 365 days a year, the manpower needed to monitor assets has significantly come down. That's helping us reduce total cost of investment across our infrastructure."
"60% of website issues are caught in advance, thanks to Site24x7. The visibility we get across network layers — things we wouldn't have noticed otherwise — has changed how our team responds to incidents."
Frequently asked questions
A BGP hijack occurs when an unauthorized autonomous system (AS) announces your IP prefix, potentially redirecting your traffic to unintended—and possibly hostile—infrastructure. BGP monitoring detects hijacks by comparing the observed Origin AS against the expected Origin AS configured for each prefix. When a mismatch is detected, an alert fires immediately with the unauthorized ASN, affected prefix, and vantage point data.
A route hijack is when an unauthorized AS claims ownership of your prefix by announcing it without authorization. A route leak is when a route is propagated beyond its intended scope. For example, a downstream AS re-advertising a prefix it should only use locally, exposing your route to networks that shouldn't receive it. Both can cause traffic misdirection; hijacks typically carry greater risk of interception while leaks typically introduce unexpected routing paths and latency.
RPKI (Resource Public Key Infrastructure) is a security framework that cryptographically validates the authorization of BGP route announcements. A Route Origin Authorization (ROA) confirms that a specific AS is authorized to announce a specific IP prefix. Site24x7 validates RPKI status on every BGP check—an RPKI-invalid route means an ROA exists but the announcing AS or prefix length doesn't match, which is a strong signal of unauthorized routing that warrants immediate investigation.
DNS monitoring validates that your domain resolves to the correct IP address and that record values haven't been tampered with. BGP monitoring validates that the IP prefix those addresses belong to is being announced by the correct autonomous system across the internet. Both layers can be compromised independently—a DNS hijack changes the record; a BGP hijack changes where that IP's traffic actually goes. Complete routing security requires monitoring both layers.
Yes, this is the primary value of BGP monitoring. Because BGP routing anomalies often manifest before application-layer failures, monitoring at the prefix level gives you an earlier warning signal than uptime checks. An Origin AS change, for example, may only affect some users initially as routing tables propagate across the internet. BGP monitoring detects the change at the moment of announcement typically before most users are affected, allowing your team to investigate and respond proactively.
AS path monitoring tracks the sequence of autonomous systems through which your route announcements travel to reach global vantage points. Unexpected AS path changes—such as new intermediaries, longer paths, or divergent routes observed from different vantage points—can indicate network instability, route flapping, or traffic being routed through unexpected providers. Frequent path changes may signal BGP instability that precedes a more significant routing event.
Site24x7 supports BGP check intervals starting at five minutes. The appropriate frequency depends on your organization's risk profile and the criticality of the monitored prefix. For example, revenue-critical prefixes and those belonging to organizations in high-risk sectors typically benefit from more frequent monitoring. All check results are logged with full vantage point data for historical analysis and incident review.
