Network · data from 2026-11-12

AS267365 AS267365 - Giga Tecnologia em Redes e Internet LTDA

Registry name: AS267365 - Giga Tecnologia em Redes e Internet LTDA, BR · not in PeeringDB

5IPv4 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

6Route objects not announced registered with origin AS267365, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267365, 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.234.128.0/22	Valid	Other IRR onlyRADB, TC	671 100%	67
45.234.128.0/23	Valid	Other IRR onlyTC	671 100%	67
45.234.130.0/23	Valid	Other IRR onlyTC	671 100%	67
45.234.128.0/24	Valid	Other IRR onlyTC	670 100%	67
45.234.129.0/24	Valid	Other IRR onlyTC	670 100%	67
2804:4c58::/32	Valid	Other IRR onlyRADB, TC	634 100%	67
2804:4c58::/33	Valid	Other IRR onlyTC	634 100%	67
2804:4c58:8000::/33	Valid	Other IRR onlyTC	634 100%	67

AS-SET

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

Route object: RIR8
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	45.234.128.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.234.128.0/23	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.234.130.0/23	Route object only in TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.234.128.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	45.234.129.0/24	Route object only in TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	2804:4c58::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:4c58::/33	Route object only in TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:4c58:8000::/33	Route object only in TC. Add it in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

45.234.128.0/22

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

671 of 673

Route object: RIR

45.234.128.0/23

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

671 of 673

Route object: RIR

45.234.130.0/23

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

671 of 673

Route object: RIR

45.234.128.0/24

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

670 of 673

Route object: RIR

45.234.129.0/24

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

670 of 673

Route object: RIR

2804:4c58::/32

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

634 of 636

Route object: RIR

2804:4c58::/33

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

634 of 636

Route object: RIR

2804:4c58:8000::/33

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

634 of 636

Route objects not announced

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


45.234.130.0/24	TC	Valid
45.234.131.0/24	TC	Valid
2804:4c58::/34	TC	Valid
2804:4c58:4000::/34	TC	Valid
2804:4c58:8000::/34	TC	Valid
2804:4c58:c000::/34	TC	Valid

45.234.130.0/24

Valid

45.234.131.0/24

Valid

2804:4c58::/34

Valid

2804:4c58:4000::/34

Valid

2804:4c58:8000::/34

Valid

2804:4c58:c000::/34

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.