bgpreport

Network · data from 2026-11-12

AS1286 IVAS01

Registry name: IVAS01 - Altay Corporation, US · PeeringDB

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

Announced routes

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

8.15.201.0/24 No ROA Other IRR onlyRADB 673 100% 67
38.67.136.0/23 No ROA Other IRR onlyRADB 673 100% 67
38.106.7.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.74.130.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.74.131.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.74.136.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.98.53.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.99.250.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.106.28.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.106.29.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.106.32.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.106.33.0/24 No ROA Other IRR onlyRADB 670 100% 68
64.208.102.0/24 No ROA Other IRR onlyRADB 670 100% 68
162.97.198.0/24 No ROA Other IRR onlyRADB 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS1286: RADB::AS1286:AS-ALL. 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 (AS1286 isn't in the set, or no route object for AS1286 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 objectsAS1286 in itNot covered
RADB::AS1286:AS-ALL RADB 1114 Yes 0

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

  • ROA: none14
  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
ROA: none8.15.201.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.673 of 673
Route object: RIR8.15.201.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.67.136.0/23No ROA covers it. Add a ROA for AS1286, maxLength 23.673 of 673
Route object: RIR38.67.136.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.106.7.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.672 of 673
Route object: RIR38.106.7.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.74.130.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.74.130.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.74.131.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.74.131.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.74.136.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.74.136.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.98.53.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.98.53.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.99.250.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.99.250.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.106.28.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.106.28.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.106.29.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.106.29.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.106.32.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.106.32.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.106.33.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR38.106.33.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none64.208.102.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR64.208.102.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none162.97.198.0/24No ROA covers it. Add a ROA for AS1286, maxLength 24.670 of 673
Route object: RIR162.97.198.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Every route object with origin AS1286 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.