bgpreport

Network · data from 2026-11-12

AS34403 INGBANK TR

Registry name: ingbanktr-as ING BANK ANONIM SIRKETI, TR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34403, 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.
85.158.96.0/21 Valid None 673 100% 67
85.158.98.0/24 Valid Nonecovered by 85.158.96.0/22 673 100% 67
85.158.99.0/24 Valid Nonecovered by 85.158.96.0/22 673 100% 67
85.158.100.0/24 Valid Nonecovered by 85.158.100.0/22 673 100% 67
85.158.102.0/24 Valid Nonecovered by 85.158.100.0/22 673 100% 67
85.158.103.0/24 Valid Nonecovered by 85.158.100.0/22 673 100% 67
85.158.96.0/22 Valid RIR databaseRIPE 672 100% 67
85.158.96.0/24 Valid RIR databaseRIPE 671 100% 67
85.158.97.0/24 Valid RIR databaseRIPE 671 100% 67
85.158.101.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS34403'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 8 are in fix.csv.

  • Route object: none6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none85.158.96.0/21No route object for it. Add a route object with origin AS34403 in the RIR database for the space.673 of 673
Route object: none85.158.98.0/24No route object for it. A route object for 85.158.96.0/22 with origin AS34403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34403 in the RIR database for the space.673 of 673
Route object: none85.158.99.0/24No route object for it. A route object for 85.158.96.0/22 with origin AS34403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34403 in the RIR database for the space.673 of 673
Route object: none85.158.100.0/24No route object for it. A route object for 85.158.100.0/22 with origin AS34403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34403 in the RIR database for the space.673 of 673
Route object: none85.158.102.0/24No route object for it. A route object for 85.158.100.0/22 with origin AS34403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34403 in the RIR database for the space.673 of 673
Route object: none85.158.103.0/24No route object for it. A route object for 85.158.100.0/22 with origin AS34403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34403 in the RIR database for the space.673 of 673

Route objects not announced

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

85.158.96.32/30RIPEInvalid: maxLength
85.158.100.0/22RIPEInvalid: maxLength

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.