Network · data from 2026-11-12

AS270813 AS270813 - INTERJOIN TELECOMUNICACAO LTDA

Registry name: AS270813 - INTERJOIN TELECOMUNICACAO LTDA, BR · not in PeeringDB

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

3IPv6 routes 100.0% RPKI valid · 33.3% 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 AS270813, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270813, 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:71d0::/33	Valid	Nonecovered by 2804:71d0::/32	634 100%	67
2804:71d0:8000::/33	Valid	Nonecovered by 2804:71d0::/32	634 100%	67
177.128.200.0/23	Valid	Other IRR onlyRADB	672 100%	66
177.128.200.0/24	Valid	Other IRR onlyRADB	672 100%	66
177.128.201.0/24	Valid	Other IRR onlyRADB	672 100%	66
2804:71d0::/32	Valid	Other IRR onlyRADB	634 100%	67

AS-SET

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

Route object: none2
Route object: RIR4

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:71d0::/33	No route object for it. A route object for 2804:71d0::/32 with origin AS270813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270813 in the RIR database for the space.	634 of 636
Route object: none	2804:71d0:8000::/33	No route object for it. A route object for 2804:71d0::/32 with origin AS270813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270813 in the RIR database for the space.	634 of 636
Route object: RIR	177.128.200.0/23	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	177.128.200.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	177.128.201.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2804:71d0::/32	Route object only in RADB. Add it in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:71d0::/33

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

634 of 636

Route object: none

2804:71d0:8000::/33

634 of 636

Route object: RIR

177.128.200.0/23

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

672 of 673

Route object: RIR

177.128.200.0/24

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

672 of 673

Route object: RIR

177.128.201.0/24

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

672 of 673

Route object: RIR

2804:71d0::/32

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

634 of 636

Route objects not announced

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