bgpreport

Network · data from 2026-11-12

AS269420 AS269420 - IST INFORMATICA E TELECOMUNICAO 991DF EIRELI - ME

Registry name: AS269420 - IST INFORMATICA E TELECOMUNICAO 991DF EIRELI - ME, BR · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
6Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS269420, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269420, 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.186.116.0/22 Valid Other IRR onlyRADB, TC 665 99% 67
2804:6450::/32 Valid Other IRR onlyRADB, TC 629 99% 67
2804:6450:100::/40 Valid Other IRR onlyTC 629 99% 67
2804:6450:6500::/40 Valid Other IRR onlyTC 629 99% 67
2804:6450:7100::/40 Valid Other IRR onlyTC 629 99% 67
2804:6450:7200::/40 Valid Other IRR onlyTC 629 99% 67
45.186.116.0/23 Valid Other IRR onlyRADB, TC 34 5%low visibility 12
45.186.117.0/24 Valid Other IRR onlyRADB, TC 34 5%low visibility 12
45.186.118.0/23 Valid Other IRR onlyRADB, TC 34 5%low visibility 12
45.186.118.0/24 Valid Other IRR onlyRADB, TC 34 5%low visibility 12
45.186.116.0/24 Valid Other IRR onlyRADB, TC 33 5%low visibility 11
45.186.119.0/24 Valid Other IRR onlyRADB, TC 33 5%low visibility 11

AS-SET

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

  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: RIR45.186.116.0/22Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:6450::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6450:100::/40Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6450:6500::/40Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6450:7100::/40Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:6450:7200::/40Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR45.186.116.0/23Route object only in RADB, TC. Add it in the RIR database for the space.34 of 673
Route object: RIR45.186.117.0/24Route object only in RADB, TC. Add it in the RIR database for the space.34 of 673
Route object: RIR45.186.118.0/23Route object only in RADB, TC. Add it in the RIR database for the space.34 of 673
Route object: RIR45.186.118.0/24Route object only in RADB, TC. Add it in the RIR database for the space.34 of 673
Route object: RIR45.186.116.0/24Route object only in RADB, TC. Add it in the RIR database for the space.33 of 673
Route object: RIR45.186.119.0/24Route object only in RADB, TC. Add it in the RIR database for the space.33 of 673

Route objects not announced

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