bgpreport

Network · data from 2026-11-12

AS275071 AS275071 - RSS75

Registry name: AS275071 - RSS75, CO · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 20.0% with a route object
10IPv6 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
2Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS275071, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS275071, 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.

38.17.96.0/24 Valid Nonecovered by 38.17.96.0/22 666 99% 67
38.17.97.0/24 Valid Nonecovered by 38.17.96.0/22 666 99% 67
38.17.98.0/24 Valid Nonecovered by 38.17.96.0/22 666 99% 67
38.17.99.0/24 Valid Nonecovered by 38.17.96.0/22 666 99% 67
2803:20b0:5000::/36 Valid RIR databaseLACNIC 635 100% 67
2803:20b0:6000::/36 Valid RIR databaseLACNIC 635 100% 67
2803:20b0:7000::/36 Valid RIR databaseLACNIC 635 100% 67
2803:20b0:8000::/36 Valid RIR databaseLACNIC 635 100% 67
2803:20b0:9000::/36 Valid RIR databaseLACNIC 635 100% 67
2803:20b0:1000::/36 Valid RIR databaseLACNIC 634 100% 68
2803:20b0:2000::/36 Valid RIR databaseLACNIC 634 100% 68
2803:20b0:4000::/36 Valid RIR databaseLACNIC 634 100% 68
2803:20b0:3000::/36 Valid RIR databaseLACNIC 633 100% 68
38.17.96.0/22 Valid RIR databaseARIN, RADB 1 0%low visibility 2
2803:20b0::/32 Valid RIR databaseLACNIC, RADB 1 0%low visibility 1

AS-SET

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

  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none38.17.96.0/24No route object for it. A route object for 38.17.96.0/22 with origin AS275071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275071 in the RIR database for the space.666 of 673
Route object: none38.17.97.0/24No route object for it. A route object for 38.17.96.0/22 with origin AS275071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275071 in the RIR database for the space.666 of 673
Route object: none38.17.98.0/24No route object for it. A route object for 38.17.96.0/22 with origin AS275071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275071 in the RIR database for the space.666 of 673
Route object: none38.17.99.0/24No route object for it. A route object for 38.17.96.0/22 with origin AS275071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275071 in the RIR database for the space.666 of 673

Route objects not announced

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

2803:20b0:a000::/36LACNICValid
2803:20b0:b000::/36LACNICValid

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.