Network · data from 2026-11-12

AS269307 LIVENET

Registry name: AS269307 - LIVENET SERVICOS DE COMUNICACAO MULTMIDIA LTDA ME, BR · PeeringDB

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

3IPv6 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

0Route objects not announced registered with origin AS269307, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269307, 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.184.8.0/22	Valid	Other IRR onlyTC	672 100%	67
45.184.8.0/23	Valid	Other IRR onlyTC	667 99%	67
45.184.10.0/23	Valid	Other IRR onlyTC	664 99%	67
2804:629c::/32	Valid	Other IRR onlyRADB, TC	633 100%	67
2804:629c::/33	Valid	Other IRR onlyTC	336 53%	65
2804:629c:8000::/33	Valid	Other IRR onlyTC	336 53%	65
45.184.9.0/24	Valid	Other IRR onlyTC	135 20%	45
45.184.10.0/24	Valid	Other IRR onlyTC	135 20%	45
45.184.11.0/24	Valid	Other IRR onlyTC	135 20%	45
45.184.8.0/24	Valid	Other IRR onlyTC	132 20%	44

AS-SET

AS269307'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 10 are in fix.csv.

Route object: RIR10

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.184.8.0/22	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	45.184.8.0/23	Route object only in TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	45.184.10.0/23	Route object only in TC. Add it in the RIR database for the space.	664 of 673
Route object: RIR	2804:629c::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	633 of 636
Route object: RIR	2804:629c::/33	Route object only in TC. Add it in the RIR database for the space.	336 of 636
Route object: RIR	2804:629c:8000::/33	Route object only in TC. Add it in the RIR database for the space.	336 of 636
Route object: RIR	45.184.9.0/24	Route object only in TC. Add it in the RIR database for the space.	135 of 673
Route object: RIR	45.184.10.0/24	Route object only in TC. Add it in the RIR database for the space.	135 of 673
Route object: RIR	45.184.11.0/24	Route object only in TC. Add it in the RIR database for the space.	135 of 673
Route object: RIR	45.184.8.0/24	Route object only in TC. Add it in the RIR database for the space.	132 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.184.8.0/22

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

672 of 673

Route object: RIR

45.184.8.0/23

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

667 of 673

Route object: RIR

45.184.10.0/23

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

664 of 673

Route object: RIR

2804:629c::/32

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

633 of 636

Route object: RIR

2804:629c::/33

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

336 of 636

Route object: RIR

2804:629c:8000::/33

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

336 of 636

Route object: RIR

45.184.9.0/24

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

135 of 673

Route object: RIR

45.184.10.0/24

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

135 of 673

Route object: RIR

45.184.11.0/24

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

135 of 673

Route object: RIR

45.184.8.0/24

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

132 of 673

Route objects not announced

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