bgpreport

Network · data from 2026-11-12

AS266498 UNIVERSO INTERNET

Registry name: AS266498 - UNIVERSO FIBER COMUNICACAO MULTIMIDIA, BR · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 25.0% with a route object
0RPKI invalid 0 origin · 0 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 AS266498, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266498, 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:38bc:800::/40 Valid Nonecovered by 2804:38bc::/32 366 58% 65
2804:38bc:900::/40 Valid Nonecovered by 2804:38bc::/32 366 58% 65
2804:38bc:a00::/40 Valid Nonecovered by 2804:38bc::/32 366 58% 65
170.244.72.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
170.244.72.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:38bc::/32 Valid Other IRR onlyRADB, TC 631 99% 67
170.244.72.0/23 Valid Other IRR onlyRADB, TC 188 28% 51
170.244.74.0/23 Valid Other IRR onlyRADB, TC 188 28% 51
170.244.74.0/24 Valid Other IRR onlyRADB, TC 99 15% 37
170.244.73.0/24 Valid Other IRR onlyRADB, TC 98 15% 36
170.244.75.0/24 Valid Other IRR onlyRADB, TC 98 15% 36
38.224.136.0/23 Valid RIR databaseARIN 673 100% 66

AS-SET

PeeringDB's irr_as_set for AS266498: AS266498:AS-UNIVERSO. 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 (AS266498 isn't in the set, or no route object for AS266498 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 objectsAS266498 in itNot covered
AS266498:AS-UNIVERSO TC 2317 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 11 are in fix.csv.

  • Route object: none3
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:38bc:800::/40No route object for it. A route object for 2804:38bc::/32 with origin AS266498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266498 in the RIR database for the space.366 of 636
Route object: none2804:38bc:900::/40No route object for it. A route object for 2804:38bc::/32 with origin AS266498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266498 in the RIR database for the space.366 of 636
Route object: none2804:38bc:a00::/40No route object for it. A route object for 2804:38bc::/32 with origin AS266498 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266498 in the RIR database for the space.366 of 636
Route object: RIR170.244.72.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.244.72.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:38bc::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR170.244.72.0/23Route object only in RADB, TC. Add it in the RIR database for the space.188 of 673
Route object: RIR170.244.74.0/23Route object only in RADB, TC. Add it in the RIR database for the space.188 of 673
Route object: RIR170.244.74.0/24Route object only in RADB, TC. Add it in the RIR database for the space.99 of 673
Route object: RIR170.244.73.0/24Route object only in RADB, TC. Add it in the RIR database for the space.98 of 673
Route object: RIR170.244.75.0/24Route object only in RADB, TC. Add it in the RIR database for the space.98 of 673

Route objects not announced

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