bgpreport

Network · data from 2026-11-12

AS271393 AS271393 - WALTER ROSITO JUNIOR - ME

Registry name: AS271393 - WALTER ROSITO JUNIOR - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271393, 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:7ad0::/35 No ROA Nonecovered by 2804:7ad0::/33 634 100% 67
181.189.120.0/22 No ROA Other IRR onlyALTDB, TC 671 100% 66
181.189.120.0/24 No ROA Other IRR onlyTC 671 100% 66
181.189.122.0/24 No ROA Other IRR onlyTC 671 100% 66
181.189.121.0/24 No ROA Other IRR onlyTC 670 100% 66
181.189.123.0/24 No ROA Other IRR onlyTC 670 100% 66
2804:7ad0::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS271393 isn't in PeeringDB, where networks name their 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 18 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:7ad0::/35No ROA covers it. Add a ROA for AS271393, maxLength 35.634 of 636
Route object: none2804:7ad0::/35No route object for it. A route object for 2804:7ad0::/33 with origin AS271393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271393 in the RIR database for the space.634 of 636
ROA: none181.189.120.0/22No ROA covers it. Add a ROA for AS271393, maxLength 22.671 of 673
Route object: RIR181.189.120.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
ROA: none181.189.120.0/24No ROA covers it. Add a ROA for AS271393, maxLength 24.671 of 673
Route object: RIR181.189.120.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none181.189.122.0/24No ROA covers it. Add a ROA for AS271393, maxLength 24.671 of 673
Route object: RIR181.189.122.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none181.189.121.0/24No ROA covers it. Add a ROA for AS271393, maxLength 24.670 of 673
Route object: RIR181.189.121.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none181.189.123.0/24No ROA covers it. Add a ROA for AS271393, maxLength 24.670 of 673
Route object: RIR181.189.123.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:7ad0::/32No ROA covers it. Add a ROA for AS271393, maxLength 32.634 of 636
Route object: RIR2804:7ad0::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

181.189.120.0/23TCNo ROA
181.189.122.0/23TCNo ROA
2804:7ad0::/33TCNo ROA
2804:7ad0:8000::/33TCNo 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.