bgpreport

Network · data from 2026-11-12

AS34985 NETINNOVATIONLLC-AS-AP - Net Innovation LLC

Registry name: NETINNOVATIONLLC-AS-AP - Net Innovation LLC, US · not in PeeringDB

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

Announced routes

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

103.125.248.0/24 No ROA Other IRR onlyRADB 665 99% 67
45.135.48.0/24 No ROA Other IRR onlyRADB 659 98% 67
103.96.0.0/24 Valid Other IRR onlyRADB 665 99% 67
103.96.2.0/24 Valid Other IRR onlyRADB 665 99% 67
103.96.3.0/24 Valid Other IRR onlyRADB 665 99% 67
185.254.240.0/24 Valid Other IRR onlyRADB 665 99% 67
194.246.40.0/24 Valid Other IRR onlyRADB 665 99% 67
194.246.41.0/24 Valid Other IRR onlyRADB 665 99% 67
194.246.42.0/24 Valid Other IRR onlyRADB 665 99% 67
194.246.43.0/24 Valid Other IRR onlyRADB 665 99% 67
213.139.233.0/24 Valid Other IRR onlyRADB 665 99% 67

AS-SET

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

  • ROA: none2
  • Route object: RIR11
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none103.125.248.0/24No ROA covers it. Add a ROA for AS34985, maxLength 24.665 of 673
Route object: RIR103.125.248.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none45.135.48.0/24No ROA covers it. Add a ROA for AS34985, maxLength 24.659 of 673
Route object: RIR45.135.48.0/24Route object only in RADB. Add it in the RIR database for the space.659 of 673
Route object: RIR103.96.0.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR103.96.2.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR103.96.3.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR185.254.240.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR194.246.40.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR194.246.41.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR194.246.42.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR194.246.43.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR213.139.233.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673

Route objects not announced

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

103.150.225.0/24RADBNo ROA
160.116.44.0/22AFRINICNo ROA
160.116.52.0/22AFRINICNo ROA
160.116.56.0/22AFRINICNo ROA
160.116.64.0/22AFRINICNo ROA
160.116.100.0/22AFRINICNo ROA
160.116.104.0/22AFRINICNo ROA
160.116.112.0/22AFRINICNo ROA
160.116.116.0/22AFRINICNo ROA
160.116.124.0/22AFRINICNo ROA
169.129.99.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.