Network · data from 2026-11-12

AS271188 AS271188 - VOCAL NET TELECOMUNICACOES LTDA

Registry name: AS271188 - VOCAL NET TELECOMUNICACOES LTDA, BR · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

1RPKI invalid 1 origin · 0 maxLength

0No ROA 1 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS271188, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271188, 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.


38.9.215.0/24	Invalid: origin	None	23 3%low visibility	9
200.6.48.0/24	Valid	Other IRR onlyRADB, TC	670 100%	67
2804:7798::/32	Valid	Other IRR onlyRADB, TC	633 100%	67

38.9.215.0/24

Invalid: origin

None

23 3%low visibility

200.6.48.0/24

Valid

Other IRR onlyRADB, TC

670 100%

2804:7798::/32

Valid

Other IRR onlyRADB, TC

633 100%

AS-SET

AS271188 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 4 are in fix.csv.

ROA: origin1
Route object: none1
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	38.9.215.0/24	An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS271188 should announce it, add a ROA for AS271188.	23 of 673
Route object: none	38.9.215.0/24	No route object for it. Add a route object with origin AS271188 in the RIR database for the space.	23 of 673
Route object: RIR	200.6.48.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	2804:7798::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	633 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

38.9.215.0/24

An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS271188 should announce it, add a ROA for AS271188.

23 of 673

Route object: none

38.9.215.0/24

No route object for it. Add a route object with origin AS271188 in the RIR database for the space.

23 of 673

Route object: RIR

200.6.48.0/24

Route object only in RADB, TC. Add it in the RIR database for the space.

670 of 673

Route object: RIR

2804:7798::/32

Route object only in RADB, TC. Add it in the RIR database for the space.

633 of 636

Route objects not announced

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