Network · data from 2026-11-12

AS273583 AS273583 - JOSE R DA COSTA LIMA - ME

Registry name: AS273583 - JOSE R DA COSTA LIMA - ME, BR · not in PeeringDB

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

4IPv6 routes 100.0% RPKI valid · 25.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

1Route objects not announced registered with origin AS273583, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273583, 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:8924:4000::/40	Valid	Nonecovered by 2804:8924::/32	633 100%	67
2804:8924:4100::/48	Valid	Nonecovered by 2804:8924::/32	633 100%	67
2804:8924:8000::/35	Valid	Nonecovered by 2804:8924::/32	633 100%	67
45.70.6.0/24	Valid	Other IRR onlyTC	670 100%	66
45.70.6.0/23	Valid	Other IRR onlyTC	669 99%	66
2804:8924::/32	Valid	Other IRR onlyRADB, TC	635 100%	69

AS-SET

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

Route object: none3
Route object: RIR3
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:8924:4000::/40	No route object for it. A route object for 2804:8924::/32 with origin AS273583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273583 in the RIR database for the space.	633 of 636
Route object: none	2804:8924:4100::/48	No route object for it. A route object for 2804:8924::/32 with origin AS273583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273583 in the RIR database for the space.	633 of 636
Route object: none	2804:8924:8000::/35	No route object for it. A route object for 2804:8924::/32 with origin AS273583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273583 in the RIR database for the space.	633 of 636
Route object: RIR	45.70.6.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.70.6.0/23	Route object only in TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:8924::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:8924:4000::/40

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

633 of 636

Route object: none

2804:8924:4100::/48

633 of 636

Route object: none

2804:8924:8000::/35

633 of 636

Route object: RIR

45.70.6.0/24

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

670 of 673

Route object: RIR

45.70.6.0/23

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

669 of 673

Route object: RIR

2804:8924::/32

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

635 of 636

Route objects not announced

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


45.70.7.0/24	TC	Valid

45.70.7.0/24

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.