bgpreport

Network · data from 2026-11-12

AS265906 AGILIZA ASSESSORIA E CONSULTORIA EMPRESARIAL

Registry name: AS265906 - AGILIZA ASSESSORIA E CONSULTORIA EMPRESARIAL LTDA, BR · PeeringDB

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

Announced routes

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

2804:3fac::/33 Invalid: maxLength Nonecovered by 2804:3fac::/32 35 6%low visibility 23
2804:3fac:8000::/33 Invalid: maxLength Nonecovered by 2804:3fac::/32 35 6%low visibility 23
128.201.240.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
128.201.240.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
128.201.242.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
2804:3fac::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS265906: AS265906. 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 (AS265906 isn't in the set, or no route object for AS265906 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 objectsAS265906 in itNot covered
AS265906 A single AS number, not a set: AS265906 (this network), 9 route objects.

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.

  • ROA: maxLength2
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:3fac::/33ROA 2804:3fac::/32 AS265906 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:3fac::/33.35 of 636
Route object: none2804:3fac::/33No route object for it. A route object for 2804:3fac::/32 with origin AS265906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265906 in the RIR database for the space.35 of 636
ROA: maxLength2804:3fac:8000::/33ROA 2804:3fac::/32 AS265906 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:3fac:8000::/33.35 of 636
Route object: none2804:3fac:8000::/33No route object for it. A route object for 2804:3fac::/32 with origin AS265906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265906 in the RIR database for the space.35 of 636
Route object: RIR128.201.240.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR128.201.240.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR128.201.242.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:3fac::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

128.201.240.0/24RADBValid
128.201.241.0/24RADBValid
128.201.242.0/24RADBValid
128.201.243.0/24RADBValid
128.202.240.0/22RADBNo 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.