bgpreport

Network · data from 2026-11-12

AS270749 ALCIONE DE SANTANA LIMA

Registry name: AS270749 - VTI PROVEDOR DE INTERNET E SUP DE INFORMATICA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270749, 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.
177.12.210.0/23 No ROA Nonecovered by 177.12.208.0/22 671 100% 67
177.12.208.0/24 No ROA Nonecovered by 177.12.208.0/23 669 99% 67
177.12.209.0/24 No ROA Nonecovered by 177.12.208.0/23 669 99% 67
2804:70cc::/40 No ROA Nonecovered by 2804:70cc::/32 633 100% 69
2804:70cc::/36 No ROA Nonecovered by 2804:70cc::/32 3 0%low visibility 3
177.12.208.0/22 No ROA Other IRR onlyRADB 671 100% 67
177.12.208.0/23 No ROA Other IRR onlyRADB 671 100% 67
177.12.210.0/24 No ROA Other IRR onlyRADB 671 100% 67
177.12.211.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS270749'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 19 are in fix.csv.

  • ROA: none9
  • Route object: none5
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none177.12.210.0/23No ROA covers it. Add a ROA for AS270749, maxLength 23.671 of 673
Route object: none177.12.210.0/23No route object for it. A route object for 177.12.208.0/22 with origin AS270749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270749 in the RIR database for the space.671 of 673
ROA: none177.12.208.0/24No ROA covers it. Add a ROA for AS270749, maxLength 24.669 of 673
Route object: none177.12.208.0/24No route object for it. A route object for 177.12.208.0/23 with origin AS270749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270749 in the RIR database for the space.669 of 673
ROA: none177.12.209.0/24No ROA covers it. Add a ROA for AS270749, maxLength 24.669 of 673
Route object: none177.12.209.0/24No route object for it. A route object for 177.12.208.0/23 with origin AS270749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270749 in the RIR database for the space.669 of 673
ROA: none2804:70cc::/40No ROA covers it. Add a ROA for AS270749, maxLength 40.633 of 636
Route object: none2804:70cc::/40No route object for it. A route object for 2804:70cc::/32 with origin AS270749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270749 in the RIR database for the space.633 of 636
ROA: none2804:70cc::/36No ROA covers it. Add a ROA for AS270749, maxLength 36.3 of 636
Route object: none2804:70cc::/36No route object for it. A route object for 2804:70cc::/32 with origin AS270749 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270749 in the RIR database for the space.3 of 636
ROA: none177.12.208.0/22No ROA covers it. Add a ROA for AS270749, maxLength 22.671 of 673
Route object: RIR177.12.208.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.12.208.0/23No ROA covers it. Add a ROA for AS270749, maxLength 23.671 of 673
Route object: RIR177.12.208.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.12.210.0/24No ROA covers it. Add a ROA for AS270749, maxLength 24.671 of 673
Route object: RIR177.12.210.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.12.211.0/24No ROA covers it. Add a ROA for AS270749, maxLength 24.671 of 673
Route object: RIR177.12.211.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2804:70cc::/32RADBNo 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.