ixreport

BOGAHOST

AS200239 · BogaHost

Bogahost Bilisim ve Telekomunikasyon Hiz. San ve Tic. Ltd. Sti.

1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
0Using the route servers
2To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with BOGAHOST? · Where should BOGAHOST peer next? · Compare BOGAHOST with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in BOGAHOST's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on BOGAHOST's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in BOGAHOST's PeeringDB record. Add one entry per connection with these values.

  1. Türkiye DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150From its IX-F export
    IPv4185.1.48.31
    IPv62001:7f8:3f:0:3:e2f:0:1
    Speed100000 Mbps (100G)
    RS peerNo

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Türkiye DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.48.31 is AS63199 CDS Global Cloud Co., LTD185.1.48.31

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

Exchanges over time

01Oct 3, 2026Nov 19, 20261
Show as a table
DateExchanges
Nov 19, 20261
Nov 18, 20261
Nov 17, 20261
Nov 16, 20261
Nov 15, 20261
Nov 14, 20261
Nov 13, 20261
Nov 12, 20261
Nov 11, 20261
Nov 10, 20261
Nov 9, 20261
Nov 8, 20261
Nov 7, 20261
Nov 6, 20261
Nov 5, 20261
Nov 4, 20261
Nov 3, 20261
Nov 2, 20261
Nov 1, 20261
Oct 31, 20261
Oct 30, 20261
Oct 29, 20261
Oct 28, 20261
Oct 27, 20261
Oct 26, 20261
Oct 25, 20261
Oct 24, 20261
Oct 23, 20261
Oct 22, 20261
Oct 20, 20261
Oct 19, 20261
Oct 18, 20261
Oct 17, 20261
Oct 16, 20261
Oct 15, 20261
Oct 14, 20261
Oct 13, 20261
Oct 12, 20261
Oct 11, 20261
Oct 10, 20261
Oct 9, 20261
Oct 8, 20261
Oct 7, 20261
Oct 6, 20261
Oct 5, 20261
Oct 4, 20261
Oct 3, 20261

Map

Where BOGAHOST's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 100G across 1 exchange.

Türkiye DE-CIX Istanbul Istanbul, Türkiye 185.1.48.31 2001:7f8:3f:0:3:e2f:0:1 100G Not in PeeringDB Address taken

Exchanges in its buildings that it isn't on (1)

These exchanges have a switch in a facility where BOGAHOST lists itself in PeeringDB, but don't have BOGAHOST as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Türkiye GIBIRIXİstanbul, Türkiye 28 TurkNet Iletisim Hizmetleri A.S
Facilities (2)

The buildings BOGAHOST lists in PeeringDB, and how many of the exchanges in each it's on.

Türkiye TurkNet Iletisim Hizmetleri A.SIstanbul 1 of 2
Türkiye Mars Datacenter Istanbul-1Istanbul 1 of 1