bgpreport

Network · data from 2026-11-12

AS32123 Root Automation

Registry name: 4FAST-NET - Root Automation, US · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
0IPv6 routes
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
9Route objects not announced registered with origin AS32123, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS32123, 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.
209.232.198.0/23 No ROA None 672 100% 67
69.50.88.0/24 Valid RIR databaseARIN 673 100% 67
69.50.89.0/24 Valid RIR databaseARIN 673 100% 67
69.50.90.0/24 Valid RIR databaseARIN 673 100% 67
69.50.91.0/24 Valid RIR databaseARIN 673 100% 67
162.254.180.0/22 Valid RIR databaseARIN, RADB 673 100% 68

AS-SET

AS32123'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 11 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none209.232.198.0/23No ROA covers it. Add a ROA for AS32123, maxLength 23.672 of 673
Route object: none209.232.198.0/23No route object for it. Add a route object with origin AS32123 in the RIR database for the space.672 of 673

Route objects not announced

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

69.50.88.0/22ARIN, RADBValid
69.50.88.0/23ARINValid
69.50.90.0/23ARINValid
162.254.180.0/23ARINValid
162.254.180.0/24ARINValid
162.254.181.0/24ARINValid
162.254.182.0/23ARINValid
162.254.182.0/24ARINValid
162.254.183.0/24ARINValid

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.