BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2606:5f00:8000::/33
Announced exactly
- 2606:5f00:8000::/33AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:8000::
- Registry
- ARIN · Puerto Rico · Nov 10, 2011
- Delegated block
- 2606:5f00:: – 2606:5f00:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2606:5f00:9000::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9000::
- 2606:5f00:9001::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9001::
- 2606:5f00:9002::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9002::
- 2606:5f00:9003::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9003::
- 2606:5f00:9040::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9040::
- 2606:5f00:9041::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9041::
- 2606:5f00:9042::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9042::
- 2606:5f00:9043::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9043::
- 2606:5f00:9400::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9400::
- 2606:5f00:9401::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9401::
- 2606:5f00:9402::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9402::
- 2606:5f00:9403::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9403::
- 2606:5f00:9440::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9440::
- 2606:5f00:9441::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9441::
- 2606:5f00:9442::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9442::
- 2606:5f00:9443::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:9443::
- 2606:5f00:a000::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a000::
- 2606:5f00:a001::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a001::
- 2606:5f00:a002::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a002::
- 2606:5f00:a003::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a003::
- 2606:5f00:a004::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a004::
- 2606:5f00:a005::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a005::
- 2606:5f00:a006::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a006::
- 2606:5f00:a007::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a007::
- 2606:5f00:a008::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a008::
- 2606:5f00:a009::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a009::
- 2606:5f00:a00a::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a00a::
- 2606:5f00:a00b::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a00b::
- 2606:5f00:a00c::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a00c::
- 2606:5f00:a00d::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a00d::
- 2606:5f00:a00e::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a00e::
- 2606:5f00:a00f::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a00f::
- 2606:5f00:a010::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a010::
- 2606:5f00:a011::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a011::
- 2606:5f00:a012::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a012::
- 2606:5f00:a013::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a013::
- 2606:5f00:a014::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a014::
- 2606:5f00:a015::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a015::
- 2606:5f00:a016::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a016::
- 2606:5f00:a017::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a017::
- 2606:5f00:a018::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a018::
- 2606:5f00:a019::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a019::
- 2606:5f00:a01a::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a01a::
- 2606:5f00:a01b::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a01b::
- 2606:5f00:a01c::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a01c::
- 2606:5f00:a01d::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a01d::
- 2606:5f00:a01e::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a01e::
- 2606:5f00:a01f::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a01f::
- 2606:5f00:a100::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a100::
- 2606:5f00:a101::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a101::
- 2606:5f00:a102::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a102::
- 2606:5f00:a103::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a103::
- 2606:5f00:a104::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a104::
- 2606:5f00:a105::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a105::
- 2606:5f00:a106::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a106::
- 2606:5f00:a107::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a107::
- 2606:5f00:a108::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a108::
- 2606:5f00:a109::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a109::
- 2606:5f00:a10a::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a10a::
- 2606:5f00:a10b::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a10b::
- 2606:5f00:a10c::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a10c::
- 2606:5f00:a10d::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a10d::
- 2606:5f00:a10e::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a10e::
- 2606:5f00:a10f::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a10f::
- 2606:5f00:a110::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a110::
- 2606:5f00:a111::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a111::
- 2606:5f00:a112::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a112::
- 2606:5f00:a113::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a113::
- 2606:5f00:a114::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a114::
- 2606:5f00:a115::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a115::
- 2606:5f00:a116::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a116::
- 2606:5f00:a117::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a117::
- 2606:5f00:a118::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a118::
- 2606:5f00:a119::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a119::
- 2606:5f00:a11a::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a11a::
- 2606:5f00:a11b::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a11b::
- 2606:5f00:a11c::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a11c::
- 2606:5f00:a11d::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a11d::
- 2606:5f00:a11e::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a11e::
- 2606:5f00:a11f::/48AS10396DATACOM CARIBE, INC.RPKI Not found2606:5f00:a11f::
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.