bgpreport

Network · data from 2026-11-12

AS266004 AS266004 - VIAWEB TELECOMUNICACOES LTDA

Registry name: AS266004 - VIAWEB TELECOMUNICACOES LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266004, 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:411c:1e2a::/48 No ROA Nonecovered by 2804:411c::/32 636 100% 67
2804:411c:1e2b::/48 No ROA Nonecovered by 2804:411c::/32 636 100% 67
2804:411c:1e2c::/48 No ROA Nonecovered by 2804:411c::/32 636 100% 67
2804:411c:1e2d::/48 No ROA Nonecovered by 2804:411c::/32 636 100% 67
181.191.108.0/22 No ROA Other IRR onlyRADB 670 100% 66
181.191.108.0/23 No ROA Other IRR onlyRADB 668 99% 66
181.191.110.0/23 No ROA Other IRR onlyRADB 668 99% 66
2804:411c::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS266004 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none2804:411c:1e2a::/48No ROA covers it. Add a ROA for AS266004, maxLength 48.636 of 636
Route object: none2804:411c:1e2a::/48No route object for it. A route object for 2804:411c::/32 with origin AS266004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266004 in the RIR database for the space.636 of 636
ROA: none2804:411c:1e2b::/48No ROA covers it. Add a ROA for AS266004, maxLength 48.636 of 636
Route object: none2804:411c:1e2b::/48No route object for it. A route object for 2804:411c::/32 with origin AS266004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266004 in the RIR database for the space.636 of 636
ROA: none2804:411c:1e2c::/48No ROA covers it. Add a ROA for AS266004, maxLength 48.636 of 636
Route object: none2804:411c:1e2c::/48No route object for it. A route object for 2804:411c::/32 with origin AS266004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266004 in the RIR database for the space.636 of 636
ROA: none2804:411c:1e2d::/48No ROA covers it. Add a ROA for AS266004, maxLength 48.636 of 636
Route object: none2804:411c:1e2d::/48No route object for it. A route object for 2804:411c::/32 with origin AS266004 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266004 in the RIR database for the space.636 of 636
ROA: none181.191.108.0/22No ROA covers it. Add a ROA for AS266004, maxLength 22.670 of 673
Route object: RIR181.191.108.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none181.191.108.0/23No ROA covers it. Add a ROA for AS266004, maxLength 23.668 of 673
Route object: RIR181.191.108.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none181.191.110.0/23No ROA covers it. Add a ROA for AS266004, maxLength 23.668 of 673
Route object: RIR181.191.110.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:411c::/32No ROA covers it. Add a ROA for AS266004, maxLength 32.636 of 636
Route object: RIR2804:411c::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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