bgpreport

Network · data from 2026-11-12

AS272865 INVERSIONES SMARTBYTE

Registry name: AS272865 - INVERSIONES SMARTBYTE, C.A., VE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272865, 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.
170.244.90.0/24 Invalid: origin Other origin only 1 0%low visibility 1
38.188.96.0/23 Valid Nonecovered by 38.188.96.0/22 672 100% 67
38.125.236.0/24 Valid Nonecovered by 38.125.236.0/22 671 100% 67
38.188.98.0/24 Valid Nonecovered by 38.188.96.0/22 671 100% 67
38.188.99.0/24 Valid Nonecovered by 38.188.96.0/22 671 100% 67
38.135.150.0/24 Valid RIR databaseARIN 672 100% 67
191.97.17.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
2803:2230::/32 Valid RIR databaseLACNIC, RADB 635 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin170.244.90.0/24ROAs covering it name AS264844, AS274286, not AS272865. If AS272865 should announce it, add a ROA for AS272865.1 of 673
Route object: none170.244.90.0/24Route objects for it name AS264844, AS274286. Add a route object with origin AS272865 in the RIR database for the space.1 of 673
Route object: none38.188.96.0/23No route object for it. A route object for 38.188.96.0/22 with origin AS272865 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272865 in the RIR database for the space.672 of 673
Route object: none38.125.236.0/24No route object for it. A route object for 38.125.236.0/22 with origin AS272865 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272865 in the RIR database for the space.671 of 673
Route object: none38.188.98.0/24No route object for it. A route object for 38.188.96.0/22 with origin AS272865 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272865 in the RIR database for the space.671 of 673
Route object: none38.188.99.0/24No route object for it. A route object for 38.188.96.0/22 with origin AS272865 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272865 in the RIR database for the space.671 of 673

Route objects not announced

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

38.125.236.0/22ARIN, RADBValid
38.188.96.0/22ARIN, RADBValid
160.238.245.0/24RADBNo ROA

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.