bgpreport

Network · data from 2026-11-12

AS215238 IRFAN TUGRA ONEM

Registry name: ONEMBILISIM IRFAN TUGRA ONEM, TR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215238, 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.
188.125.166.0/24 No ROA None 2 0%low visibility 2
212.134.162.0/24 Valid Other IRR onlyRADB 670 100% 66
176.96.128.0/24 Valid RIR databaseRIPE 672 100% 66
5.226.191.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
31.59.131.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
68.68.255.0/24 Valid RIR databaseARIN 670 100% 66
78.40.208.0/24 Valid RIR databaseRIPE 670 100% 66
87.76.130.0/24 Valid RIR databaseRIPE 670 100% 66
87.76.161.0/24 Valid RIR databaseRIPE 670 100% 66
87.232.127.0/24 Valid RIR databaseRIPE 670 100% 66
89.251.18.0/24 Valid RIR databaseRIPE 670 100% 66
109.122.21.0/24 Valid RIR databaseRIPE 670 100% 66
142.249.111.0/24 Valid RIR databaseARIN 670 100% 66
167.148.181.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
188.191.107.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
191.44.68.0/24 Valid RIR databaseRIPE 670 100% 66
191.44.89.0/24 Valid RIR databaseRIPE 670 100% 66
195.123.4.0/24 Valid RIR databaseRIPE 670 100% 66
212.38.88.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
45.39.93.0/24 Valid RIR databaseARIN, RADB 669 99% 66
45.150.149.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
167.148.212.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
2a0f:85c1:b77::/48 Valid RIR databaseRIPE 634 100% 67
2a13:9500:171::/48 Valid RIR databaseRADB, RIPE 632 99% 67

AS-SET

AS215238'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: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none188.125.166.0/24No ROA covers it. Add a ROA for AS215238, maxLength 24.2 of 673
Route object: none188.125.166.0/24No route object for it. Add a route object with origin AS215238 in the RIR database for the space.2 of 673
Route object: RIR212.134.162.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

2a13:9500:175::/48RIPEValid

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.