bgpreport

Network · data from 2026-11-12

AS3152 FNAL-AS - Fermi National Accelerator Laboratory (Fermilab)

Registry name: FNAL-AS - Fermi National Accelerator Laboratory (Fermilab), US · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
8Route objects not announced registered with origin AS3152, seen from no peer

Announced routes

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

192.190.216.0/22 No ROA Other IRR onlyRADB 670 100% 70
198.49.208.0/24 Valid RIR databaseARIN, RADB 670 100% 69
131.225.0.0/16 Valid RIR databaseARIN, RADB 667 99% 69
2620:6a::/48 Valid RIR databaseARIN 636 100% 70

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none192.190.216.0/22No ROA covers it. Add a ROA for AS3152, maxLength 22.670 of 673
Route object: RIR192.190.216.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

192.190.216.0/24ARINValid
192.190.217.0/24ARINValid
192.190.218.0/24ARINValid
192.190.219.0/24ARINValid
198.124.72.0/23ARINValid
198.125.48.0/22ARINValid
198.125.52.0/22ARINValid
198.151.133.0/24ARIN, RADBValid

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.