Routing sanity check
BGP Prefix Health Check
Validate an IPv4 or IPv6 CIDR locally, review common routing risks, and open independent live BGP, RPKI, RDAP, and geolocation checks.
Client-side CIDR validation
Start with the prefix itself.
The local check never sends the prefix to LogicWeb. Live routing verification opens the selected independent service in a new tab.
Independent live checks
Verify routing, authorization, registration, and location.
After a valid prefix is entered, these links are populated for the external tools that support deep links. LogicWeb does not mirror or repackage their live datasets.
A healthy production prefix
Look for agreement across independent systems.
A route can be visible and still have problems. Check that the intended origin ASN, RPKI authorization, IRR route object, registry record, reverse DNS plan, and geolocation intent all agree with the production design.
- BGP: the intended prefix is visible from multiple networks.
- Origin: the ASN announcing the route is the ASN you expect.
- RPKI: the route is valid, or intentionally has no ROA while you finish setup.
- IRR: route/route6 objects match the intended origin where your carriers require them.
- WHOIS/RDAP: organization and reassignment records are consistent with the lease arrangement.
- Geolocation and rDNS: update them separately; BGP does not define either one.
IP operations toolkit
Keep working with the address space.
Use the other LogicWeb tools for pricing, planning, routing, and deployment.
Need a page for a specific prefix or workload? Browse the IP leasing guides.
From planning to production
Need a prefix with the routing paperwork handled?
LogicWeb publishes IPv4 /24 through /18 and IPv6 /48, /32, and /29 lease options with routing and registry support.