bgpreport

Network · data from 2026-11-12

AS271777 AS271777 - SITELCO SPA

Registry name: AS271777 - SITELCO SPA, CL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271777, 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.43.78.0/24 Invalid: origin None 3 0%low visibility 3
206.85.26.0/24 Invalid: origin Other origin only 3 0%low visibility 3
179.49.236.0/22 No ROA Other IRR onlyRADB 673 100% 66
38.7.220.0/24 No ROA Other IRR onlyRADB 110 16% 41
179.49.236.0/23 No ROA Other IRR onlyRADB 109 16% 41
179.49.236.0/24 No ROA Other IRR onlyRADB 109 16% 41
179.49.237.0/24 No ROA Other IRR onlyRADB 109 16% 41
179.49.238.0/23 No ROA Other IRR onlyRADB 109 16% 41
179.49.238.0/24 No ROA Other IRR onlyRADB 109 16% 41
179.49.239.0/24 No ROA Other IRR onlyRADB 109 16% 41

AS-SET

AS271777 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 20 are in fix.csv.

  • ROA: origin2
  • ROA: none8
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: origin38.43.78.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS271777 should announce it, add a ROA for AS271777.3 of 673
Route object: none38.43.78.0/24No route object for it. Add a route object with origin AS271777 in the RIR database for the space.3 of 673
ROA: origin206.85.26.0/24ROAs covering it name AS273238, not AS271777. If AS271777 should announce it, add a ROA for AS271777.3 of 673
Route object: none206.85.26.0/24Route objects for it name AS273238. Add a route object with origin AS271777 in the RIR database for the space.3 of 673
ROA: none179.49.236.0/22No ROA covers it. Add a ROA for AS271777, maxLength 22.673 of 673
Route object: RIR179.49.236.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.7.220.0/24No ROA covers it. Add a ROA for AS271777, maxLength 24.110 of 673
Route object: RIR38.7.220.0/24Route object only in RADB. Add it in the RIR database for the space.110 of 673
ROA: none179.49.236.0/23No ROA covers it. Add a ROA for AS271777, maxLength 23.109 of 673
Route object: RIR179.49.236.0/23Route object only in RADB. Add it in the RIR database for the space.109 of 673
ROA: none179.49.236.0/24No ROA covers it. Add a ROA for AS271777, maxLength 24.109 of 673
Route object: RIR179.49.236.0/24Route object only in RADB. Add it in the RIR database for the space.109 of 673
ROA: none179.49.237.0/24No ROA covers it. Add a ROA for AS271777, maxLength 24.109 of 673
Route object: RIR179.49.237.0/24Route object only in RADB. Add it in the RIR database for the space.109 of 673
ROA: none179.49.238.0/23No ROA covers it. Add a ROA for AS271777, maxLength 23.109 of 673
Route object: RIR179.49.238.0/23Route object only in RADB. Add it in the RIR database for the space.109 of 673
ROA: none179.49.238.0/24No ROA covers it. Add a ROA for AS271777, maxLength 24.109 of 673
Route object: RIR179.49.238.0/24Route object only in RADB. Add it in the RIR database for the space.109 of 673
ROA: none179.49.239.0/24No ROA covers it. Add a ROA for AS271777, maxLength 24.109 of 673
Route object: RIR179.49.239.0/24Route object only in RADB. Add it in the RIR database for the space.109 of 673

Route objects not announced

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