bgpreport

Network · data from 2026-11-12

AS48407 TIGRISNET

Registry name: TIGRISNET-IRAQ TigrisNet, IQ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48407, 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.
81.90.18.0/24 Valid RIR databaseRIPE 672 100% 67
81.90.19.0/24 Valid RIR databaseRIPE 672 100% 67
81.90.23.0/24 Valid RIR databaseRIPE 672 100% 67
81.90.26.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
81.90.27.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
93.94.53.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
93.94.50.0/24 Valid RIR databaseRADB, RIPE 669 99% 68
93.94.55.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
93.94.54.0/24 Valid RIR databaseRADB, RIPE 1 0%low visibility 1

AS-SET

AS48407'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 6 are in fix.csv.

  • Route object: not announced6

Route objects not announced

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

81.90.21.0/24RIPEValid
81.90.22.0/24RIPEValid
81.90.24.0/24RADBValid
93.94.48.0/21RIPENo ROA
178.17.55.0/24RADBNo ROA
2a00:8b20::/32RIPEValid

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.