bgpreport

Network · data from 2026-11-12

AS262364 AS262364 - VIASATDIGITAL TELECOM LTDA

Registry name: AS262364 - VIASATDIGITAL TELECOM LTDA, BR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 75.0% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No 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 AS262364, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262364, 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.128.34.0/24 No ROA Nonecovered by 177.128.32.0/22 672 100% 67
2804:b4c::/33 No ROA Nonecovered by 2804:b4c::/32 354 56% 65
2804:b4c:8000::/33 No ROA Nonecovered by 2804:b4c::/32 354 56% 65
177.128.32.0/21 No ROA Other IRR onlyRADB, TC 671 100% 66
2804:b4c::/32 No ROA Other IRR onlyRADB, TC 633 100% 69
177.128.32.0/22 No ROA Other IRR onlyRADB, TC 207 31% 56
177.128.36.0/22 No ROA Other IRR onlyRADB, TC 207 31% 56

AS-SET

AS262364 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none177.128.34.0/24No ROA covers it. Add a ROA for AS262364, maxLength 24.672 of 673
Route object: none177.128.34.0/24No route object for it. A route object for 177.128.32.0/22 with origin AS262364 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262364 in the RIR database for the space.672 of 673
ROA: none2804:b4c::/33No ROA covers it. Add a ROA for AS262364, maxLength 33.354 of 636
Route object: none2804:b4c::/33No route object for it. A route object for 2804:b4c::/32 with origin AS262364 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262364 in the RIR database for the space.354 of 636
ROA: none2804:b4c:8000::/33No ROA covers it. Add a ROA for AS262364, maxLength 33.354 of 636
Route object: none2804:b4c:8000::/33No route object for it. A route object for 2804:b4c::/32 with origin AS262364 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262364 in the RIR database for the space.354 of 636
ROA: none177.128.32.0/21No ROA covers it. Add a ROA for AS262364, maxLength 21.671 of 673
Route object: RIR177.128.32.0/21Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:b4c::/32No ROA covers it. Add a ROA for AS262364, maxLength 32.633 of 636
Route object: RIR2804:b4c::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none177.128.32.0/22No ROA covers it. Add a ROA for AS262364, maxLength 22.207 of 673
Route object: RIR177.128.32.0/22Route object only in RADB, TC. Add it in the RIR database for the space.207 of 673
ROA: none177.128.36.0/22No ROA covers it. Add a ROA for AS262364, maxLength 22.207 of 673
Route object: RIR177.128.36.0/22Route object only in RADB, TC. Add it in the RIR database for the space.207 of 673

Route objects not announced

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