bgpreport

Network · data from 2026-11-12

AS268791 E C de CANO

Registry name: AS268791 - AREA 51 PROVEDOR DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268791, 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.172.64.0/22 No ROA Other IRR onlyALTDB, RADB, TC 672 100% 66
200.9.28.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:5ab8::/32 No ROA Other IRR onlyALTDB, RADB, TC 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS268791: AS268791: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 (AS268791 isn't in the set, or no route object for AS268791 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 objectsAS268791 in itNot covered
AS268791:AS-ALL TC 2236 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 24 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none45.172.64.0/22No ROA covers it. Add a ROA for AS268791, maxLength 22.672 of 673
Route object: RIR45.172.64.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none200.9.28.0/22No ROA covers it. Add a ROA for AS268791, maxLength 22.672 of 673
Route object: RIR200.9.28.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:5ab8::/32No ROA covers it. Add a ROA for AS268791, maxLength 32.632 of 636
Route object: RIR2804:5ab8::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

45.172.64.0/23RADB, TCNo ROA
45.172.64.0/24TCNo ROA
45.172.65.0/24TCNo ROA
45.172.66.0/23RADB, TCNo ROA
45.172.66.0/24RADB, TCNo ROA
45.172.67.0/24TCNo ROA
200.9.28.0/23TCNo ROA
200.9.28.0/24TCNo ROA
200.9.29.0/24TCNo ROA
200.9.30.0/23TCNo ROA
200.9.30.0/24TCNo ROA
200.9.31.0/24TCNo ROA
2804:5ab8::/33RADB, TCNo ROA
2804:5ab8::/34RADB, TCNo ROA
2804:5ab8:4000::/34RADB, TCNo ROA
2804:5ab8:8000::/33RADB, TCNo ROA
2804:5ab8:8000::/34RADB, TCNo ROA
2804:5ab8:c000::/34RADB, TCNo 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.