bgpreport

Network · data from 2026-11-12

AS199724 TEKNODC TeknoDC Bilisim Teknolojileri A.S.

Registry name: TEKNODC TeknoDC Bilisim Teknolojileri A.S., TR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199724, 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.250.241.0/24 Invalid: origin Other origin only 1 0%low visibility 1
38.3.136.0/22 No ROA Other IRR onlyRADB 672 100% 66
149.13.62.0/24 No ROA Other IRR onlyRADB 672 100% 66
149.13.63.0/24 No ROA Other IRR onlyRADB 672 100% 66
149.100.70.0/24 No ROA Other IRR onlyRADB 672 100% 66
154.48.210.0/24 No ROA Other IRR onlyRADB 672 100% 66
154.49.168.0/24 No ROA Other IRR onlyRADB 672 100% 66
154.49.169.0/24 No ROA Other IRR onlyRADB 672 100% 66
154.49.170.0/24 No ROA Other IRR onlyRADB 672 100% 66
154.49.171.0/24 No ROA Other IRR onlyRADB 672 100% 66
154.58.140.0/24 No ROA Other IRR onlyRADB 672 100% 66
38.225.127.0/24 No ROA Other IRR onlyRADB 671 100% 66
38.225.192.0/24 No ROA Other IRR onlyRADB 671 100% 66
38.225.193.0/24 No ROA Other IRR onlyRADB 671 100% 66
38.225.194.0/24 No ROA Other IRR onlyRADB 671 100% 66
38.225.211.0/24 No ROA Other IRR onlyRADB 671 100% 66
38.225.212.0/24 No ROA Other IRR onlyRADB 671 100% 66
91.102.160.0/24 Valid Other origin only 672 100% 66
212.146.128.0/24 Valid RIR databaseRIPE 672 100% 66
212.146.129.0/24 Valid RIR databaseRIPE 672 100% 66
212.146.130.0/24 Valid RIR databaseRIPE 672 100% 66
212.146.131.0/24 Valid RIR databaseRIPE 672 100% 66
91.102.164.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS199724 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 37 are in fix.csv.

  • ROA: origin1
  • ROA: none16
  • Route object: none2
  • Route object: RIR16
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin185.250.241.0/24ROAs covering it name AS211804, not AS199724. If AS199724 should announce it, add a ROA for AS199724.1 of 673
Route object: none185.250.241.0/24Route objects for it name AS211804. Add a route object with origin AS199724 in the RIR database for the space.1 of 673
ROA: none38.3.136.0/22No ROA covers it. Add a ROA for AS199724, maxLength 22.672 of 673
Route object: RIR38.3.136.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.13.62.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR149.13.62.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.13.63.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR149.13.63.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.100.70.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR149.100.70.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.48.210.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR154.48.210.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.49.168.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR154.49.168.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.49.169.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR154.49.169.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.49.170.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR154.49.170.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.49.171.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR154.49.171.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none154.58.140.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.672 of 673
Route object: RIR154.58.140.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.225.127.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.671 of 673
Route object: RIR38.225.127.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.225.192.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.671 of 673
Route object: RIR38.225.192.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.225.193.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.671 of 673
Route object: RIR38.225.193.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.225.194.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.671 of 673
Route object: RIR38.225.194.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.225.211.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.671 of 673
Route object: RIR38.225.211.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.225.212.0/24No ROA covers it. Add a ROA for AS199724, maxLength 24.671 of 673
Route object: RIR38.225.212.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none91.102.160.0/24Route objects for it name AS41801. Add a route object with origin AS199724 in the RIR database for the space.672 of 673

Route objects not announced

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

185.48.220.0/22RIPEInvalid: origin
2a01:9ba0::/32RIPEInvalid: origin

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.