bgpreport

Network · data from 2026-11-12

AS268229 VIA ONDAS TELECOMUNICACOES LTDA

Registry name: AS268229 - VIA ONDAS TELECOMUNICACOES LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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 AS268229, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268229, 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.235.200.0/22 Valid Other IRR onlyRADB, TC 668 99% 66
45.235.200.0/23 Valid Other IRR onlyRADB, TC 668 99% 66
45.235.202.0/23 Valid Other IRR onlyRADB, TC 668 99% 66
2804:4df0::/32 Valid Other IRR onlyRADB, TC 630 99% 69
2804:4df0::/34 Valid Other IRR onlyRADB, TC 630 99% 69
2804:4df0:4000::/34 Valid Other IRR onlyRADB, TC 630 99% 69
2804:4df0:8000::/34 Valid Other IRR onlyRADB, TC 630 99% 69
2804:4df0:c000::/34 Valid Other IRR onlyRADB, TC 630 99% 69
2804:4df0::/35 Valid Other IRR onlyRADB, TC 463 73% 65
45.235.202.0/24 Valid Other IRR onlyRADB, TC 428 64% 60
45.235.203.0/24 Valid Other IRR onlyRADB, TC 428 64% 60
45.235.200.0/24 Valid Other IRR onlyRADB, TC 421 63% 60
45.235.201.0/24 Valid Other IRR onlyRADB, TC 421 63% 60

AS-SET

AS268229'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 13 are in fix.csv.

  • Route object: RIR13
ChangePrefix or setDetailFull-table peers
Route object: RIR45.235.200.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.235.200.0/23Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR45.235.202.0/23Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:4df0::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:4df0::/34Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:4df0:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:4df0:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:4df0:c000::/34Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:4df0::/35Route object only in RADB, TC. Add it in the RIR database for the space.463 of 636
Route object: RIR45.235.202.0/24Route object only in RADB, TC. Add it in the RIR database for the space.428 of 673
Route object: RIR45.235.203.0/24Route object only in RADB, TC. Add it in the RIR database for the space.428 of 673
Route object: RIR45.235.200.0/24Route object only in RADB, TC. Add it in the RIR database for the space.421 of 673
Route object: RIR45.235.201.0/24Route object only in RADB, TC. Add it in the RIR database for the space.421 of 673

Route objects not announced

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