bgpreport

Network · data from 2026-11-12

AS273619 ION TELECOMUNICACOES

Registry name: AS273619 - ION TELECOMUNICACOES LTDA, BR · PeeringDB

4IPv4 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 AS273619, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273619, 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.191.188.0/24 Valid Other IRR onlyRADB 672 100% 67
38.191.189.0/24 Valid Other IRR onlyRADB 672 100% 67
2804:89ac::/32 Valid Other IRR onlyRADB, TC 629 99% 67
2804:89ac::/33 Valid Other IRR onlyRADB 629 99% 67
2804:89ac:8000::/34 Valid Other IRR onlyRADB 629 99% 67
38.19.56.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.191.188.0/23 Valid RIR databaseARIN 672 100% 67

AS-SET

AS273619'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 5 are in fix.csv.

  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
Route object: RIR38.191.188.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.191.189.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:89ac::/32Route object only in RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:89ac::/33Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:89ac:8000::/34Route object only in RADB. Add it in the RIR database for the space.629 of 636

Route objects not announced

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