bgpreport

Network · data from 2026-11-12

AS397880 Mitec Solutions

Registry name: SKYWIRE-ASN - Mitec Solutions, US · PeeringDB

7IPv4 routes 85.7% RPKI valid · 85.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS397880, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS397880, 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.45.30.0/24 No ROA None 672 100% 67
45.41.26.0/23 Valid RIR databaseARIN 673 100% 67
72.172.68.0/22 Valid RIR databaseARIN 673 100% 67
140.235.186.0/23 Valid RIR databaseARIN 673 100% 67
158.51.66.0/23 Valid RIR databaseARIN 673 100% 67
161.199.71.0/24 Valid RIR databaseARIN 673 100% 67
161.199.82.0/24 Valid RIR databaseARIN 673 100% 67
2605:dbc0::/32 Valid RIR databaseARIN 635 100% 67

AS-SET

AS397880's PeeringDB record names no 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none8.45.30.0/24No ROA covers it. Add a ROA for AS397880, maxLength 24.672 of 673
Route object: none8.45.30.0/24No route object for it. Add a route object with origin AS397880 in the RIR database for the space.672 of 673

Route objects not announced

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