bgpreport

Network · data from 2026-11-12

AS268412 Alternativa Web Multiminida Ltda Me

Registry name: AS268412 - ALTERNATIVA WEB MULTIMIDIA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268412, 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.160.166.0/23 Invalid: maxLength Nonecovered by 45.160.164.0/22 32 5%low visibility 16
45.160.164.0/24 Valid Nonecovered by 45.160.164.0/22 671 100% 66
45.160.165.0/24 Valid Nonecovered by 45.160.164.0/22 671 100% 66
45.160.166.0/24 Valid Nonecovered by 45.160.164.0/22 671 100% 66
45.160.167.0/24 Valid Nonecovered by 45.160.164.0/22 671 100% 66
45.160.164.0/22 Valid Other IRR onlyRADB 671 100% 66
2804:50d0::/32 Valid Other IRR onlyRADB 633 100% 67
2804:50d0::/36 Valid Other IRR onlyRADB 633 100% 67
2804:50d0:8000::/36 Valid Other IRR onlyRADB 633 100% 67
2804:50d0:c000::/36 Valid Other IRR onlyRADB 633 100% 67

AS-SET

AS268412's PeeringDB record names no AS-SET.

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: maxLength1
  • Route object: none5
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.160.166.0/23ROA 45.160.164.0/22 AS268412 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 45.160.166.0/23.32 of 673
Route object: none45.160.166.0/23No route object for it. A route object for 45.160.164.0/22 with origin AS268412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268412 in the RIR database for the space.32 of 673
Route object: none45.160.164.0/24No route object for it. A route object for 45.160.164.0/22 with origin AS268412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268412 in the RIR database for the space.671 of 673
Route object: none45.160.165.0/24No route object for it. A route object for 45.160.164.0/22 with origin AS268412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268412 in the RIR database for the space.671 of 673
Route object: none45.160.166.0/24No route object for it. A route object for 45.160.164.0/22 with origin AS268412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268412 in the RIR database for the space.671 of 673
Route object: none45.160.167.0/24No route object for it. A route object for 45.160.164.0/22 with origin AS268412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268412 in the RIR database for the space.671 of 673
Route object: RIR45.160.164.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:50d0::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:50d0::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:50d0:8000::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:50d0:c000::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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