bgpreport

Network · data from 2026-11-12

AS209711 MUVHost MUV Bilisim ve Telekomunikasyon Hizmetleri Ltd. Sti.

Registry name: MUVHost MUV Bilisim ve Telekomunikasyon Hizmetleri Ltd. Sti., TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209711, 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.86.155.0/24 Invalid: origin None 2 0%low visibility 2
185.184.25.0/24 Invalid: origin None 2 0%low visibility 2
185.184.26.0/24 Invalid: origin None 2 0%low visibility 2
185.98.62.0/24 Invalid: origin Other origin only 1 0%low visibility 1
31.14.52.0/24 Valid RIR databaseRIPE 673 100% 67
31.214.129.0/24 Valid RIR databaseRIPE 673 100% 67
31.214.152.0/24 Valid RIR databaseRIPE 673 100% 67
37.156.246.0/24 Valid RIR databaseRIPE 673 100% 67
89.45.94.0/24 Valid RIR databaseRIPE 673 100% 67
93.113.96.0/24 Valid RIR databaseRIPE 673 100% 67
109.230.196.0/24 Valid RIR databaseRIPE 673 100% 67
168.222.79.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.111.244.0/24 Valid RIR databaseRIPE 673 100% 67
185.111.246.0/24 Valid RIR databaseRIPE 673 100% 67
185.111.247.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.53.87.0/24 Valid RIR databaseRIPE 673 100% 67
193.53.98.0/24 Valid RIR databaseRIPE 673 100% 67
193.53.103.0/24 Valid RIR databaseRIPE 673 100% 67
193.53.245.0/24 Valid RIR databaseRIPE 673 100% 67
45.139.222.0/24 Valid RIR databaseRIPE 672 100% 67
45.145.20.0/24 Valid RIR databaseRIPE 672 100% 67
185.111.245.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS209711 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 9 are in fix.csv.

  • ROA: origin4
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin185.86.155.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS209711 should announce it, add a ROA for AS209711.2 of 673
Route object: none185.86.155.0/24No route object for it. Add a route object with origin AS209711 in the RIR database for the space.2 of 673
ROA: origin185.184.25.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS209711 should announce it, add a ROA for AS209711.2 of 673
Route object: none185.184.25.0/24No route object for it. Add a route object with origin AS209711 in the RIR database for the space.2 of 673
ROA: origin185.184.26.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS209711 should announce it, add a ROA for AS209711.2 of 673
Route object: none185.184.26.0/24No route object for it. Add a route object with origin AS209711 in the RIR database for the space.2 of 673
ROA: origin185.98.62.0/24ROAs covering it name AS218642, not AS209711. If AS209711 should announce it, add a ROA for AS209711.1 of 673
Route object: none185.98.62.0/24Route objects for it name AS218642. Add a route object with origin AS209711 in the RIR database for the space.1 of 673

Route objects not announced

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

45.74.243.0/24RIPEValid

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.