bgpreport

Network · data from 2026-11-12

AS268011 S.BARROS DE SOUZA EIRELI

Registry name: AS268011 - S.BARROS DE SOUZA-ME, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
4Route objects not announced registered with origin AS268011, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268011, 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.

45.167.140.0/22 Valid Other IRR onlyRADB, TC 667 99% 66
45.167.142.0/24 Valid Other IRR onlyTC 667 99% 66
45.167.140.0/23 Valid Other IRR onlyRADB, TC 666 99% 67
45.167.140.0/24 Valid Other IRR onlyTC 666 99% 67
45.167.141.0/24 Valid Other IRR onlyTC 666 99% 67
45.167.142.0/23 Valid Other IRR onlyTC 666 99% 67
2804:5698::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:5698::/33 Valid Other IRR onlyTC 631 99% 67
2804:5698::/34 Valid Other IRR onlyTC 354 56% 64
2804:5698:4000::/34 Valid Other IRR onlyTC 354 56% 64
2804:5698:8000::/34 Valid Other IRR onlyTC 354 56% 64
45.167.143.0/24 Valid Other IRR onlyTC 207 31% 54

AS-SET

PeeringDB's irr_as_set for AS268011: AS268011: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 (AS268011 isn't in the set, or no route object for AS268011 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 objectsAS268011 in itNot covered
AS268011:AS-ALL TC2 member sets in no database: AS268011:AS-NETFACIL-CUSTOM, AS268011:AS-NETFACIL-ONLY 010 No 12

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 19 are in fix.csv.

  • Route object: RIR12
  • AS-SET: own ASN1
  • AS-SET: missing member2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR45.167.140.0/22Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.167.142.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.167.140.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.167.140.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.167.141.0/24Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.167.142.0/23Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:5698::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5698::/33Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5698::/34Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:5698:4000::/34Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:5698:8000::/34Route object only in TC. Add it in the RIR database for the space.354 of 636
Route object: RIR45.167.143.0/24Route object only in TC. Add it in the RIR database for the space.207 of 673
AS-SET: own ASNAS268011:AS-ALLAS268011 isn't in AS268011:AS-ALL (TC) once expanded. Add AS268011 to it.
AS-SET: missing memberAS268011:AS-ALLAS268011:AS-ALL (TC) lists AS268011:AS-NETFACIL-CUSTOM; no IRR database read has it.
AS-SET: missing memberAS268011:AS-ALLAS268011:AS-ALL (TC) lists AS268011:AS-NETFACIL-ONLY; no IRR database read has it.

Route objects not announced

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

2804:5698:900::/40RADBValid
2804:5698:8000::/33TCValid
2804:5698:c000::/34TCValid
2804:56cc::/32RADBNo ROA

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.