bgpreport

Network · data from 2026-11-12

AS30150 Exegy

Registry name: EXEGY - Exegy Incorporated, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30150, 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.
202.36.74.0/24 No ROA RIR databaseAPNIC 673 100% 69
185.125.104.0/24 Valid RIR databaseRIPE 673 100% 67
185.125.106.0/24 Valid RIR databaseRIPE 673 100% 67
199.191.53.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.99.212.0/24 Valid RIR databaseARIN 671 100% 67
216.99.213.0/24 Valid RIR databaseARIN 671 100% 67
216.99.215.0/24 Valid RIR databaseARIN 671 100% 68
2620:1b:6001::/48 Valid RIR databaseARIN 634 100% 68
2a0c:e340::/32 Valid RIR databaseRIPE 634 100% 68
2a0c:e340:1::/48 Valid RIR databaseRIPE 634 100% 68
2620:1b:6000::/48 Valid RIR databaseARIN, RADB 605 95% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none202.36.74.0/24No ROA covers it. Add a ROA for AS30150, maxLength 24.673 of 673

Route objects not announced

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

199.30.244.0/24RADBNo ROA
2001:470:423::/48ARINValid
2620:1b:6002::/48RADBNo 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.