bgpreport

Network · data from 2026-11-12

AS49334 SH-COM-TR SH ONLINE ILETISIM ANONIM SIRKETI

Registry name: SH-COM-TR SH ONLINE ILETISIM ANONIM SIRKETI, TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49334, 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.
31.210.34.0/24 Valid None 672 100% 66
31.210.52.0/24 Valid RIR databaseRIPE 673 100% 66
31.210.53.0/24 Valid RIR databaseRIPE 673 100% 66
31.210.60.0/24 Valid RIR databaseRIPE 673 100% 66
78.135.65.0/24 Valid RIR databaseRIPE 673 100% 66
188.132.131.0/24 Valid RIR databaseRIPE 673 100% 66
188.132.173.0/24 Valid RIR databaseRIPE 673 100% 66
188.132.181.0/24 Valid RIR databaseRIPE 673 100% 66
188.132.182.0/24 Valid RIR databaseRIPE 673 100% 66
188.132.187.0/24 Valid RIR databaseRIPE 673 100% 66
212.68.53.0/24 Valid RIR databaseRIPE 673 100% 66
212.68.54.0/24 Valid RIR databaseRIPE 673 100% 66
212.68.62.0/24 Valid RIR databaseRIPE 673 100% 66
212.68.63.0/24 Valid RIR databaseRIPE 673 100% 66
2a02:26b0:8003::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS49334 isn't in PeeringDB, where networks name their 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none31.210.34.0/24No route object for it. Add a route object with origin AS49334 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS49334 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.