bgpreport

Network · data from 2026-11-12

AS272190 AS272190 - I9 COMERCIO E SERVICOS DE TELECOMUNICACAO

Registry name: AS272190 - I9 COMERCIO E SERVICOS DE TELECOMUNICACAO, BR · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
18Route objects not announced registered with origin AS272190, seen from no peer

Announced routes

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

38.159.164.0/24 No ROA None 152 23% 50
2804:8350:8400::/39 No ROA Other IRR onlyRADB 635 100% 68
2804:8350::/32 No ROA Other IRR onlyALTDB, RADB, TC 634 100% 67

AS-SET

AS272190 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 24 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none38.159.164.0/24No ROA covers it. Add a ROA for AS272190, maxLength 24.152 of 673
Route object: none38.159.164.0/24No route object for it. Add a route object with origin AS272190 in the RIR database for the space.152 of 673
ROA: none2804:8350:8400::/39No ROA covers it. Add a ROA for AS272190, maxLength 39.635 of 636
Route object: RIR2804:8350:8400::/39Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:8350::/32No ROA covers it. Add a ROA for AS272190, maxLength 32.634 of 636
Route object: RIR2804:8350::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2804:8350::/33TCNo ROA
2804:8350::/36TCNo ROA
2804:8350:1000::/36TCNo ROA
2804:8350:2000::/36TCNo ROA
2804:8350:3000::/36TCNo ROA
2804:8350:4000::/36TCNo ROA
2804:8350:5000::/36TCNo ROA
2804:8350:6000::/36TCNo ROA
2804:8350:7000::/36TCNo ROA
2804:8350:8000::/33TCNo ROA
2804:8350:8000::/36TCNo ROA
2804:8350:9000::/36TCNo ROA
2804:8350:a000::/36TCNo ROA
2804:8350:b000::/36TCNo ROA
2804:8350:c000::/36TCNo ROA
2804:8350:d000::/36TCNo ROA
2804:8350:e000::/36TCNo ROA
2804:8350:f000::/36TCNo ROA

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.