bgpreport

Network · data from 2026-11-12

AS272442 AS272442 - VOY TELECOM EIRELI

Registry name: AS272442 - VOY TELECOM EIRELI, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272442, 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.
138.0.87.0/24 No ROA Other IRR onlyRADB, TC 669 99% 66
2804:8140::/36 No ROA Other IRR onlyTC 635 100% 67
2804:8140:1000::/36 No ROA Other IRR onlyTC 635 100% 67
2804:8140:2000::/36 No ROA Other IRR onlyTC 635 100% 67
2804:8140:3000::/36 No ROA Other IRR onlyTC 635 100% 67
2804:8140:4000::/36 No ROA Other IRR onlyTC 635 100% 67
2804:8140::/32 No ROA Other IRR onlyRADB, TC 634 100% 69

AS-SET

AS272442 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: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none138.0.87.0/24No ROA covers it. Add a ROA for AS272442, maxLength 24.669 of 673
Route object: RIR138.0.87.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:8140::/36No ROA covers it. Add a ROA for AS272442, maxLength 36.635 of 636
Route object: RIR2804:8140::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:8140:1000::/36No ROA covers it. Add a ROA for AS272442, maxLength 36.635 of 636
Route object: RIR2804:8140:1000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:8140:2000::/36No ROA covers it. Add a ROA for AS272442, maxLength 36.635 of 636
Route object: RIR2804:8140:2000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:8140:3000::/36No ROA covers it. Add a ROA for AS272442, maxLength 36.635 of 636
Route object: RIR2804:8140:3000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:8140:4000::/36No ROA covers it. Add a ROA for AS272442, maxLength 36.635 of 636
Route object: RIR2804:8140:4000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:8140::/32No ROA covers it. Add a ROA for AS272442, maxLength 32.634 of 636
Route object: RIR2804:8140::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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