bgpreport

Network · data from 2026-11-12

AS47123 MEDNAUTILUS

Registry name: MEDNAUTILUS TI Sparkle Turkey Telekomunukasyon A.S, TR · PeeringDB

38IPv4 routes 100.0% RPKI valid · 97.4% with a route object
8IPv6 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
13Route objects not announced registered with origin AS47123, seen from no peer

Announced routes

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

185.141.111.0/24 Valid None 673 100% 67
93.94.248.0/24 Valid RIR databaseRIPE 673 100% 67
93.94.249.0/24 Valid RIR databaseRIPE 673 100% 67
93.94.251.0/24 Valid RIR databaseRIPE 673 100% 67
93.94.252.0/23 Valid RIR databaseRIPE 673 100% 67
93.94.254.0/24 Valid RIR databaseRIPE 673 100% 67
93.94.255.0/24 Valid RIR databaseRIPE 673 100% 67
185.44.193.0/24 Valid RIR databaseRIPE 673 100% 67
185.44.194.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.64.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.65.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.66.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.67.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.68.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.69.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.70.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.71.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.72.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.74.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.75.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.76.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.77.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.78.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.79.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.82.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.83.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.84.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.85.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.86.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.87.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.88.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.89.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.90.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.91.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.92.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.93.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.94.0/24 Valid RIR databaseRIPE 673 100% 67
195.155.95.0/24 Valid RIR databaseRIPE 673 100% 67
2a04:c0::/32 Valid RIR databaseRIPE 634 100% 67
2a04:c2::/32 Valid RIR databaseRIPE 634 100% 67
2a04:c3::/32 Valid RIR databaseRIPE 634 100% 67
2a04:c4::/32 Valid RIR databaseRIPE 634 100% 67
2a04:c5::/32 Valid RIR databaseRIPE 634 100% 67
2a04:c6::/32 Valid RIR databaseRIPE 634 100% 67
2a04:c7::/32 Valid RIR databaseRIPE 634 100% 67
2a04:c1::/32 Valid RIR databaseRIPE 631 99% 67

AS-SET

AS47123'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 14 are in fix.csv.

  • Route object: none1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none185.141.111.0/24No route object for it. Add a route object with origin AS47123 in the RIR database for the space.673 of 673

Route objects not announced

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

5.253.250.0/24RIPEValid
5.253.251.0/24RIPEValid
93.94.248.0/21RIPENo ROA
93.94.250.0/24RIPEValid
93.94.252.0/24RIPEInvalid: maxLength
93.94.253.0/24RIPEInvalid: maxLength
185.44.192.0/24RIPEValid
185.44.195.0/24RIPEValid
195.155.64.0/19RIPENo ROA
195.155.73.0/24RIPEValid
195.155.80.0/24RIPEValid
195.155.81.0/24RIPEValid
2a04:c0::/29RIPENo ROA

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.