bgpreport

Network · data from 2026-11-12

AS31976 Red Hat Inc

Registry name: REDHAT-0 - Red Hat, Inc., US · PeeringDB

1IPv4 routes 0.0% 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
15Route objects not announced registered with origin AS31976, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31976, 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.132.189.0/24 No ROA RIR databaseARIN 673 100% 66

AS-SET

AS31976'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 16 are in fix.csv.

  • ROA: none1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none209.132.189.0/24No ROA covers it. Add a ROA for AS31976, maxLength 24.673 of 673

Route objects not announced

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

38.145.32.0/19RADBNo ROA
66.187.224.0/20ARINNo ROA
66.187.224.0/21ARIN, RADBNo ROA
66.187.232.0/21ARIN, RADBNo ROA
66.187.236.0/24ARINNo ROA
209.132.176.0/20ARINNo ROA
209.132.176.0/21ARIN, RADBNo ROA
209.132.180.0/23ARIN, RADBNo ROA
209.132.182.0/23ARIN, RADBNo ROA
209.132.184.0/21RADBNo ROA
209.132.184.0/23ARINNo ROA
209.132.184.0/24RADBNo ROA
209.132.186.0/24ARINNo ROA
2620:52::/40ARINNo ROA
2620:52:1::/48ARINNo ROA

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.