bgpreport

Network · data from 2026-11-12

AS26068 OnShore, Inc.

Registry name: ONSH-NET-CHGO-BLK01 - OnShore, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26068, 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.98.180.0/24 No ROA None 670 100% 67
66.146.192.0/20 No ROA Other IRR onlyRADB 671 100% 68
66.146.208.0/21 No ROA Other IRR onlyRADB 671 100% 68
66.146.216.0/22 No ROA Other IRR onlyRADB 671 100% 68
66.146.221.0/24 No ROA Other IRR onlyRADB 671 100% 68
66.146.222.0/23 No ROA Other IRR onlyRADB 671 100% 68
66.251.224.0/20 No ROA Other IRR onlyRADB 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS26068: AS26068:AS-CONE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS26068 isn't in the set, or no route object for AS26068 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS26068 in itNot covered
AS26068:AS-CONE RADB 6120 Yes 1

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

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none38.98.180.0/24No ROA covers it. Add a ROA for AS26068, maxLength 24.670 of 673
Route object: none38.98.180.0/24No route object for it. Add a route object with origin AS26068 in the RIR database for the space.670 of 673
ROA: none66.146.192.0/20No ROA covers it. Add a ROA for AS26068, maxLength 20.671 of 673
Route object: RIR66.146.192.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.146.208.0/21No ROA covers it. Add a ROA for AS26068, maxLength 21.671 of 673
Route object: RIR66.146.208.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.146.216.0/22No ROA covers it. Add a ROA for AS26068, maxLength 22.671 of 673
Route object: RIR66.146.216.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.146.221.0/24No ROA covers it. Add a ROA for AS26068, maxLength 24.671 of 673
Route object: RIR66.146.221.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.146.222.0/23No ROA covers it. Add a ROA for AS26068, maxLength 23.671 of 673
Route object: RIR66.146.222.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.251.224.0/20No ROA covers it. Add a ROA for AS26068, maxLength 20.671 of 673
Route object: RIR66.251.224.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS26068 is announced.

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.