Network · data from 2026-11-12

AS265227 TITAN TELECOMUNICACOES

Registry name: AS265227 - TITAN TELECOMUNICACOES LTDA, BR · PeeringDB

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

0IPv6 routes

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 AS265227, seen from no peer

Announced routes

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


167.250.228.0/22	Valid	Other IRR onlyRADB, TC	669 99%	67
167.250.228.0/23	Valid	Other IRR onlyTC	669 99%	67
167.250.229.0/24	Valid	Other IRR onlyRADB, TC	669 99%	67
167.250.230.0/23	Valid	Other IRR onlyTC	669 99%	67
167.250.230.0/24	Valid	Other IRR onlyRADB, TC	669 99%	67
167.250.228.0/24	Valid	Other IRR onlyRADB, TC	668 99%	67

AS-SET

AS265227's PeeringDB record names no 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	167.250.228.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	167.250.228.0/23	Route object only in TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	167.250.229.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	167.250.230.0/23	Route object only in TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	167.250.230.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	669 of 673
Route object: RIR	167.250.228.0/24	Route object only in RADB, TC. Add it in the RIR database for the space.	668 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

167.250.228.0/22

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

669 of 673

Route object: RIR

167.250.228.0/23

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

669 of 673

Route object: RIR

167.250.229.0/24

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

669 of 673

Route object: RIR

167.250.230.0/23

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

669 of 673

Route object: RIR

167.250.230.0/24

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

669 of 673

Route object: RIR

167.250.228.0/24

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

668 of 673

Route objects not announced

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


167.250.231.0/24	RADB, TC	Valid
2804:2c90::/32	RADB, TC	Valid

167.250.231.0/24

RADB, TC

Valid

2804:2c90::/32

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.