BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2610:b0::/33
Announced exactly
- 2610:b0::/33AS3573Accenture LLPRPKI Valid2610:b0::
- Registry
- ARIN · United States · Jul 28, 2006
- Delegated block
- 2610:b0:: – 2610:b0:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
- 2610:b0::/32AS3573Accenture LLPRPKI Valid2610:b0::
More-specific routes
- 2610:b0:300::/40AS3573Accenture LLPRPKI Valid2610:b0:300::
- 2610:b0:400::/40AS3573Accenture LLPRPKI Valid2610:b0:400::
- 2610:b0:2020::/44AS3573Accenture LLPRPKI Valid2610:b0:2020::
- 2610:b0:2060::/44AS3573Accenture LLPRPKI Valid2610:b0:2060::
- 2610:b0:4006::/47AS3573Accenture LLPRPKI Valid2610:b0:4006::
- 2610:b0:4006::/48AS3573Accenture LLPRPKI Valid2610:b0:4006::
- 2610:b0:4007::/48AS3573Accenture LLPRPKI Valid2610:b0:4007::
- 2610:b0:400e::/47AS3573Accenture LLPRPKI Valid2610:b0:400e::
- 2610:b0:400e::/48AS3573Accenture LLPRPKI Valid2610:b0:400e::
- 2610:b0:400f::/48AS3573Accenture LLPRPKI Valid2610:b0:400f::
- 2610:b0:4032::/47AS3573Accenture LLPRPKI Valid2610:b0:4032::
- 2610:b0:4032::/48AS3573Accenture LLPRPKI Valid2610:b0:4032::
- 2610:b0:4033::/48AS3573Accenture LLPRPKI Valid2610:b0:4033::
- 2610:b0:403a::/47AS3573Accenture LLPRPKI Valid2610:b0:403a::
- 2610:b0:403a::/48AS3573Accenture LLPRPKI Valid2610:b0:403a::
- 2610:b0:403b::/48AS3573Accenture LLPRPKI Valid2610:b0:403b::
- 2610:b0:4070::/47AS3573Accenture LLPRPKI Valid2610:b0:4070::
- 2610:b0:4082::/47AS3573Accenture LLPRPKI Valid2610:b0:4082::
- 2610:b0:4082::/48AS3573Accenture LLPRPKI Valid2610:b0:4082::
- 2610:b0:4083::/48AS3573Accenture LLPRPKI Valid2610:b0:4083::
- 2610:b0:4084::/48AS3573Accenture LLPRPKI Valid2610:b0:4084::
- 2610:b0:4085::/48AS3573Accenture LLPRPKI Valid2610:b0:4085::
- 2610:b0:4086::/47AS3573Accenture LLPRPKI Valid2610:b0:4086::
- 2610:b0:4086::/48AS3573Accenture LLPRPKI Valid2610:b0:4086::
- 2610:b0:4087::/48AS3573Accenture LLPRPKI Valid2610:b0:4087::
- 2610:b0:408a::/47AS3573Accenture LLPRPKI Valid2610:b0:408a::
- 2610:b0:408a::/48AS3573Accenture LLPRPKI Valid2610:b0:408a::
- 2610:b0:408b::/48AS3573Accenture LLPRPKI Valid2610:b0:408b::
- 2610:b0:408e::/48AS3573Accenture LLPRPKI Valid2610:b0:408e::
- 2610:b0:408f::/48AS3573Accenture LLPRPKI Valid2610:b0:408f::
- 2610:b0:4098::/47AS3573Accenture LLPRPKI Valid2610:b0:4098::
- 2610:b0:4098::/48AS3573Accenture LLPRPKI Valid2610:b0:4098::
- 2610:b0:4099::/48AS3573Accenture LLPRPKI Valid2610:b0:4099::
- 2610:b0:40a0::/48AS3573Accenture LLPRPKI Valid2610:b0:40a0::
- 2610:b0:40a1::/48AS3573Accenture LLPRPKI Valid2610:b0:40a1::
- 2610:b0:40a8::/47AS3573Accenture LLPRPKI Valid2610:b0:40a8::
- 2610:b0:40aa::/47AS3573Accenture LLPRPKI Valid2610:b0:40aa::
- 2610:b0:40aa::/48AS3573Accenture LLPRPKI Valid2610:b0:40aa::
- 2610:b0:40ab::/48AS3573Accenture LLPRPKI Valid2610:b0:40ab::
- 2610:b0:40b2::/48AS3573Accenture LLPRPKI Valid2610:b0:40b2::
- 2610:b0:40b3::/48AS3573Accenture LLPRPKI Valid2610:b0:40b3::
- 2610:b0:40b8::/47AS3573Accenture LLPRPKI Valid2610:b0:40b8::
- 2610:b0:40b8::/48AS3573Accenture LLPRPKI Valid2610:b0:40b8::
- 2610:b0:40b9::/48AS3573Accenture LLPRPKI Valid2610:b0:40b9::
- 2610:b0:40ba::/47AS3573Accenture LLPRPKI Valid2610:b0:40ba::
- 2610:b0:40ba::/48AS3573Accenture LLPRPKI Valid2610:b0:40ba::
- 2610:b0:40bb::/48AS3573Accenture LLPRPKI Valid2610:b0:40bb::
- 2610:b0:40c0::/47AS3573Accenture LLPRPKI Valid2610:b0:40c0::
- 2610:b0:40c0::/48AS3573Accenture LLPRPKI Valid2610:b0:40c0::
- 2610:b0:40c1::/48AS3573Accenture LLPRPKI Valid2610:b0:40c1::
- 2610:b0:40c8::/47AS3573Accenture LLPRPKI Valid2610:b0:40c8::
- 2610:b0:40c8::/48AS3573Accenture LLPRPKI Valid2610:b0:40c8::
- 2610:b0:40c9::/48AS3573Accenture LLPRPKI Valid2610:b0:40c9::
- 2610:b0:40ca::/47AS3573Accenture LLPRPKI Valid2610:b0:40ca::
- 2610:b0:40ca::/48AS3573Accenture LLPRPKI Valid2610:b0:40ca::
- 2610:b0:40cb::/48AS3573Accenture LLPRPKI Valid2610:b0:40cb::
- 2610:b0:40ce::/47AS3573Accenture LLPRPKI Valid2610:b0:40ce::
- 2610:b0:40ce::/48AS3573Accenture LLPRPKI Valid2610:b0:40ce::
- 2610:b0:40cf::/48AS3573Accenture LLPRPKI Valid2610:b0:40cf::
- 2610:b0:40d0::/48AS3573Accenture LLPRPKI Valid2610:b0:40d0::
- 2610:b0:40d1::/48AS3573Accenture LLPRPKI Valid2610:b0:40d1::
- 2610:b0:40dc::/48AS3573Accenture LLPRPKI Valid2610:b0:40dc::
- 2610:b0:40dd::/48AS3573Accenture LLPRPKI Valid2610:b0:40dd::
- 2610:b0:40ec::/47AS3573Accenture LLPRPKI Valid2610:b0:40ec::
- 2610:b0:40ec::/48AS3573Accenture LLPRPKI Valid2610:b0:40ec::
- 2610:b0:40ed::/48AS3573Accenture LLPRPKI Valid2610:b0:40ed::
- 2610:b0:40f4::/47AS3573Accenture LLPRPKI Valid2610:b0:40f4::
- 2610:b0:4122::/48AS3573Accenture LLPRPKI Valid2610:b0:4122::
- 2610:b0:4123::/48AS3573Accenture LLPRPKI Valid2610:b0:4123::
- 2610:b0:4126::/47AS3573Accenture LLPRPKI Valid2610:b0:4126::
- 2610:b0:4126::/48AS3573Accenture LLPRPKI Valid2610:b0:4126::
- 2610:b0:4127::/48AS3573Accenture LLPRPKI Valid2610:b0:4127::
- 2610:b0:412c::/47AS3573Accenture LLPRPKI Valid2610:b0:412c::
- 2610:b0:412c::/48AS3573Accenture LLPRPKI Valid2610:b0:412c::
- 2610:b0:412d::/48AS3573Accenture LLPRPKI Valid2610:b0:412d::
- 2610:b0:4132::/47AS3573Accenture LLPRPKI Valid2610:b0:4132::
- 2610:b0:4132::/48AS3573Accenture LLPRPKI Valid2610:b0:4132::
- 2610:b0:4133::/48AS3573Accenture LLPRPKI Valid2610:b0:4133::
- 2610:b0:413e::/47AS3573Accenture LLPRPKI Valid2610:b0:413e::
- 2610:b0:4144::/47AS3573Accenture LLPRPKI Valid2610:b0:4144::
- 2610:b0:4144::/48AS3573Accenture LLPRPKI Valid2610:b0:4144::
- 2610:b0:4145::/48AS3573Accenture LLPRPKI Valid2610:b0:4145::
- 2610:b0:414a::/48AS3573Accenture LLPRPKI Valid2610:b0:414a::
- 2610:b0:414b::/48AS3573Accenture LLPRPKI Valid2610:b0:414b::
- 2610:b0:414e::/47AS3573Accenture LLPRPKI Valid2610:b0:414e::
- 2610:b0:414e::/48AS3573Accenture LLPRPKI Valid2610:b0:414e::
- 2610:b0:414f::/48AS3573Accenture LLPRPKI Valid2610:b0:414f::
- 2610:b0:4150::/47AS3573Accenture LLPRPKI Valid2610:b0:4150::
- 2610:b0:4150::/48AS3573Accenture LLPRPKI Valid2610:b0:4150::
- 2610:b0:4164::/47AS3573Accenture LLPRPKI Valid2610:b0:4164::
- 2610:b0:4164::/48AS3573Accenture LLPRPKI Valid2610:b0:4164::
- 2610:b0:4176::/47AS3573Accenture LLPRPKI Valid2610:b0:4176::
- 2610:b0:4176::/48AS3573Accenture LLPRPKI Valid2610:b0:4176::
- 2610:b0:4180::/47AS3573Accenture LLPRPKI Valid2610:b0:4180::
- 2610:b0:4180::/48AS3573Accenture LLPRPKI Valid2610:b0:4180::
- 2610:b0:4181::/48AS3573Accenture LLPRPKI Valid2610:b0:4181::
- 2610:b0:418c::/47AS3573Accenture LLPRPKI Valid2610:b0:418c::
- 2610:b0:418c::/48AS3573Accenture LLPRPKI Valid2610:b0:418c::
- 2610:b0:418d::/48AS3573Accenture LLPRPKI Valid2610:b0:418d::
- 2610:b0:4194::/47AS3573Accenture LLPRPKI Valid2610:b0:4194::
Showing the first 100.
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.