bgpreport

Network · data from 2026-11-12

AS268316 AS268316 - VAITELECOM LTDA ME

Registry name: AS268316 - VAITELECOM LTDA ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268316, 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:4f44:100::/40 No ROA Nonecovered by 2804:4f44::/32 3 0%low visibility 3
45.238.80.0/24 No ROA Other IRR onlyRADB 673 100% 66
45.238.82.0/23 No ROA Other IRR onlyRADB 672 100% 66
45.238.82.0/24 No ROA Other IRR onlyRADB 671 100% 66
45.238.83.0/24 No ROA Other IRR onlyRADB 671 100% 66
2804:4f44:200::/40 No ROA Other IRR onlyRADB 636 100% 67
2804:4f44:8000::/40 No ROA Other IRR onlyRADB 634 100% 67
45.238.81.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS268316 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 21 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none2804:4f44:100::/40No ROA covers it. Add a ROA for AS268316, maxLength 40.3 of 636
Route object: none2804:4f44:100::/40No route object for it. A route object for 2804:4f44::/32 with origin AS268316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268316 in the RIR database for the space.3 of 636
ROA: none45.238.80.0/24No ROA covers it. Add a ROA for AS268316, maxLength 24.673 of 673
Route object: RIR45.238.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none45.238.82.0/23No ROA covers it. Add a ROA for AS268316, maxLength 23.672 of 673
Route object: RIR45.238.82.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.238.82.0/24No ROA covers it. Add a ROA for AS268316, maxLength 24.671 of 673
Route object: RIR45.238.82.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.238.83.0/24No ROA covers it. Add a ROA for AS268316, maxLength 24.671 of 673
Route object: RIR45.238.83.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:4f44:200::/40No ROA covers it. Add a ROA for AS268316, maxLength 40.636 of 636
Route object: RIR2804:4f44:200::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:4f44:8000::/40No ROA covers it. Add a ROA for AS268316, maxLength 40.634 of 636
Route object: RIR2804:4f44:8000::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none45.238.81.0/24No ROA covers it. Add a ROA for AS268316, maxLength 24.2 of 673
Route object: RIR45.238.81.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.162.117.0/24RADBNo ROA
45.238.80.0/22RADB, TCNo ROA
2804:4f44::/32RADB, TCNo ROA
2804:4f44:200::/41RADBNo ROA
2804:4f44:280::/41RADBNo 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.