bgpreport

Network · data from 2026-11-12

AS267262 Unit Telecom

Registry name: AS267262 - Unit Fibra LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267262, 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:4ac4::/33 Invalid: maxLength Nonecovered by 2804:4ac4::/32 81 13% 42
2804:4ac4:8000::/33 Invalid: maxLength Nonecovered by 2804:4ac4::/32 81 13% 42
2804:4ac4:9000::/37 Valid Nonecovered by 2804:4ac4::/32 636 100% 67
45.232.100.0/23 Valid Other IRR onlyALTDB, RADB 673 100% 66
45.232.102.0/23 Valid Other IRR onlyALTDB, RADB 673 100% 66
45.232.100.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
45.232.102.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
45.232.103.0/24 Valid Other IRR onlyALTDB, RADB 669 99% 67
2804:4ac4::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS267262: AS267262. 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 (AS267262 isn't in the set, or no route object for AS267262 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 objectsAS267262 in itNot covered
AS267262 A single AS number, not a set: AS267262 (this network), 6 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 11 are in fix.csv.

  • ROA: maxLength2
  • Route object: none3
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:4ac4::/33ROA 2804:4ac4::/32 AS267262 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:4ac4::/33.81 of 636
Route object: none2804:4ac4::/33No route object for it. A route object for 2804:4ac4::/32 with origin AS267262 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267262 in the RIR database for the space.81 of 636
ROA: maxLength2804:4ac4:8000::/33ROA 2804:4ac4::/32 AS267262 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:4ac4:8000::/33.81 of 636
Route object: none2804:4ac4:8000::/33No route object for it. A route object for 2804:4ac4::/32 with origin AS267262 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267262 in the RIR database for the space.81 of 636
Route object: none2804:4ac4:9000::/37No route object for it. A route object for 2804:4ac4::/32 with origin AS267262 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267262 in the RIR database for the space.636 of 636
Route object: RIR45.232.100.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.232.102.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.232.100.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.232.102.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.232.103.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:4ac4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS267262 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.