bgpreport

Network · data from 2026-11-12

AS11097 EMPRESA BRASILEIRA DE PESQUISA AGROPECUARIA

Registry name: AS11097 - EMPRESA BRASILEIRA DE PESQUISA AGROPECUARIA, BR · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS11097, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11097, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

192.207.194.0/24 Valid Other IRR onlyRADB, TC 671 100% 68
200.0.70.0/24 Valid Other IRR onlyRADB, TC 670 100% 68
200.19.230.0/24 Valid Other IRR onlyRADB 670 100% 68
200.136.111.0/24 Valid Other IRR onlyRADB 670 100% 68
200.19.231.0/24 Valid Other IRR onlyRADB 669 99% 68
200.202.128.0/18 Valid Other IRR onlyRADB, TC 669 99% 68
2801:80:1400::/48 Valid Other IRR onlyTC 635 100% 70
2801:80:140c::/48 Valid Other IRR onlyTC 635 100% 70
2801:80:1414::/48 Valid Other IRR onlyRADB, TC 635 100% 70
2801:80:148c::/48 Valid Other IRR onlyRADB, TC 635 100% 70
2801:80:14e0::/43 Valid Other IRR onlyTC 635 100% 70
2801:80:1418::/48 Valid Other IRR onlyRADB, TC 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS11097: TC::AS11097:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS11097 isn't in the set, or no route object for AS11097 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS11097 in itNot covered
TC::AS11097:AS-ALL TC 1213 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • Route object: RIR12
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: RIR192.207.194.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.0.70.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR200.19.230.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.136.111.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.19.231.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.202.128.0/18Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2801:80:1400::/48Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:80:140c::/48Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:80:1414::/48Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:80:148c::/48Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:80:14e0::/43Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2801:80:1418::/48Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

Route objects with origin AS11097 whose prefix no peer sees AS11097 announce. Many are kept on purpose (backup routes, space announced only in some places).

2801:80:1400::/40RADB, TCValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.