Network · data from 2026-11-12

AS267653 AS267653 - IS TELECOM LTDA ME

Registry name: AS267653 - IS TELECOM LTDA ME, BR · not in PeeringDB

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

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

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

Announced routes

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


45.224.88.0/24	Valid	Other IRR onlyTC	670 100%	67
45.224.89.0/24	Valid	Other IRR onlyTC	670 100%	67
45.224.90.0/24	Valid	Other IRR onlyTC	670 100%	67
45.224.91.0/24	Valid	Other IRR onlyTC	670 100%	67
45.224.88.0/22	Valid	Other IRR onlyRADB, TC	669 99%	66
2804:44c8::/32	Valid	Other IRR onlyRADB, TC	635 100%	67

AS-SET

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

Route object: RIR6
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.224.88.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.224.89.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.224.90.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.224.91.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.224.88.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:44c8::/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: RIR

45.224.88.0/24

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

670 of 673

Route object: RIR

45.224.89.0/24

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

670 of 673

Route object: RIR

45.224.90.0/24

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

670 of 673

Route object: RIR

45.224.91.0/24

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

670 of 673

Route object: RIR

45.224.88.0/22

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

669 of 673

Route object: RIR

2804:44c8::/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 AS267653 whose prefix no peer sees AS267653 announce. Many are kept on purpose (backup routes, space announced only in some places).


45.224.88.0/23	TC	Valid
45.224.90.0/23	TC	Valid

45.224.88.0/23

Valid

45.224.90.0/23

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.