bgpreport

Network · data from 2026-11-12

AS61503 SERVICIOS DE TELECOMUNICACIONES INTERCABLE

Registry name: AS61503 - SERVICIOS DE TELECOMUNICACIONES INTERCABLE LTDA., CL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61503, 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.250.124.0/22 Invalid: origin None 35 5%low visibility 23
38.250.124.0/24 Invalid: origin None 35 5%low visibility 23
38.250.125.0/24 Invalid: origin None 35 5%low visibility 23
38.250.126.0/24 Invalid: origin None 35 5%low visibility 23
38.250.127.0/24 Invalid: origin None 35 5%low visibility 23
2803:2f80::/32 No ROA Other origin only 635 100% 67
2803:2f80::/48 No ROA None 630 99% 67
2803:2f80:1::/48 No ROA None 630 99% 67
2803:2f80:2::/48 No ROA None 630 99% 67
138.36.252.0/24 Valid Nonecovered by 138.36.252.0/22 669 99% 67
138.36.253.0/24 Valid Nonecovered by 138.36.252.0/22 669 99% 67
138.36.255.0/24 Valid Nonecovered by 138.36.252.0/22 669 99% 67
138.36.252.0/22 Valid RIR databaseALTDB, LACNIC, RADB 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS61503: AS61503:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS61503 isn't in the set, or no route object for AS61503 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS61503 in itNot covered
AS61503:AS-CUSTOMERS LACNIC 221112 Yes 9

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

  • ROA: origin5
  • ROA: none4
  • Route object: none12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin38.250.124.0/22An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61503 should announce it, add a ROA for AS61503.35 of 673
Route object: none38.250.124.0/22No route object for it. Add a route object with origin AS61503 in the RIR database for the space.35 of 673
ROA: origin38.250.124.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61503 should announce it, add a ROA for AS61503.35 of 673
Route object: none38.250.124.0/24No route object for it. Add a route object with origin AS61503 in the RIR database for the space.35 of 673
ROA: origin38.250.125.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61503 should announce it, add a ROA for AS61503.35 of 673
Route object: none38.250.125.0/24No route object for it. Add a route object with origin AS61503 in the RIR database for the space.35 of 673
ROA: origin38.250.126.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61503 should announce it, add a ROA for AS61503.35 of 673
Route object: none38.250.126.0/24No route object for it. Add a route object with origin AS61503 in the RIR database for the space.35 of 673
ROA: origin38.250.127.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS61503 should announce it, add a ROA for AS61503.35 of 673
Route object: none38.250.127.0/24No route object for it. Add a route object with origin AS61503 in the RIR database for the space.35 of 673
ROA: none2803:2f80::/32No ROA covers it. Add a ROA for AS61503, maxLength 32.635 of 636
Route object: none2803:2f80::/32Route objects for it name AS25703, AS269733. Add a route object with origin AS61503 in the RIR database for the space.635 of 636
ROA: none2803:2f80::/48No ROA covers it. Add a ROA for AS61503, maxLength 48.630 of 636
Route object: none2803:2f80::/48No route object for it. Add a route object with origin AS61503 in the RIR database for the space.630 of 636
ROA: none2803:2f80:1::/48No ROA covers it. Add a ROA for AS61503, maxLength 48.630 of 636
Route object: none2803:2f80:1::/48No route object for it. Add a route object with origin AS61503 in the RIR database for the space.630 of 636
ROA: none2803:2f80:2::/48No ROA covers it. Add a ROA for AS61503, maxLength 48.630 of 636
Route object: none2803:2f80:2::/48No route object for it. Add a route object with origin AS61503 in the RIR database for the space.630 of 636
Route object: none138.36.252.0/24No route object for it. A route object for 138.36.252.0/22 with origin AS61503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61503 in the RIR database for the space.669 of 673
Route object: none138.36.253.0/24No route object for it. A route object for 138.36.252.0/22 with origin AS61503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61503 in the RIR database for the space.669 of 673
Route object: none138.36.255.0/24No route object for it. A route object for 138.36.252.0/22 with origin AS61503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61503 in the RIR database for the space.669 of 673

Route objects not announced

Route objects with origin AS61503 whose prefix no peer sees AS61503 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.181.120.0/22LACNICValid
2803:2f80:1701::/64RADBNo ROA

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.