bgpreport

Network · data from 2026-11-12

AS273230 SDI DOMINICANA

Registry name: AS273230 - SDI DOMINICANA, S.R.L., DO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273230, 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.
206.84.94.0/24 Valid Nonecovered by 206.84.94.0/23 672 100% 67
206.84.95.0/24 Valid Nonecovered by 206.84.94.0/23 672 100% 67
206.84.94.0/23 Valid RIR databaseARIN 673 100% 67
38.196.251.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2803:5e50::/32 Valid RIR databaseLACNIC 635 100% 67
2803:5e50:5::/48 Valid RIR databaseLACNIC 635 100% 67
2803:5e50:6::/48 Valid RIR databaseLACNIC 635 100% 67
2803:5e50:4::/48 Valid RIR databaseLACNIC 634 100% 67
2803:5e50:2::/48 Valid RIR databaseLACNIC 632 99% 67

AS-SET

AS273230'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 21 are in fix.csv.

  • Route object: none2
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: none206.84.94.0/24No route object for it. A route object for 206.84.94.0/23 with origin AS273230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273230 in the RIR database for the space.672 of 673
Route object: none206.84.95.0/24No route object for it. A route object for 206.84.94.0/23 with origin AS273230 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273230 in the RIR database for the space.672 of 673

Route objects not announced

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

2803:5e50:1::/48LACNICValid
2803:5e50:3::/48LACNICValid
2803:5e50:7::/48LACNICValid
2803:5e50:8::/48LACNICValid
2803:5e50:9::/48LACNICValid
2803:5e50:a::/48LACNICValid
2803:5e50:b::/48LACNICValid
2803:5e50:10::/48LACNICValid
2803:5e50:11::/48LACNICValid
2803:5e50:12::/48LACNICValid
2803:5e50:13::/48LACNICValid
2803:5e50:14::/48LACNICValid
2803:5e50:15::/48LACNICValid
2803:5e50:16::/48LACNICValid
2803:5e50:17::/48LACNICValid
2803:5e50:18::/48LACNICValid
2803:5e50:19::/48LACNICValid
2803:5e50:20::/48LACNICValid
2803:5e50:ffff::/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.