Network · data from 2026-11-12

AS270393 IPT TELECOM

Registry name: AS270393 - IPT TELECOM, BR · PeeringDB

5IPv4 routes 80.0% RPKI valid · 60.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 6 with no route object for this origin

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

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

Announced routes

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


190.89.142.0/24	No ROA	Other IRR onlyALTDB, RADB	669 99%	67
2804:6b54::/33	Valid	Nonecovered by 2804:6b54::/32	636 100%	67
2804:6b54:8000::/33	Valid	Nonecovered by 2804:6b54::/32	635 100%	67
2804:6b54::/34	Valid	Nonecovered by 2804:6b54::/32	349 55%	64
2804:6b54:4000::/34	Valid	Nonecovered by 2804:6b54::/32	349 55%	64
190.89.141.0/24	Valid	Nonecovered by 190.89.140.0/23	201 30%	54
190.89.140.0/24	Valid	Nonecovered by 190.89.140.0/23	200 30%	54
190.89.140.0/23	Valid	Other IRR onlyALTDB	671 100%	66
190.89.143.0/24	Valid	Other IRR onlyALTDB, RADB	670 100%	66

AS-SET

PeeringDB's irr_as_set for AS270393: AS-270393. 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 (AS270393 isn't in the set, or no route object for AS270393 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	AS270393 in it	Not covered
AS-270393	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS270393 in it

Not covered

AS-270393

In no IRR database read today.

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

ROA: none1
Route object: none6
Route object: RIR3
AS-SET: not found1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: none	190.89.142.0/24	No ROA covers it. Add a ROA for AS270393, maxLength 24.	669 of 673
Route object: RIR	190.89.142.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	669 of 673
Route object: none	2804:6b54::/33	No route object for it. A route object for 2804:6b54::/32 with origin AS270393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270393 in the RIR database for the space.	636 of 636
Route object: none	2804:6b54:8000::/33	No route object for it. A route object for 2804:6b54::/32 with origin AS270393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270393 in the RIR database for the space.	635 of 636
Route object: none	2804:6b54::/34	No route object for it. A route object for 2804:6b54::/32 with origin AS270393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270393 in the RIR database for the space.	349 of 636
Route object: none	2804:6b54:4000::/34	No route object for it. A route object for 2804:6b54::/32 with origin AS270393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270393 in the RIR database for the space.	349 of 636
Route object: none	190.89.141.0/24	No route object for it. A route object for 190.89.140.0/23 with origin AS270393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270393 in the RIR database for the space.	201 of 673
Route object: none	190.89.140.0/24	No route object for it. A route object for 190.89.140.0/23 with origin AS270393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270393 in the RIR database for the space.	200 of 673
Route object: RIR	190.89.140.0/23	Route object only in ALTDB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	190.89.143.0/24	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	670 of 673
AS-SET: not found	AS-270393	PeeringDB names AS-270393; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

190.89.142.0/24

No ROA covers it. Add a ROA for AS270393, maxLength 24.

669 of 673

Route object: RIR

190.89.142.0/24

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

669 of 673

Route object: none

2804:6b54::/33

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

636 of 636

Route object: none

2804:6b54:8000::/33

635 of 636

Route object: none

2804:6b54::/34

349 of 636

Route object: none

2804:6b54:4000::/34

349 of 636

Route object: none

190.89.141.0/24

No route object for it. A route object for 190.89.140.0/23 with origin AS270393 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270393 in the RIR database for the space.

201 of 673

Route object: none

190.89.140.0/24

200 of 673

Route object: RIR

190.89.140.0/23

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

671 of 673

Route object: RIR

190.89.143.0/24

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

670 of 673

AS-SET: not found

AS-270393

PeeringDB names AS-270393; no IRR database read has it.

Route objects not announced

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


190.89.140.0/22	ALTDB, RADB, TC	No ROA
2804:6b54::/32	ALTDB, RADB, TC	Valid

190.89.140.0/22

ALTDB, RADB, TC

No ROA

2804:6b54::/32

ALTDB, RADB, TC

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.