bgpreport

Network · data from 2026-11-12

AS973 REVIVE-IT-NETWORK - Revive IT Solutions LLC

Registry name: REVIVE-IT-NETWORK - Revive IT Solutions LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS973, 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.
89.251.24.0/24 Invalid: origin Other origin only 2 0%low visibility 2
38.107.215.0/24 No ROA None 672 100% 67
38.107.255.0/24 No ROA None 672 100% 67
31.58.100.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.153.224.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
109.234.215.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
151.242.110.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.160.21.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
209.151.108.0/24 Valid RIR databaseARIN 673 100% 67
209.151.109.0/24 Valid RIR databaseARIN 673 100% 67
209.151.110.0/24 Valid RIR databaseARIN 673 100% 67
209.151.111.0/24 Valid RIR databaseARIN 673 100% 67
212.69.31.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
45.152.240.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

AS973 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.

  • ROA: origin1
  • ROA: none2
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin89.251.24.0/24ROAs covering it name AS219048, not AS973. If AS973 should announce it, add a ROA for AS973.2 of 673
Route object: none89.251.24.0/24Route objects for it name AS219048. Add a route object with origin AS973 in the RIR database for the space.2 of 673
ROA: none38.107.215.0/24No ROA covers it. Add a ROA for AS973, maxLength 24.672 of 673
Route object: none38.107.215.0/24No route object for it. Add a route object with origin AS973 in the RIR database for the space.672 of 673
ROA: none38.107.255.0/24No ROA covers it. Add a ROA for AS973, maxLength 24.672 of 673
Route object: none38.107.255.0/24No route object for it. Add a route object with origin AS973 in the RIR database for the space.672 of 673

Route objects not announced

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