Network · data from 2026-11-12

AS274581 EVAR SOLUCOES EM TI LTDA

Registry name: AS274581 - EVAR SOLUCOES EM TI LTDA, BR · PeeringDB

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

3IPv6 routes 100.0% RPKI valid · 66.7% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

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

2Route objects not announced registered with origin AS274581, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS274581, 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:9644:102::/48	Valid	Nonecovered by 2804:9644:100::/40	632 99%	67
192.141.163.0/24	Valid	Other IRR onlyALTDB, RADB, TC	670 100%	67
2804:9644:201::/48	Valid	Other IRR onlyRADB, TC	636 100%	67
2804:9644:100::/40	Valid	Other IRR onlyALTDB, RADB, TC	632 99%	67
151.247.21.0/24	Valid	RIR databaseALTDB, RADB, RIPE	670 100%	67

AS-SET

AS274581's PeeringDB record names no 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 6 are in fix.csv.

Route object: none1
Route object: RIR3
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:9644:102::/48	No route object for it. A route object for 2804:9644:100::/40 with origin AS274581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274581 in the RIR database for the space.	632 of 636
Route object: RIR	192.141.163.0/24	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	2804:9644:201::/48	Route object only in RADB, TC. Add it in the RIR database for the space.	636 of 636
Route object: RIR	2804:9644:100::/40	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	632 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:9644:102::/48

No route object for it. A route object for 2804:9644:100::/40 with origin AS274581 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274581 in the RIR database for the space.

632 of 636

Route object: RIR

192.141.163.0/24

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

670 of 673

Route object: RIR

2804:9644:201::/48

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

636 of 636

Route object: RIR

2804:9644:100::/40

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

632 of 636

Route objects not announced

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


2804:9644::/32	ALTDB, TC	Valid
2a13:9500:13d::/48	RIPE	Valid

2804:9644::/32

ALTDB, TC

Valid

2a13:9500:13d::/48

RIPE

Valid

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.