bgpreport

Network · data from 2026-11-12

AS269918 SISTEMAS TELCORP, C.A.

Registry name: AS269918 - SISTEMAS TELCORP, C.A., VE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269918, 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.
131.72.168.0/22 No ROA None 1 0%low visibility 1
131.72.168.0/24 Valid RIR databaseLACNIC, RADB 672 100% 66
131.72.169.0/24 Valid RIR databaseLACNIC, RADB 672 100% 66
131.72.170.0/24 Valid RIR databaseLACNIC, RADB 672 100% 66
131.72.171.0/24 Valid RIR databaseLACNIC, RADB 672 100% 66
2803:dd80::/32 Valid RIR databaseLACNIC, RADB 631 99% 68

AS-SET

PeeringDB's irr_as_set for AS269918: AS269918:AS-CUSTOMERS AS269918:AS-UPSTREAMS. 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 (AS269918 isn't in the set, or no route object for AS269918 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 objectsAS269918 in itNot covered
AS269918:AS-CUSTOMERS LACNIC 4135 Yes 1
AS269918:AS-UPSTREAMS LACNIC 21197 No 6

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

  • ROA: none1
  • Route object: none1
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none131.72.168.0/22No ROA covers it. Add a ROA for AS269918, maxLength 22.1 of 673
Route object: none131.72.168.0/22No route object for it. Add a route object with origin AS269918 in the RIR database for the space.1 of 673
AS-SET: own ASNAS269918:AS-UPSTREAMSAS269918 isn't in AS269918:AS-UPSTREAMS (LACNIC) once expanded. Add AS269918 to it.

Route objects not announced

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