Network · data from 2026-11-12

AS271754 Velosch Telecomunicações - Eireli

Registry name: AS271754 - Velosch Telecomunicacoes - Eireli, BR · PeeringDB

2IPv4 routes 100.0% RPKI valid · 0.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


164.163.243.0/24	Valid	None	671 100%	66
200.1.7.0/24	Valid	None	669 99%	67
2804:8080::/32	Valid	Other IRR onlyRADB	635 100%	67
2804:8080:8000::/33	Valid	Other IRR onlyRADB	635 100%	67

AS-SET

PeeringDB's irr_as_set for AS271754: AS271754. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS271754 isn't in the set, or no route object for AS271754 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS271754 in it	Not covered
AS271754	A single AS number, not a set: AS271754 (this network), 2 route objects.

Name

Database

ASNs

Sets

Route objects

AS271754 in it

Not covered

AS271754

A single AS number, not a set: AS271754 (this network), 2 route objects.

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.

Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: none	164.163.243.0/24	No route object for it. Add a route object with origin AS271754 in the RIR database for the space.	671 of 673
Route object: none	200.1.7.0/24	No route object for it. Add a route object with origin AS271754 in the RIR database for the space.	669 of 673
Route object: RIR	2804:8080::/32	Route object only in RADB. Add it in the RIR database for the space.	635 of 636
Route object: RIR	2804:8080:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

164.163.243.0/24

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

671 of 673

Route object: none

200.1.7.0/24

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

669 of 673

Route object: RIR

2804:8080::/32

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

635 of 636

Route object: RIR

2804:8080:8000::/33

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

635 of 636

Route objects not announced

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