Network · data from 2026-11-12

AS273747 AS273747 - TECH IN SOLUCOES LTDA

Registry name: AS273747 - TECH IN SOLUCOES LTDA, BR · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object

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

1RPKI invalid 1 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

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

Announced routes

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


177.190.156.0/23	Invalid: origin	Other origin only	104 15%	43
2804:8ba8::/33	Valid	Nonecovered by 2804:8ba8::/32	634 100%	67
2804:8ba8:8000::/33	Valid	Nonecovered by 2804:8ba8::/32	634 100%	67
2804:8ba8::/32	Valid	Other IRR onlyRADB	632 99%	67

AS-SET

AS273747 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 5 are in fix.csv.

ROA: origin1
Route object: none3
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	177.190.156.0/23	ROAs covering it name AS263457, not AS273747. If AS273747 should announce it, add a ROA for AS273747.	104 of 673
Route object: none	177.190.156.0/23	Route objects for it name AS263457. Add a route object with origin AS273747 in the RIR database for the space.	104 of 673
Route object: none	2804:8ba8::/33	No route object for it. A route object for 2804:8ba8::/32 with origin AS273747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273747 in the RIR database for the space.	634 of 636
Route object: none	2804:8ba8:8000::/33	No route object for it. A route object for 2804:8ba8::/32 with origin AS273747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273747 in the RIR database for the space.	634 of 636
Route object: RIR	2804:8ba8::/32	Route object only in RADB. Add it in the RIR database for the space.	632 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: origin

177.190.156.0/23

ROAs covering it name AS263457, not AS273747. If AS273747 should announce it, add a ROA for AS273747.

104 of 673

Route object: none

177.190.156.0/23

Route objects for it name AS263457. Add a route object with origin AS273747 in the RIR database for the space.

104 of 673

Route object: none

2804:8ba8::/33

No route object for it. A route object for 2804:8ba8::/32 with origin AS273747 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273747 in the RIR database for the space.

634 of 636

Route object: none

2804:8ba8:8000::/33

634 of 636

Route object: RIR

2804:8ba8::/32

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

632 of 636

Route objects not announced

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