bgpreport

Network · data from 2026-11-12

AS272869 INTERCOMM DE NARIÑO SAS

Registry name: AS272869 - INTERCOMM DE NARINO SAS, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272869, 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.
185.240.215.0/24 Invalid: origin None 2 0%low visibility 2
185.244.235.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
38.51.243.0/24 Valid RIR databaseARIN 670 100% 67
209.61.12.0/24 Valid RIR databaseARIN, RADB 669 99% 67
2803:7290:1b00::/40 Valid RIR databaseLACNIC 636 100% 67
2803:7290:1c00::/40 Valid RIR databaseLACNIC 636 100% 67
2803:7290:200::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:300::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:400::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:800::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:900::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:b00::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:c00::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:d00::/40 Valid RIR databaseLACNIC 634 100% 69
2803:7290:e00::/40 Valid RIR databaseLACNIC 634 100% 69

AS-SET

AS272869's PeeringDB record names no 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: origin1
  • Route object: none1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: origin185.240.215.0/24ROAs covering it name AS34760, not AS272869. If AS272869 should announce it, add a ROA for AS272869.2 of 673
Route object: none185.240.215.0/24No route object for it. Add a route object with origin AS272869 in the RIR database for the space.2 of 673

Route objects not announced

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

2803:7290::/32RADBNo ROA
2803:7290:100::/40LACNICValid
2803:7290:500::/40LACNICValid
2803:7290:600::/40LACNICValid
2803:7290:700::/40LACNICValid
2803:7290:a00::/40LACNICValid
2803:7290:f00::/40LACNICValid
2803:7290:1000::/40LACNICValid
2803:7290:1100::/40LACNICValid
2803:7290:1200::/40LACNICValid
2803:7290:1300::/40LACNICValid
2803:7290:1400::/40LACNICValid
2803:7290:1500::/40LACNICValid
2803:7290:1600::/40LACNICValid
2803:7290:1700::/40LACNICValid
2803:7290:1800::/40LACNICValid
2803:7290:1900::/40LACNICValid
2803:7290:1a00::/40LACNICValid

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.