Network · data from 2026-11-12

AS200239 BOGAHOST

Registry name: BOGAHOST Bogahost Bilisim ve Telekomunikasyon Hiz San ve Tic. Ltd. Sti, TR · PeeringDB

22IPv4 routes 86.4% RPKI valid · 86.4% with a route object

0IPv6 routes

3RPKI invalid 3 origin · 0 maxLength

0No ROA 3 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS200239, seen from no peer

Announced routes

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


92.112.154.0/24	Invalid: origin	Other origin only	147 22%	49
31.57.215.0/24	Invalid: origin	Other origin only	146 22%	49
185.218.101.0/24	Invalid: origin	Other origin only	7 1%low visibility	9
2.27.78.0/24	Valid	RIR databaseRIPE	672 100%	67
5.178.100.0/24	Valid	RIR databaseRIPE	672 100%	67
5.180.32.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
104.252.135.0/24	Valid	RIR databaseARIN	672 100%	67
141.11.204.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
162.141.9.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
168.222.73.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
185.194.30.0/24	Valid	RIR databaseRADB, RIPE	672 100%	67
185.229.220.0/24	Valid	RIR databaseRIPE	672 100%	67
193.106.197.0/24	Valid	RIR databaseRIPE	672 100%	67
194.87.64.0/24	Valid	RIR databaseRIPE	672 100%	67
194.87.91.0/24	Valid	RIR databaseRIPE	672 100%	67
194.87.188.0/24	Valid	RIR databaseRIPE	672 100%	67
195.58.63.0/24	Valid	RIR databaseRIPE	672 100%	67
2.59.181.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
45.80.174.0/24	Valid	RIR databaseRIPE	671 100%	67
46.37.107.0/24	Valid	RIR databaseRADB, RIPE	671 100%	67
45.195.144.0/24	Valid	RIR databaseAFRINIC, RADB	670 100%	67
45.90.88.0/24	Valid	RIR databaseRIPE	641 95%	67

92.112.154.0/24

Invalid: origin

Other origin only

147 22%

31.57.215.0/24

Invalid: origin

Other origin only

146 22%

185.218.101.0/24

Invalid: origin

Other origin only

7 1%low visibility

2.27.78.0/24

Valid

RIR databaseRIPE

672 100%

5.178.100.0/24

Valid

RIR databaseRIPE

672 100%

5.180.32.0/24

Valid

RIR databaseRADB, RIPE

672 100%

104.252.135.0/24

Valid

RIR databaseARIN

672 100%

141.11.204.0/24

Valid

RIR databaseRADB, RIPE

672 100%

162.141.9.0/24

Valid

RIR databaseRADB, RIPE

672 100%

168.222.73.0/24

Valid

RIR databaseRADB, RIPE

672 100%

185.194.30.0/24

Valid

RIR databaseRADB, RIPE

672 100%

185.229.220.0/24

Valid

RIR databaseRIPE

672 100%

193.106.197.0/24

Valid

RIR databaseRIPE

672 100%

194.87.64.0/24

Valid

RIR databaseRIPE

672 100%

194.87.91.0/24

Valid

RIR databaseRIPE

672 100%

194.87.188.0/24

Valid

RIR databaseRIPE

672 100%

195.58.63.0/24

Valid

RIR databaseRIPE

672 100%

2.59.181.0/24

Valid

RIR databaseRADB, RIPE

671 100%

45.80.174.0/24

Valid

RIR databaseRIPE

671 100%

46.37.107.0/24

Valid

RIR databaseRADB, RIPE

671 100%

45.195.144.0/24

Valid

RIR databaseAFRINIC, RADB

670 100%

45.90.88.0/24

Valid

RIR databaseRIPE

641 95%

AS-SET

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

ROA: origin3
Route object: none3
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	92.112.154.0/24	ROAs covering it name AS147281, not AS200239. If AS200239 should announce it, add a ROA for AS200239.	147 of 673
Route object: none	92.112.154.0/24	Route objects for it name AS834. Add a route object with origin AS200239 in the RIR database for the space.	147 of 673
ROA: origin	31.57.215.0/24	ROAs covering it name AS834, not AS200239. If AS200239 should announce it, add a ROA for AS200239.	146 of 673
Route object: none	31.57.215.0/24	Route objects for it name AS834. Add a route object with origin AS200239 in the RIR database for the space.	146 of 673
ROA: origin	185.218.101.0/24	ROAs covering it name AS834, AS147281, not AS200239. If AS200239 should announce it, add a ROA for AS200239.	7 of 673
Route object: none	185.218.101.0/24	Route objects for it name AS147281. Add a route object with origin AS200239 in the RIR database for the space.	7 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

92.112.154.0/24

ROAs covering it name AS147281, not AS200239. If AS200239 should announce it, add a ROA for AS200239.

147 of 673

Route object: none

92.112.154.0/24

Route objects for it name AS834. Add a route object with origin AS200239 in the RIR database for the space.

147 of 673

ROA: origin

31.57.215.0/24

ROAs covering it name AS834, not AS200239. If AS200239 should announce it, add a ROA for AS200239.

146 of 673

Route object: none

31.57.215.0/24

Route objects for it name AS834. Add a route object with origin AS200239 in the RIR database for the space.

146 of 673

ROA: origin

185.218.101.0/24

ROAs covering it name AS834, AS147281, not AS200239. If AS200239 should announce it, add a ROA for AS200239.

7 of 673

Route object: none

185.218.101.0/24

Route objects for it name AS147281. Add a route object with origin AS200239 in the RIR database for the space.

7 of 673

Route objects not announced

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


5.133.101.0/24	RIPE	Valid

5.133.101.0/24

RIPE

Valid

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.