bgpreport

Network · data from 2026-11-12

AS274913 HCTERCOM DOMINICANA, SRL

Registry name: AS274913 - HCTERCOM DOMINICANA, SRL, DO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274913, 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.
84.75.247.0/24 Valid Nonecovered by 84.75.246.0/23 669 99% 67
154.88.181.0/24 Valid Nonecovered by 154.88.180.0/23 668 99% 67
84.75.246.0/24 Valid Nonecovered by 84.75.246.0/23 667 99% 67
154.88.180.0/24 Valid Nonecovered by 154.88.180.0/23 2 0%low visibility 2
2803:be30::/32 Valid RIR databaseLACNIC 632 99% 67

AS-SET

AS274913'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 6 are in fix.csv.

  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none84.75.247.0/24No route object for it. A route object for 84.75.246.0/23 with origin AS274913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274913 in the RIR database for the space.669 of 673
Route object: none154.88.181.0/24No route object for it. A route object for 154.88.180.0/23 with origin AS274913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274913 in the RIR database for the space.668 of 673
Route object: none84.75.246.0/24No route object for it. A route object for 84.75.246.0/23 with origin AS274913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274913 in the RIR database for the space.667 of 673
Route object: none154.88.180.0/24No route object for it. A route object for 154.88.180.0/23 with origin AS274913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274913 in the RIR database for the space.2 of 673

Route objects not announced

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

84.75.246.0/23RADB, RIPEValid
154.88.180.0/23AFRINIC, 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.