bgpreport

Network · data from 2026-11-12

AS22096 Tigris Data

Registry name: TIGRISDATA - Tigris Data Inc., US · PeeringDB

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

Announced routes

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

23.88.233.0/24 Valid Nonecovered by 23.88.232.0/21 673 100% 67
66.93.0.0/24 Valid Nonecovered by 66.93.0.0/22 673 100% 67
66.93.2.0/24 Valid Nonecovered by 66.93.0.0/22 671 100% 67
23.88.232.0/21 Valid RIR databaseARIN, RADB 673 100% 67
66.93.0.0/22 Valid RIR databaseARIN, RADB 673 100% 67
2604:9a0::/32 Valid RIR databaseARIN 636 100% 67

AS-SET

AS22096'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 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none23.88.233.0/24No route object for it. A route object for 23.88.232.0/21 with origin AS22096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22096 in the RIR database for the space.673 of 673
Route object: none66.93.0.0/24No route object for it. A route object for 66.93.0.0/22 with origin AS22096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22096 in the RIR database for the space.673 of 673
Route object: none66.93.2.0/24No route object for it. A route object for 66.93.0.0/22 with origin AS22096 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22096 in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS22096 is announced.

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.