rtsak.com provides network operator tools for BGP routing analysis. Query AS numbers, examine announced prefixes, and validate route origins — essential for peering decisions, troubleshooting, and security monitoring.
Available Tools
AS Lookup
Query any Autonomous System for organization info, announced prefixes, upstream/downstream relationships, and routing policy. The starting point for understanding any network's internet presence.
BGP Routes
Examine BGP routing for a prefix. See the AS path, origin AS, and how routes propagate across the global routing table. Essential for troubleshooting reachability issues.
Prefix Origin
Validate who is announcing a prefix. Compare current announcements against expected origins to detect potential hijacks or misconfigurations.
Why RTSAK?
Operator-focused - Built for network engineers who need BGP data for real decisions, not curiosity. The interface prioritizes actionable information.
Current data - BGP routing changes constantly. Our data reflects recent routing table state, typically within minutes of changes.
Relationship visibility - See upstream providers, downstream customers, and peering connections. Understand how traffic flows through the internet.
Common Use Cases
Peering Decisions
- Evaluate potential peering partners
- Assess network size and customer base
- Identify common upstream providers
- Research IXP presence and connectivity
Troubleshooting
- Diagnose routing anomalies and blackholes
- Trace AS paths for unexpected latency
- Verify your own announcements are visible
- Check for route leaks or hijacks
Security Monitoring
- Detect unauthorized prefix announcements
- Monitor for BGP hijacking attempts
- Validate origin AS against ROA records
- Track changes to your prefixes
Capacity Planning
- Analyze traffic sources by origin AS
- Identify growth opportunities in peering
- Research competitor network topology
Understanding BGP Data
AS Path - The sequence of autonomous systems a route traverses. Shorter paths generally mean faster, more reliable connectivity.
Origin AS - The AS that originated (first announced) the prefix. Should match the prefix owner.
Transit vs Peering - Transit is paid upstream connectivity. Peering is mutual traffic exchange, often settlement-free.
Prefix Length - More specific prefixes (/24 vs /16) are preferred in routing. This is how BGP hijacks work.
Try It Now
Enter any AS number or IP prefix in the search box above, or explore these examples:
Related Tools
RTSAK focuses on BGP and routing. For other network tools:
- DNS Ninja - Fast DNS lookups including MX, SPF, and DKIM records
- RBLS - IP and domain reputation checking
- HashXP - Bitcoin and Lightning Network explorer