BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2806::/28
Announced exactly
- Registry
- LACNIC · Mexico · Oct 6, 2010
- Delegated block
- 2806:: – 2806:f:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2806::/32AS6503Axtel, S.A.B. de C.V.RPKI Not found2806::
- 2806:0:100::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:100::
- 2806:0:400::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:400::
- 2806:0:401::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:401::
- 2806:0:402::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:402::
- 2806:0:403::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:403::
- 2806:0:404::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:404::
- 2806:0:405::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:405::
- 2806:0:406::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:406::
- 2806:0:407::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:407::
- 2806:0:408::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:408::
- 2806:0:409::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:409::
- 2806:0:40a::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:40a::
- 2806:0:40c::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:40c::
- 2806:0:40d::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:40d::
- 2806:0:40e::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:40e::
- 2806:0:40f::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:40f::
- 2806:0:410::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:410::
- 2806:0:413::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:413::
- 2806:0:417::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:417::
- 2806:0:419::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:419::
- 2806:0:41a::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:41a::
- 2806:0:41b::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:41b::
- 2806:0:41c::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:41c::
- 2806:0:41d::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:41d::
- 2806:0:41e::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:41e::
- 2806:0:41f::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:41f::
- 2806:0:421::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:421::
- 2806:0:422::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:422::
- 2806:0:500::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:500::
- 2806:0:5fd::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:5fd::
- 2806:0:5fe::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:5fe::
- 2806:0:8000::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:8000::
- 2806:0:8040::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:8040::
- 2806:0:80b0::/44AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:80b0::
- 2806:0:80c0::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:80c0::
- 2806:0:8100::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:8100::
- 2806:0:8140::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:8140::
- 2806:0:81b0::/44AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:81b0::
- 2806:0:81c0::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:81c0::
- 2806:0:8300::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:0:8300::
- 2806:1::/32AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1::
- 2806:1:200::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:200::
- 2806:1:201::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:201::
- 2806:1:202::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:202::
- 2806:1:203::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:203::
- 2806:1:204::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:204::
- 2806:1:205::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:205::
- 2806:1:207::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:207::
- 2806:1:208::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:208::
- 2806:1:209::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:209::
- 2806:1:20a::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:20a::
- 2806:1:20b::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:20b::
- 2806:1:20c::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:20c::
- 2806:1:20d::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:20d::
- 2806:1:20f::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:20f::
- 2806:1:210::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:210::
- 2806:1:213::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:213::
- 2806:1:214::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:214::
- 2806:1:215::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:215::
- 2806:1:216::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:216::
- 2806:1:217::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:217::
- 2806:1:218::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:218::
- 2806:1:21a::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:21a::
- 2806:1:21d::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:21d::
- 2806:1:21e::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:21e::
- 2806:1:21f::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:21f::
- 2806:1:221::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:221::
- 2806:1:222::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:222::
- 2806:1:247::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:247::
- 2806:1:300::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:300::
- 2806:1:301::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:301::
- 2806:1:308::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:308::
- 2806:1:310::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:310::
- 2806:1:320::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:320::
- 2806:1:400::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:400::
- 2806:1:7fc::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:7fc::
- 2806:1:8000::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:8000::
- 2806:1:8040::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:8040::
- 2806:1:80b0::/44AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:80b0::
- 2806:1:80c0::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:80c0::
- 2806:1:8100::/40AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:8100::
- 2806:1:8100::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:8100::
- 2806:1:8140::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:8140::
- 2806:1:81b0::/44AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:81b0::
- 2806:1:81c0::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:81c0::
- 2806:1:8200::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:8200::
- 2806:1:8240::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:8240::
- 2806:1:82b0::/44AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:82b0::
- 2806:1:82c0::/42AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:1:82c0::
- 2806:2::/32AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:2::
- 2806:3::/32AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3::
- 2806:3:100::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:100::
- 2806:3:101::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:101::
- 2806:3:102::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:102::
- 2806:3:103::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:103::
- 2806:3:104::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:104::
- 2806:3:105::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:105::
- 2806:3:106::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:106::
- 2806:3:107::/48AS6503Axtel, S.A.B. de C.V.RPKI Not found2806:3:107::
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, 193.166.0.0/15. 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.