bgpreport

Network · data from 2026-11-12

AS267325 USB INFORMATICA

Registry name: AS267325 - USBINF INFORMATICA LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267325, 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:4bb4:1000::/36 Valid Nonecovered by 2804:4bb4::/32 636 100% 67
45.233.176.0/22 Valid Other IRR onlyTC 671 100% 67
45.233.178.0/24 Valid Other IRR onlyTC 669 99% 67
45.233.179.0/24 Valid Other IRR onlyTC 668 99% 67
2804:4bb4::/32 Valid Other IRR onlyTC 633 100% 70
45.233.176.0/23 Valid Other IRR onlyTC 128 19% 45
45.233.178.0/23 Valid Other IRR onlyTC 128 19% 45
45.233.176.0/24 Valid Other IRR onlyTC 120 18% 41
45.233.177.0/24 Valid Other IRR onlyTC 119 18% 41
2804:4bb4:100::/40 Valid Other IRR onlyTC 111 17% 43
2804:4bb4:300::/40 Valid Other IRR onlyTC 111 17% 43

AS-SET

PeeringDB's irr_as_set for AS267325: AS267325:AS-USB. 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 (AS267325 isn't in the set, or no route object for AS267325 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 objectsAS267325 in itNot covered
AS267325:AS-USB TC1 member set in no database: AS267325:AS-USB-ONLY 3256 No 11

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: none1
  • Route object: RIR10
  • AS-SET: own ASN1
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: none2804:4bb4:1000::/36No route object for it. A route object for 2804:4bb4::/32 with origin AS267325 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267325 in the RIR database for the space.636 of 636
Route object: RIR45.233.176.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.233.178.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.233.179.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:4bb4::/32Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR45.233.176.0/23Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR45.233.178.0/23Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR45.233.176.0/24Route object only in TC. Add it in the RIR database for the space.120 of 673
Route object: RIR45.233.177.0/24Route object only in TC. Add it in the RIR database for the space.119 of 673
Route object: RIR2804:4bb4:100::/40Route object only in TC. Add it in the RIR database for the space.111 of 636
Route object: RIR2804:4bb4:300::/40Route object only in TC. Add it in the RIR database for the space.111 of 636
AS-SET: own ASNAS267325:AS-USBAS267325 isn't in AS267325:AS-USB (TC) once expanded. Add AS267325 to it.
AS-SET: missing memberAS267325:AS-USBAS267325:AS-USB (TC) lists AS267325:AS-USB-ONLY; no IRR database read has it.

Route objects not announced

Every route object with origin AS267325 is announced.

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.