bgpreport

Network · data from 2026-11-12

AS398989 DeepIntent

Registry name: DEEPINTENT - DeepIntent, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS398989, 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.
8.18.47.0/24 No ROA None 2 0%low visibility 3
38.91.45.0/24 No ROA RIR databaseARIN 671 100% 68
38.105.184.0/24 No ROA RIR databaseARIN 671 100% 68
168.151.55.0/24 Valid RIR databaseARIN 671 100% 68
2620:90:a00a::/48 Valid RIR databaseARIN 635 100% 69
169.197.150.0/24 Valid RIR databaseARIN 2 0%low visibility 2
2620:90:a000::/48 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS398989'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 5 are in fix.csv.

  • ROA: none3
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none8.18.47.0/24No ROA covers it. Add a ROA for AS398989, maxLength 24.2 of 673
Route object: none8.18.47.0/24No route object for it. Add a route object with origin AS398989 in the RIR database for the space.2 of 673
ROA: none38.91.45.0/24No ROA covers it. Add a ROA for AS398989, maxLength 24.671 of 673
ROA: none38.105.184.0/24No ROA covers it. Add a ROA for AS398989, maxLength 24.671 of 673

Route objects not announced

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

2001:470:576::/48ARINValid

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.