bgpreport

Network · data from 2026-11-12

AS274888 AS274888 - RASER TELECOMUNICACIONES SAS

Registry name: AS274888 - RASER TELECOMUNICACIONES SAS, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274888, 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.
2803:e630::/36 No ROA None 636 100% 67
2803:e630::/48 No ROA None 632 99% 67
2803:e630:1000::/36 No ROA Other IRR onlyRADB 634 100% 67
38.190.120.0/23 Valid Nonecovered by 38.190.120.0/22 672 100% 67
38.190.123.0/24 Valid Nonecovered by 38.190.120.0/22 671 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2803:e630::/36No ROA covers it. Add a ROA for AS274888, maxLength 36.636 of 636
Route object: none2803:e630::/36No route object for it. Add a route object with origin AS274888 in the RIR database for the space.636 of 636
ROA: none2803:e630::/48No ROA covers it. Add a ROA for AS274888, maxLength 48.632 of 636
Route object: none2803:e630::/48No route object for it. Add a route object with origin AS274888 in the RIR database for the space.632 of 636
ROA: none2803:e630:1000::/36No ROA covers it. Add a ROA for AS274888, maxLength 36.634 of 636
Route object: RIR2803:e630:1000::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: none38.190.120.0/23No route object for it. A route object for 38.190.120.0/22 with origin AS274888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274888 in the RIR database for the space.672 of 673
Route object: none38.190.123.0/24No route object for it. A route object for 38.190.120.0/22 with origin AS274888 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274888 in the RIR database for the space.671 of 673

Route objects not announced

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

38.190.120.0/22ARINValid

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.