BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2803:d700::/32
Announced exactly
- 2803:d700::/32AS61461Airtek Solutions C.A.RPKI Valid2803:d700::
- Registry
- LACNIC · Venezuela · Jun 18, 2013
- Delegated block
- 2803:d700:: – 2803:d700:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2803:d700:2000::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:2000::
- 2803:d700:7000::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:7000::
- 2803:d700:8100::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:8100::
- 2803:d700:8400::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:8400::
- 2803:d700:8500::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:8500::
- 2803:d700:8600::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:8600::
- 2803:d700:8a00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:8a00::
- 2803:d700:8e00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:8e00::
- 2803:d700:9000::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9000::
- 2803:d700:9200::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9200::
- 2803:d700:9300::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9300::
- 2803:d700:9400::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9400::
- 2803:d700:9500::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9500::
- 2803:d700:9600::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9600::
- 2803:d700:9700::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9700::
- 2803:d700:9800::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9800::
- 2803:d700:9900::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:9900::
- 2803:d700:a000::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:a000::
- 2803:d700:a300::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:a300::
- 2803:d700:a400::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:a400::
- 2803:d700:a500::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:a500::
- 2803:d700:a600::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:a600::
- 2803:d700:a700::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:a700::
- 2803:d700:a800::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:a800::
- 2803:d700:aa00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:aa00::
- 2803:d700:ab00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:ab00::
- 2803:d700:ac00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:ac00::
- 2803:d700:ad00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:ad00::
- 2803:d700:ce00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:ce00::
- 2803:d700:da00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:da00::
- 2803:d700:db00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:db00::
- 2803:d700:dc00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:dc00::
- 2803:d700:dd00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:dd00::
- 2803:d700:de00::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:de00::
- 2803:d700:e200::/40AS61461Airtek Solutions C.A.RPKI Valid2803:d700:e200::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.