bgpreport

Network · data from 2026-11-12

AS269804 SEPCOM COMUNICACIONES SAS

Registry name: AS269804 - SEPCOM COMUNICACIONES SAS, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269804, 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.199.69.0/24 Invalid: origin Other origin only 28 4%low visibility 16
38.199.70.0/24 Invalid: origin Other origin only 2 0%low visibility 2
38.199.71.0/24 Invalid: origin Other origin only 2 0%low visibility 2
206.84.79.0/24 No ROA Other IRR onlyRADB 673 100% 67
45.167.124.0/24 Valid Other IRR onlyRADB 671 100% 67
45.167.125.0/24 Valid Other IRR onlyRADB 671 100% 67
2803:b5a0:c000::/34 Valid Other IRR onlyRADB 635 100% 67
2803:b5a0:8000::/34 Valid Other IRR onlyRADB 634 100% 67
2803:b5a0::/34 Valid Other IRR onlyRADB 632 99% 69
2803:b5a0:4000::/34 Valid Other IRR onlyRADB 632 99% 69
45.167.126.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67
38.211.68.0/24 Valid RIR databaseARIN, RADB 670 100% 67
38.211.69.0/24 Valid RIR databaseARIN, RADB 670 100% 67
2803:ed30::/32 Valid RIR databaseLACNIC, RADB 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS269804: AS269804: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 (AS269804 isn't in the set, or no route object for AS269804 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 objectsAS269804 in itNot covered
AS269804:AS-CUSTOMERS LACNIC 8192 Yes 3

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

  • ROA: origin3
  • ROA: none1
  • Route object: none3
  • Route object: RIR7
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin38.199.69.0/24ROAs covering it name AS272806, not AS269804. If AS269804 should announce it, add a ROA for AS269804.28 of 673
Route object: none38.199.69.0/24Route objects for it name AS272806. Add a route object with origin AS269804 in the RIR database for the space.28 of 673
ROA: origin38.199.70.0/24ROAs covering it name AS272806, not AS269804. If AS269804 should announce it, add a ROA for AS269804.2 of 673
Route object: none38.199.70.0/24Route objects for it name AS272806. Add a route object with origin AS269804 in the RIR database for the space.2 of 673
ROA: origin38.199.71.0/24ROAs covering it name AS272806, not AS269804. If AS269804 should announce it, add a ROA for AS269804.2 of 673
Route object: none38.199.71.0/24Route objects for it name AS272806. Add a route object with origin AS269804 in the RIR database for the space.2 of 673
ROA: none206.84.79.0/24No ROA covers it. Add a ROA for AS269804, maxLength 24.673 of 673
Route object: RIR206.84.79.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR45.167.124.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.167.125.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2803:b5a0:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2803:b5a0:8000::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2803:b5a0::/34Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2803:b5a0:4000::/34Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

38.211.68.0/22RADBNo ROA
38.211.68.0/23ARINValid
38.211.70.0/23ARINValid
45.167.124.0/23LACNIC, RADBValid
2803:b5a0::/32LACNIC, RADBValid

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.