bgpreport

Network · data from 2026-11-12

AS213724 FnA Maximum-Net LLC

Registry name: FnA Maximum-Net LLC, UA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213724, 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.
208.98.127.0/24 No ROA Other IRR onlyALTDB 666 99% 66
31.57.103.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
88.135.69.0/24 Valid RIR databaseRIPE 673 100% 66
109.122.4.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
31.57.230.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
31.58.40.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
82.24.191.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
82.198.249.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
82.198.251.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
85.117.231.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
151.242.155.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
185.243.154.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
31.57.111.0/24 Valid RIR databaseRADB, RIPE 668 99% 67

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none208.98.127.0/24No ROA covers it. Add a ROA for AS213724, maxLength 24.666 of 673
Route object: RIR208.98.127.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

65.162.108.0/24ALTDBNo ROA
195.128.25.0/24RIPEInvalid: origin

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.