bgpreport

Network · data from 2026-11-12

AS273158 273158

Registry name: AS273158 - INTERSAT DOMINICANA SRL, DO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273158, 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:c250:500::/48 Invalid: maxLength Nonecovered by 2803:c250::/32 19 3%low visibility 10
206.0.152.0/24 No ROA Nonecovered by 206.0.152.0/22 672 100% 67
206.0.153.0/24 No ROA Nonecovered by 206.0.152.0/22 672 100% 67
206.0.154.0/24 No ROA Nonecovered by 206.0.152.0/22 672 100% 67
206.0.155.0/24 No ROA Nonecovered by 206.0.152.0/22 672 100% 67
154.59.201.0/24 No ROA None 57 8%low visibility 33
2803:c250::/32 Valid RIR databaseLACNIC 635 100% 67

AS-SET

AS273158'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 22 are in fix.csv.

  • ROA: maxLength1
  • ROA: none5
  • Route object: none6
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: maxLength2803:c250:500::/48ROA 2803:c250::/32 AS273158 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2803:c250:500::/48.19 of 636
Route object: none2803:c250:500::/48No route object for it. A route object for 2803:c250::/32 with origin AS273158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273158 in the RIR database for the space.19 of 636
ROA: none206.0.152.0/24No ROA covers it. Add a ROA for AS273158, maxLength 24.672 of 673
Route object: none206.0.152.0/24No route object for it. A route object for 206.0.152.0/22 with origin AS273158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273158 in the RIR database for the space.672 of 673
ROA: none206.0.153.0/24No ROA covers it. Add a ROA for AS273158, maxLength 24.672 of 673
Route object: none206.0.153.0/24No route object for it. A route object for 206.0.152.0/22 with origin AS273158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273158 in the RIR database for the space.672 of 673
ROA: none206.0.154.0/24No ROA covers it. Add a ROA for AS273158, maxLength 24.672 of 673
Route object: none206.0.154.0/24No route object for it. A route object for 206.0.152.0/22 with origin AS273158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273158 in the RIR database for the space.672 of 673
ROA: none206.0.155.0/24No ROA covers it. Add a ROA for AS273158, maxLength 24.672 of 673
Route object: none206.0.155.0/24No route object for it. A route object for 206.0.152.0/22 with origin AS273158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273158 in the RIR database for the space.672 of 673
ROA: none154.59.201.0/24No ROA covers it. Add a ROA for AS273158, maxLength 24.57 of 673
Route object: none154.59.201.0/24No route object for it. Add a route object with origin AS273158 in the RIR database for the space.57 of 673

Route objects not announced

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

206.0.152.0/22RADBNo ROA
2803:c250:1::/48LACNICValid
2803:c250:2::/48LACNICValid
2803:c250:3::/48LACNICValid
2803:c250:4::/48LACNICValid
2803:c250:5::/48LACNICValid
2803:c250:6::/48LACNICValid
2803:c250:7::/48LACNICValid
2803:c250:8::/48LACNICValid
2803:c250:9::/48LACNICValid

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.