bgpreport

Network · data from 2026-11-12

AS270124 AS270124 - SCONTINUIDAD LATAM, S.A. DE C.V.

Registry name: AS270124 - SCONTINUIDAD LATAM, S.A. DE C.V., MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270124, 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.
201.159.80.0/24 No ROA Other origin onlycovered by 201.159.80.0/22 672 100% 67
201.159.81.0/24 No ROA Other origin onlycovered by 201.159.80.0/22 672 100% 67
201.159.82.0/24 No ROA Nonecovered by 201.159.80.0/22 672 100% 67
201.159.83.0/24 No ROA Nonecovered by 201.159.80.0/22 672 100% 67
2801:c4:3a::/48 No ROA Other origin only 633 100% 68
201.159.80.0/22 No ROA Other IRR onlyRADB 672 100% 67
2806:3ca::/32 No ROA Other IRR onlyRADB 635 100% 70

AS-SET

AS270124 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none201.159.80.0/24No ROA covers it. Add a ROA for AS270124, maxLength 24.672 of 673
Route object: none201.159.80.0/24Route objects for it name AS16531. A route object for 201.159.80.0/22 with origin AS270124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270124 in the RIR database for the space.672 of 673
ROA: none201.159.81.0/24No ROA covers it. Add a ROA for AS270124, maxLength 24.672 of 673
Route object: none201.159.81.0/24Route objects for it name AS11172. A route object for 201.159.80.0/22 with origin AS270124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270124 in the RIR database for the space.672 of 673
ROA: none201.159.82.0/24No ROA covers it. Add a ROA for AS270124, maxLength 24.672 of 673
Route object: none201.159.82.0/24No route object for it. A route object for 201.159.80.0/22 with origin AS270124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270124 in the RIR database for the space.672 of 673
ROA: none201.159.83.0/24No ROA covers it. Add a ROA for AS270124, maxLength 24.672 of 673
Route object: none201.159.83.0/24No route object for it. A route object for 201.159.80.0/22 with origin AS270124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270124 in the RIR database for the space.672 of 673
ROA: none2801:c4:3a::/48No ROA covers it. Add a ROA for AS270124, maxLength 48.633 of 636
Route object: none2801:c4:3a::/48Route objects for it name AS270171. Add a route object with origin AS270124 in the RIR database for the space.633 of 636
ROA: none201.159.80.0/22No ROA covers it. Add a ROA for AS270124, maxLength 22.672 of 673
Route object: RIR201.159.80.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2806:3ca::/32No ROA covers it. Add a ROA for AS270124, maxLength 32.635 of 636
Route object: RIR2806:3ca::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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