bgpreport

Network · data from 2026-11-12

AS52441 SONDA - DC Quiliicura

Registry name: AS52441 - SONDA S.A., CL · PeeringDB

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

Announced routes

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

198.41.46.0/24 Valid None 671 100% 67
198.41.42.0/24 Valid Other IRR onlyNTTCOM 666 99% 67
198.41.43.0/24 Valid Other IRR onlyNTTCOM 666 99% 67
198.41.44.0/24 Valid Other IRR onlyNTTCOM 666 99% 67
198.41.45.0/24 Valid Other IRR onlyNTTCOM 666 99% 67

AS-SET

AS52441'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: none1
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none198.41.46.0/24No route object for it. Add a route object with origin AS52441 in the RIR database for the space.671 of 673
Route object: RIR198.41.42.0/24Route object only in NTTCOM. Add it in the RIR database for the space.666 of 673
Route object: RIR198.41.43.0/24Route object only in NTTCOM. Add it in the RIR database for the space.666 of 673
Route object: RIR198.41.44.0/24Route object only in NTTCOM. Add it in the RIR database for the space.666 of 673
Route object: RIR198.41.45.0/24Route object only in NTTCOM. Add it in the RIR database for the space.666 of 673

Route objects not announced

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